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

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
phone field data

The typical page weighs 2.5 MB across 72 requests.

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

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

0ms 750ms 1500ms 2250ms 3000ms
2.5s
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 (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
3

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

Page weight & requests — nSitesPassing LCPLCP
1–2 1,124 85% 1.4s
3 248 86% 1.4s
4–6 728 85% 1.4s
7–11 1,292 89% 1.1s
12–19 3,406 90% 1.2s
20–34 10,425 91% 1.2s
35–62 23,047 87% 1.4s
63–112 27,773 80% 1.7s
113–202 17,897 73% 1.8s
203–365 7,089 77% 1.7s
>p98 1,878 80% 1.7s
Good Needs Improvement Poor Faded rows: under 100 sites

Page weight & requests — n 72. p75 122. p99 436. At the low end (1–2): LCP 1.4s. At the high end (>p98): LCP 1.7s. computed

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

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

0ms 750ms 1500ms 2250ms 3000ms
2.5s
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 (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
5

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

Page weight & requests — sizeSitesPassing LCPLCP
0 150 89% 1.5s
0.1–0.346 193 88% 1.5s
0.346–1.2 440 84% 1.4s
1.2–4.15 368 84% 1.5s
4.15–14.4 266 81% 1.4s
14.4–49.8 526 88% 1.2s
49.8–172 1,080 88% 1.1s
172–596 5,619 92% 1.1s
596–2065 30,318 87% 1.4s
2065–7149 41,935 80% 1.7s
7149–24753 12,119 74% 1.8s
>p98 1,896 73% 1.9s
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): LCP 1.5s. At the high end (>p98): LCP 1.9s. computed

The State of Web Vitals · Q1 2026 · 94,910 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.

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, 84% of sites pass the LCP. Where it is high, 73% do. The decline is gradual. There is no point where sites suddenly start failing.

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 94,910 sites, representing millions of real page loads · How we measured