Consent platforms

Consent platforms present on the page.

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

At a glance the headline numbers for Consent platforms

Consent platforms present on the page.

16
Categories
In the distribution
18.1%
Fleet share
Top: quantcast_choice
100.0%
Sites with any
Of quantcast_choice
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2

The consent platforms mix who uses what, and how fast each group loads

VariantShare of sitesMedian
Quantcast choice
18%
Complianz
17%
Civic cookie control
16%
Cookiebot
15%
Borlabs cookie
10%
Cookieyes
9%
Onetrust
4%
Cookie script
2%
Didomi
2%
Gdpr cookie compliance
2%
Iubenda
2%
Cookiefirst
1%
Termly
1%
Cookie information
0%
Osano
0%
Trustarc
0%

Consent platforms. On the fleet: 18.1% quantcast choice, 16.8% complianz, 16.4% civic cookie control. 100.0% of sites use at least one quantcast_choice.

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

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

Consent platforms run before everything else by design, because they gate the other tags. That puts them on the critical path of every first visit. The banner is often the first thing the visitor interacts with, so a slow consent script means the first click of the session is the slow one.

The banner is also a CLS suspect when it pushes content down instead of overlaying it. Overlay it, load the consent script early, and keep it small. It runs on every single first visit, so its weight multiplies.

Related signals JS framework → Optimization plugins → Third parties per page → Cookie wall detected → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured