Average web page size increased 15% in 2014 to almost 2MB; HTTP requests per page hardly changed at 95
Average Page Weight Increases 15% in 2014 — The HTTP Archive Report collates information from almost half a million of the web's most popular websites.
Context & Ripple Effects
The HTTP Archive's annual crawl of roughly half a million popular sites shows pages getting heavier without multiplying parts: average weight climbed 15% in 2014 to almost 2MB while the per-page HTTP request count stayed pinned near 95. That split matters because it isolates where the bloat lives — not in more files, but in bigger ones, typically images and scripts shipped with each existing request.
This lands mid-arc in a decade of accumulating weight: six months later Monday Note documented news pages following the same curve, with the New York Times needing four minutes and 2MB just to load one story news sites are getting slower, and by late 2020 the protocol itself had been rebuilt around the problem, when HTTP/2 overtook HTTP/1.1 across the top million pages HTTP/2 overtook HTTP/1.1 on top pages.
First-order effects
- Visitors on metered or slow connections absorb the cost directly: each page view now transfers roughly 15% more bytes than a year earlier for the same number of round trips.
- Publishers shipping those heavier assets face rising bandwidth bills per visit even as their request counts — the metric most caching and optimization tooling was built around — stay flat.
Second-order effects
- Flat request counts against growing payload sizes redirect optimization effort from reducing the number of files toward shrinking what travels inside them — compression, image formats, and script trimming become the battleground.
- Protocol-level fixes gain urgency: multiplexing many requests over one connection, the change that eventually made HTTP/2 dominant by 2020, attacks exactly the latency penalty that ~95 requests per page imposes.
Third-order effects
- If weight keeps compounding annually while request counts stagnate, the web's performance problem structurally shifts from connection overhead to payload discipline, pushing tooling, protocols, and developer norms toward per-byte rather than per-request accountability.
The trend: Web pages have grown steadily heavier year over year even as their structure stays static, making payload size — not request count — the defining constraint of web performance.