sorry.pia.jp speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:52 UTC. Grade B (85/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 54 ms 11%
- TCP connect 212 ms 44%
- Server wait 211 ms 44%
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
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 477 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 1.6 KB over 4 request(s), which is lean.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- The largest element painted at 760 ms, inside the 2.5 s Google calls good.
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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 4 request(s) in total, 1.6 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 477 ms. Of that, 211 ms was the server thinking and 266 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 impact3 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.
Serve everything over HTTPS
high impactThe page itself is served over plain HTTP.
Fix: Redirect HTTP to HTTPS at the server, and rewrite the remaining http:// asset references so nothing depends on browser upgrading.
Avoid extra redirects
medium impact1 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.
Mobile viewport
medium impactNo viewport meta tag, so a phone renders the desktop layout scaled down.
Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.
Waterfall
Slowest requests
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| http://sorry.pia.jp/common/css/print.css | html | 404 | 390 ms | 0 B |
| http://sorry.pia.jp/common/js/rollover.js | html | 404 | 384 ms | 0 B |
| http://sorry.pia.jp/style.css | html | 404 | 377 ms | 0 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.