punchng.com speed test — 20 Oct 2026

What these numbers mean

• The first byte took 520 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 389.7 KB over 26 request(s). Images files are 89% 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.
• 79% 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 812 ms, inside the 2.5 s Google calls good.
• Layout stayed still (CLS 0.064), so nothing jumps under the reader's cursor.
• The main thread was blocked for 177 ms in total, which is not enough to feel.

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.