www.hatena.ne.jp speed test — 20 Oct 2026

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

https://www.hatena.ne.jp:443/

20 October 2026 at 13:13 UTC · Free test · report pt_15f2fd141448

Re-test this page Test your own site

Grade

77/100

Performance77/100

Structure77/100

11 audit(s) passed, 5 need work

First byte (TTFB)956 msmeasured from this server

Fully loaded2.30 sfirst byte + slowest asset

Requests26document + assets

Page weight151.1 KBcompressed transfer

HTML document145.5 KBgzip

ProtocolHTTP/2nginx

Third-party5.1 KBother hosts

Where the first byte went

DNS lookup 93 ms 10%
TCP connect 178 ms 19%
Server wait 685 ms 72%

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 83% of 4,999 pages tested here956 ms against a median of 448 ms

Page weightlighter than 83% of 4,999 pages tested here151.1 KB against a median of 650.5 KB

Fully loadedslower than 68% of 4,999 pages tested here2.30 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 956 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 151.1 KB over 26 request(s).
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element painted at 2.20 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.029), so nothing jumps under the reader's cursor.
The main thread was blocked for 116 ms in total, which is not enough to feel.

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.

Screenshot

What the page looks like

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

Mobile screenshot of www.hatena.ne.jp — **Mobile** 390 × 844 · 53.1 KB · page is 6000 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 paint2.20 sgood is under 2.5 s

Cumulative layout shift0.029under 0.1 is stable

Total blocking time116 mslong tasks during load

First contentful paint2.06 sfirst content on screen

Browser page weight4.08 MB352 request(s), scripts included

Failed requests4blocked or unreachable

Largest contentful paint2.20 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.029

Goodgood under 0.1, poor over 0.25

Total blocking time116 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 24 requests

5.1 KB 3%

Images 1 request

465 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 956 ms. Of that, 685 ms was the server thinking and 271 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.

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 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.

HTML document size

medium impact

The document transfers 145.5 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

Avoid extra redirects

medium impact

2 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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.