Is your cookie banner hurting your LCP?
A cookie banner doesn't have to affect your Core Web Vitals — but many do. The problem is almost never «asking for consent», it's how the CMP's script is built.
Three real causes of a CMP tanking your LCP (Largest Contentful Paint): the script weighs hundreds of KB (some enterprise CMPs exceed 100-200 KB uncompressed), it loads render-blocking in <head> instead of async/defer, or it injects extra CSS that delays first paint. None of these three have anything to do with GDPR compliance — they're vendor architecture decisions.
The test is simple: audit your current banner with Lighthouse or PageSpeed Insights and check the CMP script's network weight in the Network tab. If it exceeds 30-40 KB to paint a banner, there's real room for improvement, regardless of which one you use.
Consentio weighs under 9 KB, loads without blocking render, and doesn't add external stylesheets — the goal isn't just compliance, it's not undoing the speed work you've already put in.
/guia/consent-mode-v2 · /alternativas/cookiebot · /calculadora-coste-cmp · /registro?plan=pro