www.nikkei.com speed test — 20 Oct 2026

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

https://www.nikkei.com:443/

20 October 2026 at 12:28 UTC · Free test · report pt_1417f72cb9b9

Re-test this page Test your own site

Grade

85/100

Performance83/100

Structure88/100

12 audit(s) passed, 4 need work

First byte (TTFB)806 msmeasured from this server

Fully loaded1.74 sfirst byte + slowest asset

Requests26document + assets

Page weight468.2 KBcompressed transfer

HTML document72.9 KBbr

ProtocolHTTP/3server not sent

Third-party381.4 KBother hosts

Where the first byte went

DNS lookup 40 ms 5%
TCP connect 19 ms 2%
Server wait 746 ms 93%

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

Page weightlighter than 60% of 4,999 pages tested here468.2 KB against a median of 650.5 KB

Fully loadedfaster than 55% of 4,999 pages tested here1.74 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 806 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 468.2 KB over 26 request(s). Images files are 84% 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.
81% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 664 ms, inside the 2.5 s Google calls good.
Layout shift is 0.151 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 268 ms, so taps and scrolling wait while scripts run.

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.nikkei.com — **Mobile** 390 × 844 · 205.5 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 paint664 msgood is under 2.5 s

Cumulative layout shift0.151under 0.1 is stable

Total blocking time268 mslong tasks during load

First contentful paint596 msfirst content on screen

Browser page weight2.00 MB136 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint664 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.151

Needs improvementgood under 0.1, poor over 0.25

Total blocking time268 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

395.4 KB 84%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 806 ms. Of that, 746 ms was the server thinking and 59 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.

Cache static assets

medium impact

1 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

medium impact

2 third-party host(s) serve 381.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.

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.