Why Web Pages Are Growing Too Big—and How to Stop It

An analysis of four years of HTTP Archive data reveals that average web pages have more than doubled in size, with images now accounting for 64% of weight, and offers practical steps like performance budgets, image and font optimization, and third‑party script management to curb bloat.

21CTO
21CTO
21CTO
Why Web Pages Are Growing Too Big—and How to Stop It

Every six months I review key statistics from HTTP Archive, a valuable historical data repository covering the top 500,000 websites worldwide.

Average page size has jumped from 991 KB to 2,219 KB

Last spring the average page crossed the 2 MB threshold, reaching 2,099 KB. Today pages are 16 % larger than a year ago and 139 % larger than four years ago. In the past six months the average grew by another 120 KB, reflecting more images, CSS, scripts, and higher performance risk.

Page size growth chart
Page size growth chart

Images now make up 64 % of page weight

Images have long been a major component of page size, consistently accounting for around 60 % of the total. Their growth rate is astonishing: total image payload has more than doubled in four years, and today images alone weigh more than the entire average page did two years ago.

Size isn’t the whole story

“The secret lies in ‘page weight’—the total file size plus all sub‑resources (images, CSS, JS, etc.)—but that’s not the real problem. Bandwidth isn’t the issue; latency is.” “Most web pages now load around a hundred resources from dozens of different servers, many of which are unoptimized, unmeasured, and unsupervised, creating unpredictable performance.”

Custom fonts illustrate this point: their share has risen from under 7 % to over 50 % of page weight in just a few years. While fonts give designers control over branding, poorly implemented or externally hosted fonts can cause flash‑of‑unstyled‑text or even block page rendering.

Other resources—stylesheets, JavaScript, and numerous third‑party tags—add latency and can become single points of failure.

Custom font impact chart
Custom font impact chart

What can you do about it?

1. Set a performance budget

Many fast sites keep page size under 1 MB. A performance budget forces teams to prioritize and prune resources, reducing latency.

2. Optimize images first

Image optimization yields quick wins. Refer to Guy Podjarny’s “High Performance Images: Beautiful Shouldn’t Mean Slow” for a practical checklist.

3. Optimize fonts

Read Ilya Grigorik’s guide on web‑font optimization for developers and designers.

4. Gain control over third‑party scripts

A typical page may load 75+ third‑party scripts. Understanding their impact is essential; a short intro guide can help you audit them.

5. Educate everyone who touches the web

From CEOs to marketers, all decisions—adding a new widget or using a GIF—affect performance.

6. Understand the business impact of page size and complexity

Link page size, complexity, load time, and business metrics to identify where optimization effort yields the greatest ROI. See my short article on web performance’s effect on business and the WPO statistics repository for deeper insight.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

frontendimage-optimizationPage SizeFont Optimization
21CTO
Written by

21CTO

21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.