romarg.com speed test — 20 Oct 2026

What these numbers mean

• The first byte took 912 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 641.1 KB over 11 request(s), which is lean. Images files are 58% 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.
• 25% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
• The largest element took 6.58 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.
• Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.

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.