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 CLS site count and median CLS at each level of cookies per site — n

0.00 0.04 0.08 0.11 0.15
0.1
0 27266 54531
0 1 2 3 4 5–6 7–8 9–11 12–15 16–20 >p98
Good (≤0.1) Needs improvement Poor (>0.25) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
3

Passing CLS by cookies per site — n which level passes the CLS most often

Cookies per site — nSitesPassing CLSCLS
0 54,531 91% 0.00
1 22,919 89% 0.00
2 19,663 89% 0.00
3 16,279 88% 0.00
4 12,570 88% 0.00
5–6 16,180 87% 0.00
7–8 13,304 89% 0.00
9–11 12,165 88% 0.00
12–15 7,127 87% 0.00
16–20 3,823 85% 0.00
>p98 2,123 77% 0.01
Good Needs Improvement Poor Faded rows: under 100 sites

Cookies per site — n 2. p75 5. p99 21. At the low end (0): CLS 0.00. At the high end (>p98): CLS 0.01. computed

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

Distribution & median CLS site count and median CLS at each level of cookies per site — size

0.00 0.04 0.08 0.11 0.15
0.1
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 (≤0.1) Needs improvement Poor (>0.25) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
5

Passing CLS by cookies per site — size which level passes the CLS most often

Cookies per site — sizeSitesPassing CLSCLS
0 71,419 91% 0.00
0.1–0.132 33,418 89% 0.00
0.174–0.23 23,876 88% 0.00
0.23–0.303 15,480 88% 0.00
0.4–0.528 13,898 86% 0.00
0.528–0.696 3,232 86% 0.00
0.696–0.919 4,993 84% 0.00
0.919–1.21 7,365 88% 0.00
1.21–1.6 4,267 85% 0.00
>p98 2,736 80% 0.01
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): CLS 0.00. At the high end (>p98): CLS 0.01. 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