www.jorudan.co.jp speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:11 UTC. Grade A (96/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 85 ms 28%
- TCP connect 56 ms 19%
- Server wait 157 ms 53%
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 299 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 628 B over 1 request(s), which is lean.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- The largest element painted at 688 ms, inside the 2.5 s Google calls good.
- Layout shift is 0.319 (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 76 ms in total, which is not enough to feel.
Fix first: Avoid extra redirects - 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.
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.
Top issues
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.
Strict-Transport-Security
low impactHSTS 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.
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.