Open a busy news page on a phone and watch the little progress bar crawl. By the time it settles you’ve pulled down something like four megabytes — call it a short film’s worth of data — to look at a screen of text you could read aloud in ninety seconds. The headlines, the actual news, the reason you tapped the link, are a few dozen kilobytes buried at the very bottom of that bill. Everything above them is freight. You paid to haul it, and none of it was what you wanted.
That ratio is not an accident or a bug. It’s the shape of the modern web page, and once you’ve seen it you can’t unsee it: the information is the smallest line item on the manifest, and the manifest is enormous.
The payload has a table of contents, and the news is at the bottom
Itemize what those megabytes are and the story tells itself. Near the top: ad networks and real-time exchanges, a swarm of scripts bidding on your attention before the page has even drawn. Then the tracking — analytics, pixels, session recorders, each one small and there being a dozen of them. Then the media: a hero image sized for a desktop monitor, a video that autoplays muted whether or not you’ll ever watch it. Then the fonts, three or four weights of a typeface, each a full download. Then a framework and a fistful of widgets, an entire rendering engine shipped to lay out what is, in the end, mostly words.
And then, right at the bottom of the bill, in a font you have to squint to find on the invoice: the headlines. The one thing the page exists to deliver is the one thing that weighs almost nothing — because text, it turns out, is astonishingly cheap. It’s everything wrapped around the text that costs, and almost all of it is there to serve someone who is not you.
Weight is not a cosmetic problem. It’s whether the page opens.
On a desktop on a fast connection, all that freight is invisible — it arrives in a blink and you never feel the cost. This is exactly why it accumulates: the people building the page are testing it on the machine where the weight doesn’t show. But move to where the reading actually happens — a phone, a train, two bars of signal, a battery you’re rationing — and weight stops being invisible. Weight becomes time. Time becomes the little decision every reader makes without noticing: keep waiting, or give up and close the tab.
A megabyte you didn’t need is a second you didn’t have. On a phone, on a bad connection, that second is the whole difference between a page you read and a page you abandoned.
A news reader you have to wait for stops getting opened. Not consciously — nobody decides to stop checking a site — but the habit quietly erodes, one slow load at a time, until the app that was heavy is simply the app you don’t reach for anymore. DReader is fast on purpose because fast and gets opened are the same property measured a day apart. The weight was never a polish item to get to later. It was the product.
You can’t diet your way to light
The obvious move, if you cared about this, would be to take the heavy page and put it on a diet: compress the images, defer the scripts, lazy-load below the fold, shave a megabyte here and there. Teams do this, and it helps, and it never gets you close — because the weight isn’t fat you can trim off a healthy page. It’s structural. The ad exchange isn’t an accident of engineering; it’s the reason the page can afford to exist. The trackers aren’t sloppiness; they’re the business model, rendered as network requests. Optimize all you like and you’re still carrying the load, just carrying it more efficiently.
DReader isn’t a lighter version of that page. It’s a different object that happens to surface the same headlines. It’s light because it ships the information and nothing that monetizes it — no exchange, no pixel, no autoplay, no framework standing between you and the words. This is the same discipline as everything else we build small: the weight didn’t come off because we were clever about compression. It came off because the reasons for the weight were never ours to begin with. Subtraction, again — the restraint that is the whole product.
Why a studio bothers to weigh things
We only build things we run ourselves, and operating a reader on a real phone on a real bad connection is where you learn, viscerally, that a kilobyte is a unit of patience. You feel every one of them on the platform with no signal. That’s not a lesson you get from a Lighthouse score in a quiet office; it’s a lesson you get from being your own most impatient user.
The same instinct runs under the fastest page on this site and under reading a source that offers no feed: ship the thing someone actually needs, refuse to carry the thing they don’t. The headline was the lightest thing on the page. It was also the only thing you came for. Everything else was weight somebody else asked you to hold — and putting it down turned out to be the entire feature.