The State of Web Vitals

Cookies per site

Cookies set during a cold visit: how many and their total size.

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

At a glance the headline numbers for Cookies per site

Cookies set during a cold visit: how many and their total size.

2
cookie count
on the typical page
0 KB
cookie size
on the typical page
0 KB
1 in 4 pages exceed this
cookie size
180,899
sites measured
phone field data

The typical site sets 2 cookies.

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 cookies per site — n

0ms 63ms 125ms 188ms 250ms
200ms
0 27298 54596
0–0 1–1 2–2 3–3 4–4 5–5 6–6 7–7 8–8 9–9 10+
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 cookies per site — n which level passes the INP most often

Cookies per site — nSitesPassing INPINP
0–0 54,596 92% 93ms
1–1 22,945 91% 100ms
2–2 19,687 92% 97ms
3–3 16,300 93% 97ms
4–4 12,587 93% 97ms
5–5 9,794 89% 102ms
6–6 6,401 92% 104ms
7–7 8,472 95% 96ms
8–8 4,846 94% 102ms
9–9 5,089 94% 103ms
10+ 20,182 91% 114ms
Good Needs Improvement Poor Faded rows: under 100 sites

Cookies per site — n 2. p75 5. p99 21. At the low end (0–0): INP 93ms. At the high end (10+): INP 114ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
4

Cookies per site — size the value at each percentile across all sites

0 KB
p10
0 KB
p25
0 KB
p50
0 KB
p75
1 KB
p90
2 KB
p99

Cookies per site — size 0 KB. p75 0 KB. p99 2 KB. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
5

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

The cookie count is a proxy. It tells you how many vendors run on the page. Most cookies exist for tracking and each tracker sets its own. The count grows with every tag the marketing stack adds. Cookies are also sent with every request to their domain, which adds header weight. That is rarely the real cost.

The real cost is what the cookies stand for. The vendors behind them run script on your main thread and delay every interaction (INP). They also inject banners, widgets and ads after the page looks settled (CLS). A rising cookie count means it is time to audit the tag manager, not to shrink cookies.

Go fix it The case for limiting analytics and tracking scripts →
Related signals Responsive image markup → font-display strategy → Stylesheet origin (1P/3P) → Fonts per page → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured