Page weight & requests

Every request the page makes on a cold load: request count and total transfer size over the wire.

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · All devices field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Page weight & requests

Every request the page makes on a cold load: request count and total transfer size over the wire.

72
request count
on the typical page
2.5 MB
page weight
on the typical page
4.7 MB
1 in 4 pages exceed this
page weight
94,910
sites measured
all-device field data

The typical page weighs 2.5 MB across 72 requests.

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
2

Distribution & median INP site count and median INP at each level of page weight & requests — n

0ms 63ms 125ms 188ms 250ms
200ms
0 13887 27773
0 1–2 3 4–6 7–11 12–19 20–34 35–62 63–112 113–202 203–365 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
3

Passing INP by page weight & requests — n which level passes the INP most often

Page weight & requests — nSitesPassing INPINP
1–2 1,124 87% 87ms
3 248 79% 110ms
4–6 728 86% 96ms
7–11 1,292 84% 85ms
12–19 3,406 89% 81ms
20–34 10,425 94% 78ms
35–62 23,047 96% 81ms
63–112 27,773 96% 87ms
113–202 17,897 95% 92ms
203–365 7,089 95% 95ms
>p98 1,878 90% 115ms
Good Needs Improvement Poor Faded rows: under 100 sites

Page weight & requests — n 72. p75 122. p99 436. At the low end (1–2): INP 87ms. At the high end (>p98): INP 115ms. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
4

Distribution & median INP site count and median INP at each level of page weight & requests — size

0ms 63ms 125ms 188ms 250ms
200ms
0 20968 41935
0 0.1–0.346 0.346–1.2 1.2–4.15 4.15–14.4 14.4–49.8 49.8–172 172–596 596–2065 2065–7149 7149–24753 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
5

Passing INP by page weight & requests — size which level passes the INP most often

Page weight & requests — sizeSitesPassing INPINP
0 150 93% 94ms
0.1–0.346 193 93% 88ms
0.346–1.2 440 88% 86ms
1.2–4.15 368 82% 94ms
4.15–14.4 266 86% 91ms
14.4–49.8 526 80% 106ms
49.8–172 1,080 79% 90ms
172–596 5,619 90% 79ms
596–2065 30,318 96% 81ms
2065–7149 41,935 96% 88ms
7149–24753 12,119 95% 91ms
>p98 1,896 94% 94ms
Good Needs Improvement Poor Faded rows: under 100 sites

Page weight & requests — size 2.5 MB. p75 4.7 MB. p99 34.1 MB. At the low end (0 KB): INP 94ms. At the high end (>p98): INP 94ms. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
6

Why this matters for the Core Web Vitals, and where to start fixing it

Page weight is a bandwidth problem. The network can only move so many bytes per second and every resource on the page competes for that capacity. The LCP image does not load alone. It shares bandwidth with every script, stylesheet and tracking pixel that loads at the same time. A heavier page means the main content arrives later.

Request count matters next to the bytes. Every request adds queueing and scheduling overhead. On a busy connection important requests wait behind unimportant ones. Script bytes keep costing after the download. The main thread has to parse and execute them, and that delays interactions (INP). The resource type breakdown shows where the bytes sit.

How does page weight affect the Core Web Vitals?

Page weight & requests correlate with the LCP. Page weight separates passing sites from failing sites more than request count does. Where the page weight is low, 83% of sites pass the LCP. Where it is high, 73% do. The decline is gradual. There is no point where sites suddenly start failing.

Related signals Cookies per site → Stylesheet initiator → Script coverage (used vs unused) → font-display strategy → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured