The State of Web Vitals

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 · Phone 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,486
sites measured
phone field data

The typical page weighs 2.3 MB across 71 requests.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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 8896 17791
20–29 30–39 40–49 50–59 60–69 70–79 80–89 90–99 100–109 110–119 120–129 130–139 140–149 150–159 160–169 170–179 180–189 190–199 200+
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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
20–29 17,500 82% 103ms
30–39 15,496 93% 88ms
40–49 15,953 94% 91ms
50–59 15,288 94% 93ms
60–69 14,180 95% 94ms
70–79 12,620 94% 96ms
80–89 11,068 93% 99ms
90–99 9,527 94% 101ms
100–109 7,902 93% 103ms
110–119 6,786 93% 104ms
120–129 5,886 93% 104ms
130–139 4,970 93% 104ms
140–149 4,249 93% 106ms
150–159 3,685 92% 105ms
160–169 3,200 91% 106ms
170–179 2,716 90% 108ms
180–189 2,254 90% 110ms
190–199 2,010 90% 109ms
200+ 17,791 90% 114ms
Good Needs Improvement Poor Faded rows: under 100 sites

Page weight & requests — n 71. p75 120. p99 439. At the low end (20–29): INP 103ms. At the high end (200+): INP 114ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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 11273 22545
0–499 500–999 1000–1499 1500–1999 2000–2499 2500–2999 3000–3499 3500–3999 4000–4499 4500–4999 5000–5499 5500–5999 6000–6499 6500–6999 7000–7499 7500–7999 8000–8499 8500–8999 9000–9499 9500+
Good (≤200ms) Needs improvement Poor (>500ms) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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–499 22,545 82% 101ms
500–999 17,750 91% 92ms
1000–1499 20,558 94% 92ms
1500–1999 19,967 93% 95ms
2000–2499 17,316 93% 97ms
2500–2999 14,268 92% 99ms
3000–3499 11,420 93% 101ms
3500–3999 9,259 93% 103ms
4000–4499 7,415 93% 102ms
4500–4999 6,113 92% 103ms
5000–5499 4,998 93% 103ms
5500–5999 4,129 93% 104ms
6000–6499 3,721 94% 103ms
6500–6999 3,032 93% 103ms
7000–7499 2,570 93% 104ms
7500–7999 2,346 92% 103ms
8000–8499 1,936 92% 104ms
8500–8999 1,711 93% 106ms
9000–9499 1,487 91% 105ms
9500+ 17,589 92% 105ms
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–499 KB): INP 101ms. At the high end (9500+ KB): INP 105ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone 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.

Go fix it Bytes by resource type → Page speed on a budget → Reduce unused JavaScript → Optimize images for Core Web Vitals →
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