Fair Web
Menu

Fair Web · why this matters

The same page doesn't cost everyone the same.

Fair Web serves Halden, a fictional print shop, two ways from one Cloudflare Worker. The full version is built like a typical heavy page, and the lite version is what the server sends when a browser asks for less; the shop, the prices and the buttons are the same in both, and only the weight changes.

8.48 MBfull version, whole page
0.38 MBlite version, whole page
68 s / 3.0 sto download each at 1 Mbps (bytes ÷ bandwidth)

Weights from this build; times are arithmetic.

Part 1 · The normHeavy is normal.

The median mobile web page weighs about 2 MB, one in ten weighs more than 8 MB, and images alone account for around 0.9 MB of the median mobile page (HTTP Archive Web Almanac 2025). We built the full version of Halden to sit at that one-in-ten mark, so what you're looking at is a common page rather than a strawman.

Part 2 · The priceBytes are not priced equally.

On fast, unmetered fibre an 8 MB page costs about a second and nothing else, but on a slow or prepaid connection it costs a minute and a real share of a data bundle. The ITU found that people in low-income economies spend about 22 times more of their income on a standard mobile broadband plan than people in high-income economies, and people in lower-middle-income economies about 7 times more (ITU, Facts and Figures 2025). So the same design decision, whether it's an autoplaying video or an oversized photo, is a rounding error for one visitor and a bill for another, and that imbalance is what we mean by an unfair web.

Part 3 · The askLevelling the field starts with asking.

Browsers already have a way to ask for less: they can send Save-Data: on with every request, and a server that listens can answer with a lighter page. This one does, which is why the shop sends the lite version automatically when the header arrives. The catch is that very few browsers send it. Only Chromium-based browsers support it (caniuse); Chrome removed its main trigger, Lite mode, in Chrome 100 in 2022 (The Register); and Safari on iPhone doesn't send it, even in Low Data Mode. You can check what your browser sends, and if it doesn't, the Simulate Save-Data switch adds the header from inside your browser, so the server makes exactly the decision it would for a browser that asks and labels it as simulated.

Part 4 · The fixWhat the lite version changes.

The lite version keeps the content, the layout and every button, and it takes nothing away that you can't get back with one tap:

  • Video on request: a still image instead of the 2.3 MB hero video, with a button to play it.
  • Smaller photos: AVIF at the size the screen shows, with a "view full resolution" button on product pages.
  • Images as you scroll: prints below the fold load only when you reach them.
  • The fonts you already have: no web font downloads.
  • No speculative loading (see below).

Part 5 · The trade-offFast tricks have a price.

The full version uses speculation rules to prerender product pages before you open them: on hover on desktop, and for links on screen once you stop scrolling on mobile (Chrome's moderate setting). When you tap, the page is already there, which feels instant and is paid for in bytes, including bytes for pages you never open; the meter's Speculative figure counts them. Browsers already treat this as a luxury: Chrome doesn't prerender when Save-Data is on (Chrome for Developers), and prefetching doesn't happen when the device is in Data Saver mode (MDN), so the lite version follows the same rule.

Part 6 · The buildHow it's built.

  • One Cloudflare Worker reads Save-Data and picks the version, and a /full or /lite URL overrides the header.
  • Each version's files live under their own path, so no cache can mix them up, and the page is marked Vary: Save-Data.
  • Everything is sent with no-store, so the meter counts real downloads, not cache hits.
  • The meter reads the browser's own network timing for bytes, and the web-vitals library for LCP, INP, FCP and TTFB.
  • For images alone, Cloudflare Images can do this per request: its slow-connection quality setting applies a lower quality when the browser sends Save-Data or reports a slow connection (Chromium browsers only) (docs).

Part 7 · The limitsWhat this demo doesn't show.

  • Timings are measured on your connection. On fast Wi-Fi both versions load in about a second; the difference shows up in bytes, not in what you see.
  • The "at 1 Mbps" figure is arithmetic (bytes × 8 ÷ 1,000,000), not a measurement. Real slow networks add latency on top.
  • The side-by-side view loads both versions at once over one connection, so its timings are indicative.
  • Cloudflare Web Analytics on this domain adds a small script to each page that the meter can't measure. It's the same for both versions.

If you build websites, the fix is within reach today: listen for Save-Data, weigh your pages, and give people the choice. That's how we level the field.

Sources and credits.