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,684
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 27266 54531
0 1 2 3 4 5–6 7–8 9–11 12–15 16–20 >p98
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 54,531 92% 93ms
1 22,919 91% 100ms
2 19,663 92% 97ms
3 16,279 93% 97ms
4 12,570 93% 97ms
5–6 16,180 90% 103ms
7–8 13,304 94% 97ms
9–11 12,165 94% 104ms
12–15 7,127 92% 112ms
16–20 3,823 91% 119ms
>p98 2,123 80% 142ms
Good Needs Improvement Poor Faded rows: under 100 sites

Cookies per site — n 2. p75 5. p99 21. At the low end (0): INP 93ms. At the high end (>p98): INP 142ms. 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 cookies per site — size

0ms 63ms 125ms 188ms 250ms
200ms
0 35710 71419
0 0.1–0.132 0.132–0.174 0.174–0.23 0.23–0.303 0.303–0.4 0.4–0.528 0.528–0.696 0.696–0.919 0.919–1.21 1.21–1.6 >p98
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 cookies per site — size which level passes the INP most often

Cookies per site — sizeSitesPassing INPINP
0 71,419 92% 94ms
0.1–0.132 33,418 93% 95ms
0.174–0.23 23,876 93% 95ms
0.23–0.303 15,480 93% 104ms
0.4–0.528 13,898 92% 109ms
0.528–0.696 3,232 90% 116ms
0.696–0.919 4,993 89% 120ms
0.919–1.21 7,365 92% 103ms
1.21–1.6 4,267 92% 109ms
>p98 2,736 83% 135ms
Good Needs Improvement Poor Faded rows: under 100 sites

Cookies per site — size 0 KB. p75 0 KB. p99 2 KB. At the low end (0 KB): INP 94ms. At the high end (>p98): INP 135ms. 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

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.

How does this affect the Core Web Vitals?

Cookie count correlates with the LCP. Where the cookie count is low, 85% of sites pass the LCP. Where it is high, 64% do. Cookie count has little causal relationship with the LCP. That makes a high cookie count more likely a result or an indication of a slow, heavily built site than a cause of a slow one. More cookies almost always means more trackers, more third parties and more script, and those do slow pages down.

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