www.cnet.com speed test — 20 Oct 2026

What these numbers mean

• The server answered in 161 ms, which is fast: almost all of the wait is the page itself, not the host.
• The page transfers 35.91 MB over 26 request(s). Images files are 100% 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.
• The largest element took 4.27 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.001), so nothing jumps under the reader's cursor.
• The main thread was blocked for 1.01 s, so taps and scrolling wait while scripts run.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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.