home.blog speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:56 UTC. Grade A (91/100), with the screenshots, the timings and the fixes that matter.

https://home.blog/

20 October 2026 at 13:56 UTC · Free test · report pt_42d65c273a3d
Grade
A
91/100
Performance100/100
Structure77/100

12 audit(s) passed, 4 need work

First byte (TTFB)210 msmeasured from this server
Fully loaded1.26 sfirst byte + slowest asset
Requests22document + assets
Page weight321.7 KBcompressed transfer
HTML document17.0 KBbr
ProtocolHTTP/3nginx
Third-party15.4 KBother hosts

Where the first byte went

  • DNS lookup 79 ms 38%
  • TCP connect 24 ms 11%
  • Server wait 108 ms 51%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 91% of 4,999 pages tested here210 ms against a median of 449 ms
Page weightlighter than 70% of 4,999 pages tested here321.7 KB against a median of 650.5 KB
Fully loadedfaster than 85% of 4,999 pages tested here1.26 s against a median of 1.84 s
Requestssends fewer requests than 77% of 4,999 pages tested here22 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 210 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 321.7 KB over 22 request(s). Images files are 60% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.13 s, inside the 2.5 s Google calls good.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of home.blog
Mobile 390 × 844 · 63.3 KB · page is 1072 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.13 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint584 msfirst content on screen
Browser page weight562.2 KB35 request(s), scripts included
Largest contentful paint1.13 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 7 requests
192.4 KB 60%
Javascript 6 requests
63.0 KB 20%
Css 7 requests
49.2 KB 15%

Transfer size, compressed as sent. 22 request(s) in total, 321.7 KB across all of them.

Top issues

Render-blocking resources

high impact

8 render-blocking resource(s) in the document head (1 script(s), 7 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Cache static assets

medium impact

7 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Third-party weight

low impact

5 third-party host(s) serve 15.4 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Waterfall

Slowest requests

HTMLhome.blog/r
1.05 s
IMAGEShome.blog/wp-content/uploads/2017/11/agi_appalac…
977 ms
JAVASCRIPThome.blog/_static/
906 ms
IMAGESpixel.wp.com/b.gif
901 ms
IMAGEShome.blog/wp-content/uploads/2017/11/agi_appalac…
900 ms
JAVASCRIPTstats.wp.com/w.js
900 ms
IMAGEShome.blog/wp-content/uploads/2017/12/home-icon.jpg
900 ms
JAVASCRIPT0.gravatar.com/js/hovercards/hovercards.min.js
891 ms
IMAGEShome.blog/wp-content/uploads/2017/12/home-icon.jpg
881 ms
CSSs0.wp.com/
874 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://home.blog/rhtml4041.05 s0 B
https://home.blog/wp-content/uploads/2017/11/agi_appalachia_bierut_171120_021.jpg?w=924&h=1&crop=1images200977 ms125.5 KB
https://home.blog/_static/??-eJzTLy/QTc7PK0nNK9HPKtYvyinRLSjKr6jUyyrW0QfKZeYl55SmpBaDJLMKS1OLKqGUXm5mHkFFurmZ6UWJJalQxfa5tobmRgamxgZmFpZZACbyLJI=javascript200906 ms35.9 KB
https://pixel.wp.com/b.gif?v=noscript 3rd partyimages200901 ms43 B
https://home.blog/wp-content/uploads/2017/11/agi_appalachia_bierut_171120_021.jpg?w=924&h=0&crop=1images200900 ms49.7 KB
https://stats.wp.com/w.js?70 3rd partyjavascript200900 ms6.4 KB
https://home.blog/wp-content/uploads/2017/12/home-icon.jpg?w=50images200900 ms1.4 KB
https://0.gravatar.com/js/hovercards/hovercards.min.js?ver=202643d1133547e8a1f2801609f51cef12522abe7f6647d869e9fbc974fe356a37e613 3rd partyjavascript200891 ms6.8 KB
https://home.blog/wp-content/uploads/2017/12/home-icon.jpg?w=180images200881 ms7.1 KB
https://s0.wp.com/?custom-css=1&csblog=83xkp&cscache=6&csrev=90 3rd partycss200874 ms1.9 KB
https://home.blog/wp-content/uploads/2017/12/home-icon.jpg?w=32images200873 ms969 B
https://home.blog/_static/??-eJyNjcEKAjEMRH/ImhVlqwfxU6TbhrZrmhTTIv69u+JFvHgZ5sHwBh7VeOGG3KB0U6nHzAoztur87cNQRNYInVBBk7tjcCE83zVz3HrVDfxvumb2MPVMAVR8dmRIougX/DhbwrK8pwNEksnROriU884e9+PJDnaYXxwFS20=&cssminify=yescss200868 ms12.4 KB
https://home.blog/wp-content/uploads/2017/12/home-icon.jpg?w=192images200867 ms7.9 KB
https://home.blog/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yescss200865 ms21.6 KB
https://home.blog/_static/??-eJx9i9EKwjAMAH/ImA0G9UX8li3EGmmT0rQO/96JL4qwtzu4w7UAmTbWhu3GmR1LX9DqQxy9PRMfyf2Ae5kofVJYC1n+G3KHknoUday8JIsbRtyqL92bIhsko7mJ6Y/ANc1S3+sln8dwGoYwTWO4vwDASU76&cssminify=yescss200865 ms10.8 KB
https://home.blog/wp-content/js/bilmur.min.js?i=19&m=202643javascript200865 ms4.9 KB
https://home.blog/wp-content/mu-plugins/global-print/global-print.css?m=1465851035i&cssminify=yescss200865 ms1.9 KB
https://home.blog/_static/??/wp-content/mu-plugins/core-compat/wp-mediaelement.css,/wp-content/mu-plugins/wpcom-bbpress-premium-themes.css?m=1432920480j&cssminify=yescss200865 ms432 B
https://fonts-api.wp.com/css?family=Karla%3A400%2C700%2C400italic%2C700italic&subset=latin%2Clatin-ext 3rd partycss200865 ms244 B
https://home.blog/_static/??-eJyNjUEOwjAMwD5ECDANuCD+QtWOtEtSkWbwfMpOiBNXy5bxWSGotCgN2aHOPpEYBmXuCGYq0TD/gG22DX6F7R65a9VvqI+F1sAK1W5LgaTBDRK9/smSS2ik8nlc+bI/DqfxPB6GXX4DZtg+ZQ==javascript200862 ms8.7 KB
https://home.blog/wp-content/mu-plugins/gravatar-hovercards/wpgroho.js?m=1610363240ijavascript200862 ms370 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.