www.yomiuri.co.jp speed test — 20 Oct 2026

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

https://www.yomiuri.co.jp/

20 October 2026 at 13:46 UTC · Free test · report pt_0cca40a8a971

Re-test this page Test your own site

Grade

85/100

Performance93/100

Structure74/100

11 audit(s) passed, 5 need work

First byte (TTFB)239 msmeasured from this server

Fully loaded1.89 sfirst byte + slowest asset

Requests26document + assets

Page weight1.40 MBcompressed transfer

HTML document116.1 KBbr

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 58 ms 24%
TCP connect 37 ms 15%
Server wait 144 ms 60%

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 86% of 4,999 pages tested here239 ms against a median of 449 ms

Page weightheavier than 72% of 4,999 pages tested here1.40 MB against a median of 650.3 KB

Fully loadedslower than 52% of 4,999 pages tested here1.89 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 arrived in 239 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.40 MB over 26 request(s). Images files are 92% 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.

Fix first: Image delivery and format - 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.

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

1.28 MB 92%

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

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 2 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.

Render-blocking resources

high impact

17 render-blocking resource(s) in the document head (10 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.

Total page weight

medium impact

The page transfers 1.40 MB across 26 request(s), with the document itself at 116.1 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

HTML document size

medium impact

The document transfers 116.1 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

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.

Waterfall

Slowest requests

IMAGESwww.yomiuri.co.jp/media/2026/10/20261020-GYT1I00315-T.jpg

1.65 s

IMAGESwww.yomiuri.co.jp/media/2026/10/20261020-GYT1I00359-T.jpg

1.51 s