Skip to main contentHow fast does the banner appear?
2.75 s
Median of 15 visits.
All 10 CMPs, best first
- c15t240 ms
- Osano2.15 s
- CookieYes2.42 s
- Cookie Control2.47 s
- iubenda2.66 s
- Enzuzo2.75 s
- OneTrust3.92 s
- Usercentrics4.16 s
- Didomi4.41 s
- Ketch7.95 s
EnzuzoEnzuzoEnzuzo cookie banner: speed and features
In our tests, Enzuzo showed its cookie banner in a median 2.75 s on an emulated mid-tier phone. It delayed the main content by 768 ms. Accept responded in 56 ms and Reject in 56 ms. It held trackers back in all 4 consent checks.
On desktop, the banner took 477 ms. Per vendor docs, Enzuzo supports IAB TCF, Google Consent Mode v2, Google CMP certification and Global Privacy Control. We could not confirm IAB GPP.
How fast is Enzuzo’s cookie banner?
Does it slow the page down?
+768 ms
Compared with the same page without a consent manager. There were too few paired visits to calculate an interval.
All 10 CMPs, best first
- CookieYes176 ms
- c15t408 ms
- Osano424 ms
- OneTrust476 ms
- Cookie Control492 ms
- iubenda612 ms
- Enzuzo768 ms
- Usercentrics844 ms
- Didomi1.28 s
- Ketch1.74 s
How fast does a click respond?
56 msOne visit measured
Reject responded in 56 ms. Under 200 ms feels instant.
All 10 CMPs, best first
- Didomi16 ms
- OneTrust16 ms
- Usercentrics16 ms
- Cookie Control24 ms
- CookieYes24 ms
- c15t32 ms
- iubenda32 ms
- Ketch40 ms
- Enzuzo56 ms
- Osano128 ms
Does it block trackers until consent?
4 of 4consent checks passed
No tracker ran and the page set no cookie before the visitor chose.
All 10 CMPs, best first
- c15t100%
- Didomi100%
- Enzuzo100%
- iubenda100%
- Ketch100%
- OneTrust100%
- Usercentrics100%
- Cookie Control75%
- CookieYes75%
- Osano50%
Which standards and features does Enzuzo support?
Each status comes from Enzuzo’s documentation. CookieBench does not test these features unless a line says so.
- Verified by test
- Per vendor docs
- Partial
- Not supported
- Unknown
| Feature | Status |
|---|---|
| IAB TCF | Growth plan and up (vendor documentation, opens in a new tab) |
| IAB GPP | Unknown |
| Google Consent Mode v2 | Per vendor docs (vendor documentation, opens in a new tab) |
| Google-certified CMP | Per vendor docs (vendor documentation, opens in a new tab) |
| Global Privacy Control | Per vendor docs (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Geo-targeted banners | Growth plan and up (vendor documentation, opens in a new tab) |
| Script blocking | Per vendor docs (vendor documentation, opens in a new tab) |
| Consent records | Per vendor docs (vendor documentation, opens in a new tab) |
| Cookie scanning | Per vendor docs (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Open source | Hosted embed only (vendor documentation, opens in a new tab) |
| Self-hostable | Hosted embed only (vendor documentation, opens in a new tab) |
| Headless UI | Enterprise plan (vendor documentation, opens in a new tab) |
| TypeScript types | Unknown |
| Feature | Status |
|---|---|
| Free tier | 5,000 visitors a month (vendor documentation, opens in a new tab) |
Which frameworks does Enzuzo support?
- First-party SDKs
- None
- Script tag
- Supported
- Measured in this run
- Script tag, React, Next.js, Nuxt, Astro and TanStack Start
Support per Enzuzo’s documentation (opens in a new tab).
Enzuzo’s results by framework, mobile (emulated)
Each row is a separate app. We measured each one against the same app without a consent manager. The rows compare integrations, not frameworks.
| Framework | Banner appears | Page slowed by | Click responds in | Trackers blocked |
|---|---|---|---|---|
| Script tag | 2.32 s | +772 ms | 48 msOne visit measured | 4 of 4 passed |
| React | 2.06 s | +568 ms | 48 msOne visit measured | 4 of 4 passed |
| Next.jsShared with every CMPShown above | 2.75 s | +768 ms | 56 msOne visit measured | 4 of 4 passed |
| Nuxt | 2.49 s | +772 ms | 56 msOne visit measured | 4 of 4 passed |
| Astro | 2.31 s | +772 ms | 64 msOne visit measured | 4 of 4 passed |
| TanStack Start | 2.67 s | +768 ms | 72 msOne visit measured | 4 of 4 passed |
Were there problems testing Enzuzo?
We show each missing answer as missing, never as zero.
Desktop
- Its remote script or config changed during the run, so the run gives no confidence intervals for this cell. Differences are medians only.
Mobile (emulated)
- Its remote script or config changed during the run, so the run gives no confidence intervals for this cell. Differences are medians only.
When does Enzuzo load, and what does it cost the page?
Lab detail for engineers. All Core Web Vitals are here. The summary leaves some of them out.
When does Enzuzo start loading?
The banner was visible at 2.75 s. The published results do not show when Enzuzo started to load.
| Event | Time from navigation |
|---|---|
| First byte (TTFB) | 6 ms |
| First paint (FCP) | 248 ms |
| Banner visible | 2.75 s |
| Largest paint (LCP) | 4.22 s |
| CMP requested | |
| CMP loaded | |
| Consent state known |
How do page vitals compare with no consent manager?
Each row shows the value on the page with the consent manager. It also shows how far the value moved from the same page without one.
| Measure | With Enzuzo | Difference |
|---|---|---|
| TTFBTime to first byte | 6 ms | +1 msNo interval reported |
| FCPFirst Contentful Paint | 248 ms | +8 msNo interval reported |
| LCPLargest Contentful Paint | 4.22 s | +768 msNo interval reported |
| CLSCumulative Layout Shift | 0.00 | 0.00No interval reported |
| Primary content paintThe page’s main content, not the banner | 4.22 s | +768 msNo interval reported |
What was the largest element on screen?
LCP times the largest element on screen. If that is the banner, LCP measures the banner instead of the page.
There is no LCP attribution for this profile and framework.
What happens after a visitor clicks Accept?
The screen responded to Accept in 56 ms.
| Event | Time from the click |
|---|---|
| Screen responds | 56 ms |
| Banner gone | |
| Consent applied | |
| Analytics active |
How much does it download?
Initial transfer happens before the page settles. Deferred transfer comes after.
| Measure | With Enzuzo | Difference |
|---|---|---|
| Initial transferBytes before the page settles | 766 KB | +153 KBNo interval reported |
| Deferred transferBytes loaded later | Not compared | |
| RequestsAll requests | 12 | +2No interval reported |
| Third-party requestsRequests to other hosts | 2 | +2No interval reported |
Does it block the main thread?
Long tasks are stretches over 50 ms when the page cannot respond to taps or keys.
| Measure | With Enzuzo | Difference |
|---|---|---|
| Long-task timeBlocking time during load | 264 ms | +197 msNo interval reported |
What do returning visitors see?
A visitor who accepted on an earlier visit comes back. We check that the banner stays hidden.
- Banner stayed hidden
- Consent state known at
What was tested?
- Methodology
- cookiebench-v3.2.4
- Analysis
matrix-2026-10-11
On desktop, it appeared in a median 477 ms, against 471 ms for the median of the 10 CMPs measured. On an emulated mid-tier phone, it appeared in a median 2.75 s, against 2.71 s for the median of the 10 CMPs measured.
On desktop it delayed the main content by 4 ms. On an emulated mid-tier phone it delayed the main content by 768 ms. Delay is the extra time before the main content appears. We compare Largest Contentful Paint on the same page, with and without a consent manager.
It passed 4 of 4 checks on desktop and on an emulated mid-tier phone. A check fails if a tracker runs, the page sets a cookie or data leaves the page before the visitor chooses.
Per vendor docs, Enzuzo supports IAB TCF, Google Consent Mode v2, Google CMP certification and Global Privacy Control. We could not confirm IAB GPP. Feature support comes from Enzuzo’s documentation. CookieBench did not test these features itself.
