Fast by design.
Measured, not promised.
A consent banner should stay out of your page's way. ConsentEase loads async at a versioned, cache-friendly URL, ships no frontend framework in its runtime, and reports Web Vitals so you can measure the real impact — on your site, not a lab.
Loaded async, measured for real
Manual embed snippet
<script async src="…/script.js?v=<version>"></script>does not block page parsing
versioned, cacheable URL
The banner runtime collects Web Vitals so impact is measured on real page loads — not estimated from a lab score.
A consent banner shouldn't slow the page it protects.
A render-blocking banner holds up your page
A consent script that blocks parsing delays the first paint — visitors wait on the banner before they see your content.
Heavy runtimes tax every visit
A banner that ships a whole frontend framework to the browser adds weight to a script that runs on every page, for every visitor.
Lab scores aren't your real experience
A one-off Lighthouse number in ideal conditions says little about how the banner behaves on your actual pages and networks.
The timeline above is illustrative and relative — it shows the difference between blocking and async loading, not measured timings for any specific site.
Blocking vs. async on page load
IllustrativeRender-blocking script
Content waits for the script
Async loader
Content paints without waiting
Bar widths are illustrative and relative — not measured timings. A blocking script holds up the first paint; an async loader lets your content render while it loads.
Light to load, honest to measure.
Three choices keep the banner out of the way — and let you confirm it, rather than take our word for it.
No framework in the runtime
The generated banner script is plain JavaScript. It does not ship React or another frontend framework to your visitors.
Async delivery, cached & versioned
The manual embed loads async at a versioned URL, served with short public caching and revalidation so browsers can reuse it.
Measured with Web Vitals
The runtime collects LCP, CLS, INP, FCP and TTFB, so you can judge real-world impact from actual page loads.
Async delivery and the versioned URL apply to the manual embed. The generated runtime is vanilla JavaScript and collects Web Vitals as described in the ConsentEase embed and script.
What's designed in — and what to measure.
Performance is a set of deliberate choices plus honest measurement. Here is what is built in and what you should verify on representative pages.
Designed in
- Async loader (manual embed)non-blocking
- Versioned script URLcache-friendly
- Short public caching with revalidationreusable
- No frontend framework in the runtimevanilla JS
- Web Vitals telemetryLCP · CLS · INP · FCP · TTFB
Verify on your site
- Response transfer size and cache state
- Script execution and main-thread work
- Web Vitals before and after installation
Measure it on your own site
Real performance depends on your page, your network, and everything else you load. The honest way to know the impact is to measure it on your site — which is why the runtime reports Web Vitals rather than leaning on a lab score.
What we do not claim
No fixed kilobyte promise, no guaranteed Lighthouse score, and no "zero impact". Those numbers vary by environment, so we give you the design choices and the measurements to check them yourself.
Read the performance documentationThe async, versioned, cached delivery applies to the manual embed. Tag-manager or platform integrations follow that host's loading rules.
Performance must be measured in context. ConsentEase does not promise a fixed kilobyte size, a Lighthouse score, or zero impact. Real-world performance varies by environment, so measure transfer, execution, and Web Vitals on your own representative pages.
How the banner reaches the browser.
Async manual embed
- ConsentEase
- Non-blocking loader
- Cookiebot
- Check current setup
- CookieYes
- Check current setup
- OneTrust
- Check current setup
Versioned, cacheable URL
- ConsentEase
- Version + revalidation
- Cookiebot
- Configuration-dependent
- CookieYes
- Configuration-dependent
- OneTrust
- Configuration-dependent
Framework in the runtime
- ConsentEase
- None (vanilla JS)
- Cookiebot
- Configuration-dependent
- CookieYes
- Configuration-dependent
- OneTrust
- Configuration-dependent
Web Vitals telemetry
- ConsentEase
- Collected by runtime
- Cookiebot
- Not typically shown
- CookieYes
- Not typically shown
- OneTrust
- Not typically shown
Delivered size
- ConsentEase
- Varies by build — measure it
- Cookiebot
- Varies by configuration
- CookieYes
- Varies by configuration
- OneTrust
- Varies by configuration
Neutral comparison. Competitor delivery depends on plan and configuration, so those cells are marked as setup- or configuration-dependent rather than asserted — and we make no claim about competitor script sizes.
A banner that respects
your page speed.
Scan your site to see where you stand, then add a consent banner built to stay light.