www.channel4.com speed test — 20 Oct 2026

What these numbers mean

• The first byte arrived in 413 ms. That is workable, and the cheapest win left is caching or a warmer connection.
• The page transfers 448.3 KB over 13 request(s), which is lean. Javascript files are 98% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
• The HTML itself arrives gzip-compressed.
• It runs over HTTP/3, so the assets share a connection instead of opening one each.
• 30% 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.60 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.019), so nothing jumps under the reader's cursor.
• The main thread was blocked for 251 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.