At a glance the headline numbers for Cookie wall detected
Whether a consent wall blocks the page on first visit.
29.0% of sites block their content behind a cookie wall.
Cookie wall detected sites that have it vs sites that don't
29.0% of sites show a cookie consent wall (27,534 of 94,910). With show: LCP 1.7s, 79.0% pass. Without: LCP 1.4s, 84.3% pass. Correlates with +222ms LCP and −5.3 pp pass rate. computed
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.
How does a cookie wall affect the Core Web Vitals?
Having it makes no measurable difference to the INP: 96% pass with it, 94% without.
The gap is bigger on LCP: 79% pass with it, 84% without.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.