hatena.blog speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:06 UTC. Grade B (87/100), with the screenshots, the timings and the fixes that matter.

https://hatena.blog/

20 October 2026 at 14:06 UTC · Free test · report pt_c802c54beda7

Re-test this page Test your own site

Grade

87/100

Performance83/100

Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)748 msmeasured from this server

Fully loaded2.05 sfirst byte + slowest asset

Requests26document + assets

Page weight190.8 KBcompressed transfer

HTML document53.0 KBgzip

ProtocolHTTP/3nginx

Third-party137.8 KBother hosts

Where the first byte went

DNS lookup 85 ms 11%
TCP connect 40 ms 5%
Server wait 623 ms 83%

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 byteslower than 73% of 4,999 pages tested here748 ms against a median of 448 ms

Page weightlighter than 80% of 4,999 pages tested here190.8 KB against a median of 650.5 KB

Fully loadedslower than 59% of 4,999 pages tested here2.05 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 took 748 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 190.8 KB over 26 request(s). Images files are 72% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
72% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 25 requests

137.8 KB 72%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 748 ms. Of that, 623 ms was the server thinking and 125 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.