1
At a glance the headline numbers for Cookie wall detected
Whether a consent wall blocks the page on first visit.
0.0%
Adoption
0 of 0
—
With (median LCP)
—
Without (median LCP)
The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2
Cookie wall detected sites that have it vs sites that don't
0.0% of sites show a cookie consent wall (0 of 0). With show: LCP —, 0.0% pass. Without: LCP —, 0.0% pass. computed
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
A cookie wall blocks the page until the visitor chooses. For the vitals that means the first interaction of every new session happens on the wall: its buttons are the INP sample, its overlay is the first thing painted.
If the wall must exist, it must be the fastest thing on the page. Inline its styles, keep its script first-party, and make the buttons respond instantly. A laggy consent click is the worst first impression a page can measure.
Related signals Optimization plugins → CMS → Third parties per page → Third-party categories → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.