Modern Web in Numbers
Modern web is beyond broken. Even the simplest websites are becoming performance, privacy and accessibility nightmares. And it's only getting worse.
How bloated are popular websites?
Important note: beside the obvious page size problem, TTI (Time To Interactive) is also a huge problem - a lot of websites take way too much time to become interactive (usable). This problem is more pronounced on mobile phones and other slower devices.
Site  | Page Size | JavaScript | CSS | Images | TTI | Score |
|---|---|---|---|---|---|---|
| cnn.com | 3.95 MB 353 requests | 2.85 MB 86 requests | 6.76 KB 1 request | 193.37 KB 74 requests | 35 s | 10 |
| nytimes.com | 3.48 MB 166 requests | 2.12 MB 59 requests | 27.84 KB 7 requests | 265.02 KB 25 requests | 30 s | 24 |
| ebay.com | 1.58 MB 156 requests | 484.59 KB 32 requests | 25.94 KB 3 requests | 797.69 KB 78 requests | 13 s | 35 |
| amazon.com | 1.9 MB 218 requests | 258.53 KB 15 requests | 58.31 KB 8 requests | 1.2 MB 120 requests | 11 s | 47 |
| aliexpress.com | 2.31 MB 248 requests | 1.13 MB 52 requests | 52.64 KB 17 requests | 980.38 KB 91 requests | 22 s | 15 |
| reddit.com | 1.63 MB 76 requests | 605.27 KB 16 requests | 4.58 KB 2 requests | 891.12 KB 36 requests | 10 s | 28 |
Small and fast is beautiful
List of the sites which fit into the above description.
If you have (or know) a site which belongs here, please submit the url here.
| Site | Page Size | JavaScript | CSS | Images | TTI | Score |
|---|---|---|---|---|---|---|
| news.ycombinator.com | 11.91 KB 6 requests | 2.3 KB 1 request | 2.12 KB 1 request | 1.19 KB 3 requests | 1 s | 100 |
| teddit.net | 105.64 KB 27 requests | 0 Bytes 0 requests | 9.6 KB 2 requests | 87.7 KB 24 requests | 1 s | 82 |
| terbium.io | 28.67 KB 5 requests | 0 Bytes 0 requests | 3.9 KB 2 requests | 1.43 KB 1 request | 1 s | 100 |
| nintil.com | 138.4 KB 12 requests | 81.04 KB 3 requests | 11.51 KB 2 requests | 557 Bytes 1 request | 3 s | 94 |
| php.watch | 431.81 KB 12 requests | 13.05 KB 1 request | 8.42 KB 1 request | 390.48 KB 8 requests | 2 s | 97 |
| kmarkiv.com | 35.15 KB 9 requests | 21.11 KB 2 requests | 3.01 KB 1 request | 5.16 KB 3 requests | 2 s | 100 |
| picnicss.com | 41.74 KB 7 requests | 21.37 KB 2 requests | 8.21 KB 1 request | 1.42 KB 1 request | 2 s | 99 |
| macwright.com | 11.57 KB 1 request | 0 Bytes 0 requests | 0 Bytes 0 requests | 0 Bytes 0 requests | 1 s | 100 |
| snestudio.com | 107.88 KB 7 requests | 78.22 KB 2 requests | 7.24 KB 1 request | 18.81 KB 2 requests | 2 s | 93 |
| maxlaumeister.com | 148.02 KB 21 requests | 110.79 KB 7 requests | 5.71 KB 3 requests | 23.01 KB 7 requests | 3 s | 96 |
| htmx.org | 386.95 KB 21 requests | 111.76 KB 9 requests | 9.71 KB 3 requests | 259.32 KB 7 requests | 3 s | 93 |
* HN deserves the special mention here - written in Arc and serving millions of page view daily on a single server
For the reference, here's also betterways.dev's numbers (I still have to optimize a few things):
| Site | Page Size | JavaScript | CSS | Images | TTI | Score |
|---|---|---|---|---|---|---|
| betterways.dev | 8.85 KB 3 requests | 1.67 KB 1 request | 2.12 KB 1 request | 0 Bytes 0 requests | 1 s | 100 |
Quick tips on making the web a better place
Debloat your website and make it accessible
- Start with a clean and semantically correct HTML and progressively enhance it according to your client's capabilities
- Keep your TTI (time to interactive) as low as your can
- Return only minimal Javascript - try to avoid thick SPA frameworks whenever you can (they're breaking the core web principles and the result will always be more bloated and more broken) - see the projects like htmx and webcomponents-based approaches (like Github's Catalyst)
- Return only minimal CSS - you may not need a CSS framework - by using custom CSS, you'll have much better control and understanding of your stylesheets
- Prefer using system font stack over custom fonts
- Don't abuse your client's trust (their privacy, security, resources, etc.)
* Note: the numbers are for reference only; they are periodically refreshed by using PageSpeed Insights (mobile).