Fair Web
Menu

Weigh my page · measured just now

This page weighs 0.34 MB.

fair.cflare.dev/lite

Figure 1 · The same page at 1 Mbps

AS BUILT0.34 MB2.7 s
IF IT LISTENED0.34 MB for a browser that sends Save-Data: on2.7 s

Already about as light as these changes can make it.

Bytes measured; times are arithmetic (bytes × 8 ÷ 1,000,000). Real slow networks add latency on top.

Part 1 · Who paysNot you, probably.

That's lighter than the median mobile page (2,164 KB, HTTP Archive 2025). The changes below still take weight off for people who ask.

On fast fibre this page costs about a second. At 1 Mbps it takes 2.7 s before it's all there, and on a prepaid plan every megabyte of it is paid for. People in low-income economies spend about 22 times more of their income on a mobile broadband plan than people in high-income economies (ITU 2025).

Part 2 · Level itWhat to change, biggest first.

Make these changes when the browser sends Save-Data: on. Visitors who ask get the light page, and nobody else loses anything.

We found nothing to take off automatically: no oversized images, self-playing video or web fonts.

The site's own JavaScript: left as it is

6.3 KB · 0.05 s at 1 Mbps

We can't cut script automatically without breaking something. Every 100 KB you remove is another 0.8 s at 1 Mbps for the visitor who can least afford it.

// Any server, or a Cloudflare Worker
if (request.headers.get("Save-Data") === "on") {
  // smaller images, video on tap, system fonts
}

See it working on a whole shop: Fair Web, side by side.

Part 3 · Where the weight isEvery file, by type.

TypeFilesBytesShare
Images250.32 MB95%
JavaScript26.3 KB2%
Stylesheets15.2 KB2%
HTML14.4 KB1%
  1. fair.cflare.dev/lite/print-21.avif0.03 MB
  2. fair.cflare.dev/lite/print-23.avif0.03 MB
  3. fair.cflare.dev/lite/hero.avif0.03 MB
  4. fair.cflare.dev/lite/print-14.avif0.02 MB
  5. fair.cflare.dev/lite/print-02.avif0.02 MB

Part 4 · How we weighed itMethod and limits.

  • We fetched the page once, as a phone would ask for it, with no cookies. Images in a srcset are counted at the size a 390 px phone at 2× would pick for the slot its sizes gives.
  • Image savings couldn't be measured this time, so none are claimed: images are counted as they are.
  • Where a server didn't state a file's size, text files are counted at their gzip size, which is what they cost on the wire (brotli would be slightly less).
  • Times are arithmetic: bytes × 8 ÷ 1,000,000. Real slow networks add latency on top.
  • 22 images are lazy-loaded, so they're only fetched if the visitor scrolls that far. We counted them, because they're part of the page.
  • Some text files didn't report a compressed size, so their sizes are approximate (uncompressed).
  • Background images in CSS aren't counted.

Weigh another page