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 Q2 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.

71
request count
on the typical page
2.3 MB
page weight
on the typical page
4.5 MB
1 in 4 pages exceed this
page weight
185,271
sites measured
all-device field data

The typical page weighs 2.3 MB across 71 requests.

The State of Web Vitals · Q2 2026 · 189,915 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 26495 52990
0 1–2 3 4–6 7–11 12–19 20–35 36–62 63–112 113–203 204–366 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 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 2,280 85% 88ms
3 1,692 81% 96ms
4–6 4,413 89% 89ms
7–11 2,565 85% 84ms
12–19 6,527 90% 82ms
20–35 21,342 94% 79ms
36–62 42,096 96% 81ms
63–112 52,990 96% 87ms
113–203 34,303 95% 91ms
204–366 13,375 95% 95ms
>p98 3,683 90% 116ms
Good Needs Improvement Poor Faded rows: under 100 sites

Page weight & requests — n 71. p75 120. p99 439. At the low end (1–2): INP 88ms. At the high end (>p98): INP 116ms. computed

The State of Web Vitals · Q2 2026 · 189,915 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 40094 80188
0 0.1–0.346 0.346–1.2 1.2–4.14 4.14–14.3 14.3–49.6 49.6–172 172–593 593–2053 2053–7104 7104–24579 >p98
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 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 9,187 92% 87ms
0.1–0.346 362 93% 87ms
0.346–1.2 869 86% 87ms
1.2–4.14 737 80% 100ms
4.14–14.3 602 89% 87ms
14.3–49.6 1,041 81% 103ms
49.6–172 2,101 80% 87ms
172–593 10,655 90% 79ms
593–2053 57,127 96% 81ms
2053–7104 80,188 96% 88ms
7104–24579 23,431 95% 92ms
>p98 3,615 94% 94ms
Good Needs Improvement Poor Faded rows: under 100 sites

Page weight & requests — size 2.3 MB. p75 4.5 MB. p99 33.3 MB. At the low end (0 KB): INP 87ms. At the high end (>p98): INP 94ms. computed

The State of Web Vitals · Q2 2026 · 189,915 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, 82% of sites pass the LCP. Where it is high, 74% 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 189,915 sites, representing millions of real page loads · How we measured