thehackernews.com speed test — 20 Oct 2026

The first byte arrived after 423 ms. Of that, 302 ms was the server thinking and 121 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: 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.

16 image(s) over 200 KB and 16 large image(s) still served as JPEG or PNG.

Fix: 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.

The page transfers 7.48 MB across 26 request(s), with the document itself at 59.4 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

2 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

3 third-party host(s) serve 7.42 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.