/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

An analysis of a NYT article load finds 422 network requests totaling 49MB, triggering a sprawling programmatic ad auction, an example of “hostile architecture”

If active distraction of readers of your own website was an Olympic Sport, news publications would top the charts every time.

Shubham Bose

Context & Ripple Effects

This analysis extends a long-running pattern in related coverage: the Times’ pages were already flagged for slow, data-heavy delivery in an earlier report on news-site loading, while later NYT reporting illustrated how granular the targeting assumptions behind ad delivery can be through a 16-attribute ad-targeting experiment. The new finding makes the infrastructure behind that reader experience unusually visible: a single article load activates hundreds of requests and a broad auction process.

It matters because the reported overhead is not merely a design complaint; it ties the reading experience to the operational demands of programmatic advertising. Related coverage of widespread hidden anti-ad-blocking measures shows how publisher monetization and reader attempts to limit that overhead can become mutually reinforcing.

First-order effects

  • Readers loading the examined NYT article receive 422 network requests and 49MB of traffic, alongside the latency, device-resource use, and on-page complexity that such activity can entail.
  • NYT’s article page immediately exposes the publisher and its advertising partners to a sprawling programmatic auction rather than a simple publisher-to-reader delivery path.

Second-order effects

  • The finding strengthens the practical case for ad blocking and other reader-side controls; prior testing found blockers could materially reduce load times on news sites.
  • A larger auction and request chain increases the importance of ad-tech intermediaries in article delivery, making efforts to simplify pages harder where they could reduce monetization opportunities or measurement capacity.

Third-order effects

  • If this pattern persists, publisher product design will remain constrained by a structural trade-off between direct reader experience and the data- and auction-intensive systems used to monetize attention.
  • The broader outcome may be a sharper split between lighter, subscription-supported experiences and advertising-supported pages whose delivery stacks remain complex; the evidence here identifies the pressure, not which model will prevail.

The trend: News publishing is increasingly defined by the tension between a clean reading product and the expanding technical infrastructure required to sell, target, and measure advertising.

Discussion

  • @leahlibresco Leah Libresco Sargeant on x
    “A user is on paragraph #2. Suddenly, the text jumps down 250 pixels and they lose their place. Why? An ad network finally resolved its bidding process and injected an iframe above the viewport. In Google's Core Web Vitals, this is measured as Cumulative Layout Shift”
  • @leahlibresco Leah Libresco Sargeant on x
    “As a publisher, you can't force a user through 3-4 dismissive actions before content is properly visible and expect the experience to be appreciated. Doing so is equivalent to burning your user's cognitive budget before value is delivered.” https://thatshubham.com/...
  • @shriramk@mastodon.social Shriram Krishnamurthi on mastodon
    This article is rightly making the rounds, but somewhat misses the point.  The Guardian annoys you because you aren't paying.  What is really off here—and the article completely fails to talk about—is what they do to *subscribers*.  I'm already PAYING!  —  https://thatshubham.com…
  • @mitchsaid Mitch Said on bluesky
    nothing better illustrates the desperate search for a media business model like a 50MB web page with a 90:10 ad-to-content ratio
  • @maggie-lee @maggie-lee on bluesky
    There's enough ad/tracking crap on a sample/typical modern news webpage to equal 10-12 songs on an old iPod 🤯  —  Every damn time you just want to read an article, there's a hostile push of enough data at you to be like 10-12 songs of good quality  —  thatshubham.com/blog/news-au…
  • @indyposterboy.scot Colin Dunn on bluesky
    “People are spending less and less time on the web because websites are becoming worse and worse experiences, but the publishers of websites are almost literally trying to dig their way out of that hole by adding more and more of the reader-hostile shit that . .”  —  daringfireba…
  • @hectorjcorrea@mastodon.social Hector Correa on mastodon
    Good read: The 49MB Web Page  —  “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…