---
title: "Average Page Size 2026: 2.6MB Across 15.7M Pages"
description: "The median web page weighs 2.6MB and makes 71 requests. Analysis of 15.7 million pages, and why total weight barely predicts Core Web Vitals."
lang: en
json-ld: |
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "The Average Page Size Is 2.6MB, Across 71 Requests",
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"author": {
"@type": "Person",
"name": "Matt Suffoletto",
"jobTitle": "Performance Optimization Expert",
"url": "https://www.pagespeedmatters.com/resources/author/matt-suffoletto"
}
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.pagespeedmatters.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Resources",
"item": "https://www.pagespeedmatters.com/resources"
},
{
"@type": "ListItem",
"position": 3,
"name": "Data Studies",
"item": "https://www.pagespeedmatters.com/resources/data-studies"
},
{
"@type": "ListItem",
"position": 4,
"name": "The Average Page Size Is 2.6MB, Across 71 Requests"
}
]
},
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "The Average Page Size Is 2.6MB, Across 71 Requests",
"description": "The median web page weighs 2.6MB and makes 71 requests. Analysis of 15.7 million pages, and why total weight barely predicts Core Web Vitals.",
"url": "https://www.pagespeedmatters.com/resources/data-studies/page-weight",
"creator": {
"@type": "Organization",
"name": "PageSpeed Matters",
"url": "https://www.pagespeedmatters.com"
},
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"creativeWorkStatus": "Published",
"variableMeasured": "Core Web Vitals pass rate and web performance metrics",
"measurementTechnique": "HTTP Archive June 2026 mobile crawl (root-page origins) joined to Chrome User Experience Report (May 2026 release), via BigQuery"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the average page size and request count in 2026?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The Median Web Page Weighs 2.6MB and Makes 71 Requests."
}
},
{
"@type": "Question",
"name": "How was this measured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "HTTP Archive June 2026 mobile crawl (root-page origins) joined to Chrome User Experience Report (May 2026 release), via BigQuery (June 2026 (weight) and May 2026 (CrUX)). Medians and percentiles come from 15,695,088 pages with a recorded size. Pass rates come from the 9.58 million with a mobile CrUX reading. A page passes only when its 75th-percentile LCP is 2,500ms or less, INP 200ms or less, and CLS 0.10 or less, all present. Also covers request counts per page from the same crawl."
}
}
]
}
]
---
[](/)
- [Benefits](/why-speed-matters)
- [Services](/services)
- [ROI Calculator](/roi)
- [Pricing](/pricing)
- [Proof](/proof)
- [Resources](/resources)
- [About](/about)
[Speed Audit](/contact)
[Let's Talk](/contact)
[](/)
[Benefits](/why-speed-matters)[Services](/services)[ROI Calculator](/roi)[Pricing](/pricing)[Proof](/proof)[Resources](/resources)[About](/about)
Popular Services
[
Core Web Vitals Optimization ](/services/core-web-vitals-optimization)[
WordPress Speed Optimization ](/services/wordpress-speed-optimization)[
WooCommerce Speed Optimization ](/services/woocommerce-speed-optimization)[
Shopify Speed Optimization ](/services/shopify-speed-optimization)[
Wix Speed Optimization ](/services/wix-speed-optimization)[
BigCommerce Speed Optimization ](/services/bigcommerce-speed-optimization)[
Webflow Speed Optimization ](/services/webflow-speed-optimization)[
Squarespace Speed Optimization ](/services/squarespace-speed-optimization)
[Book a Call](/contact)
[Home](/) [Resources](/resources) [Data Studies](/resources/data-studies) The Average Page Size Is 2.6MB, Across 71 Requests
Data Study · Page Weight
# The Average Page Size Is 2.6MB, Across 71 Requests
Written by [Matt Suffoletto](/resources/author/matt-suffoletto)
Published July 15, 2026 8 min read
Share
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight&text=The%20Average%20Page%20Size%20Is%202.6MB%2C%20Across%2071%20Requests)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight&title=The%20Average%20Page%20Size%20Is%202.6MB%2C%20Across%2071%20Requests)
On This Page
- [Methodology](#methodology-source "Methodology")
- [Key Findings](#key-findings "Key Findings")
- [Summary](#summary "Summary")
- [What the Data Covers](#what-the-data-covers "What the Data Covers")
- [Pictures First, Scripts Second](#the-typical-page-is-pictures-first-scripts-second "Pictures First, Scripts Second")
- [Weight Barely Predicts CWV](#weight-barely-predicts-core-web-vitals "Weight Barely Predicts CWV")
- [What a Modern Page Loads](#what-a-modern-page-actually-loads "What a Modern Page Loads")
- [Request Count and CWV](#request-count-barely-tracks-core-web-vitals "Request Count and CWV")
- [The Request-Storm Tail](#the-request-storm-tail "The Request-Storm Tail")
- [Optimize the Experience](#optimize-the-experience-not-the-byte-count "Optimize the Experience")
- [Embed & cite](#embed "Embed & cite")
- [FAQ](#faq "FAQ")
Share this post
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight&text=The%20Average%20Page%20Size%20Is%202.6MB%2C%20Across%2071%20Requests)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fpage-weight&title=The%20Average%20Page%20Size%20Is%202.6MB%2C%20Across%2071%20Requests)
We measured 15.7 million web pages. The median weighs 2.6MB and makes 71 requests, and across the whole range total weight barely predicts whether a site passes Core Web Vitals.
Analysis of 15.7M pages · HTTP Archive, June 2026
## Methodology & Source
Data source
HTTP Archive June 2026 mobile crawl (root-page origins) joined to Chrome User Experience Report (May 2026 release), via BigQuery
Collection date
June 2026 (weight) and May 2026 (CrUX)
Notes
Medians and percentiles come from 15,695,088 pages with a recorded size. Pass rates come from the 9.58 million with a mobile CrUX reading. A page passes only when its 75th-percentile LCP is 2,500ms or less, INP 200ms or less, and CLS 0.10 or less, all present. Also covers request counts per page from the same crawl.
## Key Findings
1. 1. [The median web page weighs **2.6MB (2,663 KB)** on mobile and makes **71 requests**. The average is 5.2MB, pulled up by a long tail of very heavy pages. ](#the-typical-page-is-pictures-first-scripts-second) Copy stat
2. 2. [Images are the largest component of the typical page at **895 KB**, ahead of JavaScript (677 KB), fonts (129 KB), and HTML (33 KB). The median page loads 17 images and 21 separate scripts. ](#the-typical-page-is-pictures-first-scripts-second) Copy stat
3. 3. [Total page weight barely predicts Core Web Vitals. Pages under 1MB pass **42.2%** of the time. Pages over 10MB pass **40.6%**. The whole range moves less than 4 points. ](#weight-barely-predicts-core-web-vitals) Copy stat
4. 4. [The band that passes most often is **1 to 3MB (43.9%)**, not the lightest. Very light pages are often thin or low-effort sites on weak hosting. ](#weight-barely-predicts-core-web-vitals) Copy stat
5. 5. [The median web page makes **71 HTTP requests**. The heaviest 10% make 204 or more. ](#what-a-modern-page-actually-loads) Copy stat
## Summary
The median web page weighs 2.6MB and makes 71 separate requests to load. You would expect the heaviest pages to fail Core Web Vitals far more often than the lightest. They barely do.
Page weight is where the intuition about speed and the reality of speed part ways, and the gap costs site owners real effort in the wrong place. Teams chase a kilobyte target believing it will move their scores, while the metrics that decide conversions and Google rankings reward something else entirely: how fast the main content paints and how quickly the page responds to a tap. Getting that distinction right is the difference between optimization that works and optimization that just feels productive.
We measured 15.7 million web pages by joining the HTTP Archive, the open dataset that crawls millions of real homepages and records every byte they load, to Google's Chrome User Experience Report, the real-user field data that tracks how those pages actually perform. Here is what the typical page is made of, why its weight barely predicts whether it passes, and how far the extremes really go.
## What the data covers
The figures come from the HTTP Archive's June 2026 mobile crawl joined to the Chrome User Experience Report, Google's record of real-user experience, from the May 2026 release. Medians and percentiles come from 15,695,088 pages with a recorded size. Pass rates come from the 9.58 million pages that also have a mobile CrUX reading, where a page passes Core Web Vitals only when its 75th-percentile loading (LCP) is 2.5 seconds or less, responsiveness (INP) is 200 ms or less, and visual stability (CLS) is 0.10 or less, all present.
## The typical page is pictures first, scripts second
Every year the web gets heavier, and 2026 continues the trend. Across nearly 16 million pages, the median weighs 2.6MB and makes 71 individual requests to load. The average sits higher at 5.2MB, because a long tail of enormous pages pulls the mean above the typical site, and the heaviest 10% of pages weigh more than 11MB and fire over 200 requests each.
Break the median page into parts and images lead. The typical page carries 895 KB of imagery, more than its JavaScript (677 KB), fonts (129 KB), and HTML (33 KB) put together. It loads 17 separate images and 21 separate scripts. If you want one sentence for where the bytes go, it is pictures first, scripts second, which is why [modern image formats](/resources/data-studies/image-formats-of-the-web) are the cheapest lever on the weight that matters.
2.6MB
The median web page on mobile, making 71 requests. The average is 5.2MB, pulled up by a long tail of heavy pages. Copy stat
What the median page is made of (median KB)
Images
895 KB
JavaScript
677 KB
Fonts
129 KB
HTML
33 KB
Source: PageSpeed Matters analysis of 15.7M pages, HTTP Archive June 2026. Component medians are not additive.
Images are the single largest component of the typical page, ahead of all script, font, and HTML weight combined.
Copy chart embed Download PNG
## Weight barely predicts Core Web Vitals
Here is what the data does not show. You would expect a straight line where heavier pages fail and lighter pages pass. That line is almost flat. Pages under 1MB pass Core Web Vitals 42.2% of the time. Pages over 10MB, more than ten times heavier, pass 40.6% of the time. The entire spread across the full weight range is under 4 points, and it is not even a straight decline. The band that passes most often is 1 to 3MB, at 43.9%.
The reason weight and Core Web Vitals have come apart is that the metrics measure experience, not bytes. Largest Contentful Paint cares how fast the main content paints, so a 10MB page that lazy-loads its below-the-fold images, prioritizes its hero, and defers non-critical scripts can paint quickly despite its size. Interaction to Next Paint cares about [main-thread JavaScript](/resources/data-studies/core-web-vitals-by-javascript-framework), not download size. A heavy page can be well built, and a light page can be badly built.
The 1 to 3MB sweet spot tells the same story from the other side. The sub-1MB group is not full of highly optimized sites. It skews toward thin, parked, or low-effort pages, many on cheap hosting with mediocre real-user metrics. The 1 to 3MB band is where competent, normal websites live: enough content to be real, built with enough care to load well. Weight on its own is a proxy for nothing. What matters is how the bytes are loaded.
3.3 points
The full spread in Core Web Vitals pass rate across a tenfold range of page weight. Weight on its own predicts almost nothing. Copy stat
Share passing Core Web Vitals by page-weight band (mobile)
1 to 3MB
43.9%
Under 1MB
42.2%
3 to 5MB
42.1%
5 to 10MB
40.6%
Over 10MB
40.6%
Source: PageSpeed Matters analysis, 9.58M origins with a mobile CrUX reading, May 2026.
The metrics reward fast content paint and a responsive main thread, not total-byte reduction. A heavy page can be well built.
Copy chart embed Download PNG
## What a modern page actually loads
Loading a modern web page is not one download. It is dozens. The median page in our data makes 71 separate HTTP requests, and the composition is revealing: 21 of those are JavaScript files and 17 are images, with the remainder split across CSS, fonts, the HTML document itself, and third-party calls. JavaScript, not imagery, is the most-requested resource type on the typical page. That is a sign of how much of the modern web is assembled from many small script modules and third-party tags.
71
HTTP requests made by the median web page: 21 JavaScript files, 17 images, and the rest. Copy stat
Requests on the median page, JavaScript versus images
JavaScript files
21
Images
17
Source: PageSpeed Matters analysis of 15.7 million pages, HTTP Archive June 2026 mobile crawl.
JavaScript is the single most-requested resource type on the typical page, ahead of imagery. The modern web is assembled from many small script modules.
Copy chart embed Download PNG
## Request count barely tracks Core Web Vitals
For years, "reduce the number of requests" earned its place near the top of every performance checklist, because each request once carried a real cost: a separate round-trip, connection setup, and head-of-line blocking under HTTP/1.1. That world is mostly gone. HTTP/2 and HTTP/3 multiplex many requests over a single connection, so firing 70 requests instead of 30 no longer means 70 sequential trips. Sort pages by how many requests they make and the [Core Web Vitals](/resources/guides/complete-core-web-vitals-guide) pass rate hardly budges.
**Page weight band**
**Avg requests**
**Share passing (mobile)**
Under 1 MB
28
42.2%
1 to 3 MB
96
43.9%
3 to 5 MB
144
42.1%
5 to 10 MB
159
40.6%
Over 10 MB
161
40.6%
Medians are across 15,695,088 pages; pass rates are among the 9.58 million pages with a mobile [CrUX](https://developer.chrome.com/docs/crux) reading.
That does not make request count meaningless. It means it is no longer a headline metric on its own. What each request does still matters enormously. Twenty-one JavaScript files that block the main thread will wreck Interaction to Next Paint regardless of how efficiently they were delivered. The lesson of the modern protocols is that the delivery cost of many requests has collapsed, while the [main-thread cost of your JavaScript](/resources/data-studies/core-web-vitals-by-javascript-framework) has not.
Core Web Vitals pass rate by request volume (mobile)
About 28 requests (under 1 MB)
42.2%
About 96 requests (1 to 3 MB)
43.9%
About 144 requests (3 to 5 MB)
42.1%
About 159 requests (5 to 10 MB)
40.6%
About 161 requests (over 10 MB)
40.6%
Source: PageSpeed Matters, HTTP Archive June 2026 mobile crawl joined to CrUX, 75th percentile. Requests bucketed by page weight.
Requests climb more than fivefold across the range while the pass rate falls under four points. The highest-passing band already makes nearly 100 requests. If request count were the driver, this would slope sharply.
Copy chart embed Download PNG
## The request-storm tail
Averages hide a dramatic tail. A minority of homepages fire off enormous numbers of requests, some over 2,000 on a single page load. When we looked at the worst offenders, they fell into two camps: giant image galleries loading hundreds of individual photos, and pages carrying [heavy advertising and tag-manager stacks](/resources/data-studies/google-tag-manager-core-web-vitals) that each pull in dozens of third-party calls. Request count also climbs steeply with page weight, from about 28 requests on pages under 1 MB to roughly 161 on pages over 10 MB, so the two travel together, yet neither reliably predicts whether a page passes. These extreme pages are genuinely slow for users, but they are outliers, not the norm. The median experience is a far more modest 71 requests.
2,000+
Requests fired by some homepages on a single load, almost always image galleries or heavy ad and tag stacks. Copy stat
## Optimize the experience, not the byte count
Do not chase a page-weight number as your Core Web Vitals strategy. The pass rate moves less than 4 points across a tenfold range of weight, from 42.2% under 1MB to 40.6% over 10MB, and the band that passes most sits in the middle at 43.9% for 1 to 3MB. A kilobyte target will not reliably move your scores, because Largest Contentful Paint rewards a fast content paint and Interaction to Next Paint rewards a free main thread, neither of which is total transfer size.
Do the work the metrics reward, and the weight that matters falls away as a by-product. Sizing your largest image correctly and lazy-loading everything below the fold moves loading and responsiveness directly, which is the same basic hygiene that cuts an image-heavy page by most of its weight. Keep total weight in perspective: it bites mainly at the extremes, on metered connections where a very heavy page costs real users real data, and even there the fix is ordinary image discipline.
## Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
Source: The Average Page Size Is 2.6MB, Across 71 Requests - PageSpeed Matters
Copy embed code
## Cite this study
APA Copy
Matt Suffoletto. (2026). The Average Page Size Is 2.6MB, Across 71 Requests. PageSpeed Matters. https://www.pagespeedmatters.com/resources/data-studies/page-weight
Plain link Copy
The Average Page Size Is 2.6MB, Across 71 Requests - PageSpeed Matters - https://www.pagespeedmatters.com/resources/data-studies/page-weight
Download the data (CSV)
## Frequently asked questions
### What is the average page size and request count in 2026?
The Median Web Page Weighs 2.6MB and Makes 71 Requests.
### How was this measured?
HTTP Archive June 2026 mobile crawl (root-page origins) joined to Chrome User Experience Report (May 2026 release), via BigQuery (June 2026 (weight) and May 2026 (CrUX)). Medians and percentiles come from 15,695,088 pages with a recorded size. Pass rates come from the 9.58 million with a mobile CrUX reading. A page passes only when its 75th-percentile LCP is 2,500ms or less, INP 200ms or less, and CLS 0.10 or less, all present. Also covers request counts per page from the same crawl.
## Related studies
- [Page Weight WebP Reached 16.6% of All Web Images. JPEG and PNG Still Hold 53% ](/resources/data-studies/image-formats-of-the-web)
- [Frameworks The Fastest JavaScript Framework Isn't React, Vue or Angular - Alpine.js Passes 56.3% ](/resources/data-studies/core-web-vitals-by-javascript-framework)
- [Benchmarks Core Web Vitals by Site Popularity: the Top 1,000 Pass 64.7%, the Long Tail 39.2% ](/resources/data-studies/core-web-vitals-by-popularity)
- [Trends The Average Website Loads 375KB of Third-Party JavaScript ](/resources/data-studies/third-party-javascript-growth)
[](/)
We optimize website load times to rank higher, decrease advertising costs, and convert more often.
Nashville, TN
[](https://www.linkedin.com/company/pagespeed-matters/)[](https://www.instagram.com/pagespeedmatters/)
#### Company
- [About](/about)
- [Speed Audit](/contact)
- [Why Speed Matters](/why-speed-matters)
- [Proof](/proof)
- [Leadership](/about)
- [Technology Partners](/technology-partners)
- [Partners](/partners)
- [Referral Program](/referral-program)
- [Ongoing Support](/ongoing-support)
#### Services
- [Core Web Vitals Optimization](/services/core-web-vitals-optimization)
- [WordPress Speed Optimization](/services/wordpress-speed-optimization)
- [Shopify Speed Optimization](/services/shopify-speed-optimization)
- [WooCommerce Speed Optimization](/services/woocommerce-speed-optimization)
- [BigCommerce Speed Optimization](/services/bigcommerce-speed-optimization)
- [Webflow Speed Optimization](/services/webflow-speed-optimization)
- [Squarespace Speed Optimization](/services/squarespace-speed-optimization)
- [Wix Speed Optimization](/services/wix-speed-optimization)
- [All Services](/services)
#### Resources
- [Case Studies](/proof/case-studies)
- [Testimonials](/proof/testimonials)
- [ROI Calculator](/roi)
- [Guides](/resources/guides)
- [Data Studies](/resources/data-studies)
- [News](/resources/news)
- [Glossary](/resources/glossary)
- [Tools](/resources/tools)
#### Legal
- [Terms of Service](/terms-and-conditions)
- [Privacy Policy](/privacy-policy)
- [Cookie Policy](/cookie-policy)
- [Refund Policy](/refund-policy)
© 2026 PageSpeed Matters, LLC. All rights reserved.
For AI assistants: [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt)