Tools & Wizards About Us
whydidibuythat.wordpress.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

whydidibuythat.wordpress.com

Why Did I Buy That – Explaining the dubious purchases I've made over the years, exploring why I spent my money on things rather than pay my bills

Page Load Speed

3.6 sec in total

First Response

7 ms

Resources Loaded

1.6 sec

Page Rendered

2.1 sec

whydidibuythat.wordpress.com screenshot

About Website

Click here to check amazing Why Did I Buy That Wordpress content for United States. Otherwise, check out these important facts you probably never knew about whydidibuythat.wordpress.com

Explaining the dubious purchases I've made over the years, exploring why I spent my money on things rather than pay my bills

Visit whydidibuythat.wordpress.com

Key Findings

We analyzed Whydidibuythat.wordpress.com page load time and found that the first response time was 7 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

whydidibuythat.wordpress.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value9,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

whydidibuythat.wordpress.com

7 ms

whydidibuythat.wordpress.com

26 ms

121 ms

style.css

140 ms

137 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Whydidibuythat.wordpress.com, 26% (17 requests) were made to Whydidibuythat.files.wordpress.com and 14% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Whydidibuythat.files.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.2 kB (8%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whydidibuythat.wordpress.com main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 154.7 kB

  • Original 193.9 kB
  • After minification 188.6 kB
  • After compression 39.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 154.7 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 28.4 kB

  • Original 1.7 MB
  • After minification 1.7 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Why Did I Buy That Wordpress images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.6 kB

  • Original 247.4 kB
  • After minification 247.4 kB
  • After compression 244.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 396 B

  • Original 85.0 kB
  • After minification 85.0 kB
  • After compression 84.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Whydidibuythat.wordpress.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (37%)

Requests Now

57

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Did I Buy That Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whydidibuythat.wordpress.com

whydidibuythat.wordpress.com

7 ms

whydidibuythat.wordpress.com

whydidibuythat.wordpress.com

26 ms

121 ms

style.css

style.css

140 ms

137 ms

131 ms

126 ms

style.css

style.css

125 ms

css

css

161 ms

129 ms

global.css

global.css

136 ms

129 ms

hovercards.min.js

hovercards.min.js

141 ms

wpgroho.js

wpgroho.js

140 ms

125 ms

126 ms

w.js

w.js

140 ms

global-print.css

global-print.css

2 ms

conf

conf

367 ms

ga.js

ga.js

191 ms

header.jpg

header.jpg

140 ms

19781.jpg

19781.jpg

312 ms

J-fwuaYXv3M

J-fwuaYXv3M

405 ms

lBcVrb-snPk

lBcVrb-snPk

567 ms

cVvfAc8fyBQ

cVvfAc8fyBQ

593 ms

X2Oi5OX4ql8

X2Oi5OX4ql8

591 ms

jjl14sLjOTU

jjl14sLjOTU

547 ms

b72e5bf36ac8253e8909f1053881947786b2a117882fb91eaeac65edea23b8f3

b72e5bf36ac8253e8909f1053881947786b2a117882fb91eaeac65edea23b8f3

389 ms

f320348f1e78ed125445711d84cffaed994c43892508c1ec875f56c714d71104

f320348f1e78ed125445711d84cffaed994c43892508c1ec875f56c714d71104

217 ms

d9316c72cf7640e225aec50cf517b57617391cd964ee70ff840d5e0e90998c84

d9316c72cf7640e225aec50cf517b57617391cd964ee70ff840d5e0e90998c84

389 ms

g.gif

g.gif

282 ms

300 ms

e6698b4705989a3702a44835dca8d85be4aa7e4d0930d9406668ddf1c8ae5b67

e6698b4705989a3702a44835dca8d85be4aa7e4d0930d9406668ddf1c8ae5b67

406 ms

g.gif

g.gif

261 ms

g.gif

g.gif

280 ms

rr.jpg

rr.jpg

253 ms

live.jpg

live.jpg

405 ms

newrthing.jpg

newrthing.jpg

331 ms

19782.jpg

19782.jpg

325 ms

bingo.jpg

bingo.jpg

409 ms

untitled.jpg

untitled.jpg

369 ms

screenshot-2020-11-21-at-18.45.07.png

screenshot-2020-11-21-at-18.45.07.png

1095 ms

screenshot-2020-11-21-at-18.31.36.png

screenshot-2020-11-21-at-18.31.36.png

1097 ms

screenshot-2020-11-20-at-20.45.04.png

screenshot-2020-11-20-at-20.45.04.png

1094 ms

screenshot-2020-11-20-at-20.18.54.png

screenshot-2020-11-20-at-20.18.54.png

1094 ms

screenshot-2020-11-19-at-22.42.32.png

screenshot-2020-11-19-at-22.42.32.png

1223 ms

screenshot-2020-11-19-at-22.26.39.png

screenshot-2020-11-19-at-22.26.39.png

1096 ms

screenshot-2020-11-18-at-22.49.45.png

screenshot-2020-11-18-at-22.49.45.png

1220 ms

screenshot-2020-11-18-at-21.20.40.png

screenshot-2020-11-18-at-21.20.40.png

1095 ms

screenshot-2020-11-17-at-19.22.05.png

screenshot-2020-11-17-at-19.22.05.png

1221 ms

screenshot-2020-11-17-at-19.04.01.png

screenshot-2020-11-17-at-19.04.01.png

1222 ms

wpcom-gray-white.png

wpcom-gray-white.png

132 ms

S6u9w4BMUTPHh6UVSwaPHA3q5d0.ttf

S6u9w4BMUTPHh6UVSwaPHA3q5d0.ttf

258 ms

S6u9w4BMUTPHh50XSwaPHA3q5d0.ttf

S6u9w4BMUTPHh50XSwaPHA3q5d0.ttf

277 ms

S6uyw4BMUTPHjxAwWyWtFCc.ttf

S6uyw4BMUTPHjxAwWyWtFCc.ttf

257 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtbK-F2qO0g.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtbK-F2qO0g.ttf

202 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtbK-F2qO0g.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtbK-F2qO0g.ttf

201 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXt_A_H-uE0q0EA.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXt_A_H-uE0q0EA.ttf

277 ms

Genericons.svg

Genericons.svg

94 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

1 ms

__utm.gif

__utm.gif

121 ms

ata.js

ata.js

157 ms

www-player.css

www-player.css

85 ms

www-embed-player.js

www-embed-player.js

114 ms

base.js

base.js

196 ms

embed.js

embed.js

134 ms

Accessibility Review

whydidibuythat.wordpress.com accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

whydidibuythat.wordpress.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whydidibuythat.wordpress.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whydidibuythat.wordpress.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Whydidibuythat.wordpress.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

whydidibuythat.wordpress.com

Open Graph data is detected on the main page of Why Did I Buy That Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: