diamond.jp speed test — 20 Oct 2026

What these numbers mean

• The first byte took 513 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 631.3 KB over 26 request(s). Images files are 95% of it, so resize and recompress the largest images before anything else.
• The HTML itself arrives gzip-compressed.
• It runs over HTTP/3, so the assets share a connection instead of opening one each.
• 95% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
• The largest element took 2.82 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
• The main thread was blocked for 302 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.