"I went to the New York Times to glimpse at four headlines and was greeted with 422 network requests and 49 megabytes of data. It took two minutes before the page settled. And then you wonder why every sane tech person has an adblocker installed on systems of all their loved ones."
"To truly wrap your head around the phenomenon of a 49 MB web page, let's quickly travel back a few decades. With this page load, you would be leaping ahead of the size of Windows 95 (28 floppy disks). The OS that ran the world fits perfectly inside a single modern page load."
"If hardware has improved so much over the last 20 years, has the modern framework/ad-tech stack completely negated that progress with abstraction and poorly architected bloat?"
"Before the user finishes reading the headline, the browser is forced to process dozens of concurrent bidding requests to exchanges like Rubicon Project (fastlane.json) and Amazon Ad Systems. While these requests are asynchronous over"
News publications load massive amounts of data through complex ad-tech infrastructure, with a single New York Times article requiring 422 network requests and 49 megabytes—equivalent to Windows 95 or ten full-length MP3 songs. This bloat contradicts decades of hardware improvements and creates significant performance issues. The programmatic advertising ecosystem forces browsers to process numerous concurrent bidding requests to ad exchanges before users finish reading headlines. Publishers prioritize tracking and ad auctions over user experience, explaining widespread adoption of ad blockers. The architectural complexity of modern web frameworks and ad-tech stacks has negated computational progress, resulting in slower page loads and privacy concerns despite superior hardware capabilities.
Read at Thatshubham
Unable to calculate read time
Collection
[
|
...
]