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
desktop field data
The typical page weighs 2.3 MB across 71 requests.
The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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
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 · desktop 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 98% 46ms
30–39 15,496 99% 44ms
40–49 15,953 99% 45ms
50–59 15,288 99% 45ms
60–69 14,180 99% 46ms
70–79 12,620 99% 47ms
80–89 11,068 99% 49ms
90–99 9,527 99% 49ms
100–109 7,902 99% 49ms
110–119 6,786 99% 51ms
120–129 5,886 99% 51ms
130–139 4,970 99% 52ms
140–149 4,249 99% 54ms
150–159 3,685 99% 54ms
160–169 3,200 99% 55ms
170–179 2,716 98% 55ms
180–189 2,254 98% 54ms
190–199 2,010 97% 59ms
200+ 17,791 99% 60ms
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 46ms. At the high end (200+): INP 60ms. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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
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 · desktop 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 98% 45ms
500–999 17,750 99% 45ms
1000–1499 20,558 99% 46ms
1500–1999 19,967 99% 47ms
2000–2499 17,316 99% 49ms
2500–2999 14,268 99% 49ms
3000–3499 11,420 99% 51ms
3500–3999 9,259 99% 51ms
4000–4499 7,415 99% 52ms
4500–4999 6,113 99% 53ms
5000–5499 4,998 99% 52ms
5500–5999 4,129 98% 53ms
6000–6499 3,721 99% 53ms
6500–6999 3,032 99% 52ms
7000–7499 2,570 98% 54ms
7500–7999 2,346 98% 52ms
8000–8499 1,936 99% 52ms
8500–8999 1,711 98% 53ms
9000–9499 1,487 99% 53ms
9500+ 17,589 99% 54ms
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 45ms. At the high end (9500+ KB): INP 54ms. computed
The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.