Skip to main contentHow fast does the banner appear?
387 ms
Median of 15 visits.
All 10 CMPs, best first
- c15t60 ms
- Cookie Control385 ms
- CookieYes387 ms
- iubenda431 ms
- Didomi466 ms
- Enzuzo477 ms
- OneTrust629 ms
- Osano644 ms
- Usercentrics672 ms
- Ketch1.68 s
CookieYesCookieYesCookieYes cookie banner: speed and features
In our tests, CookieYes showed its cookie banner in a median 387 ms on desktop. It added no measurable delay to the main content. Accept responded in 16 ms and Reject in 16 ms. It held trackers back in 3 of 4 consent checks. We could not confirm the other check.
On an emulated mid-tier phone, the banner took 2.42 s. Per vendor docs, CookieYes supports IAB TCF, Google Consent Mode v2, Google CMP certification and Global Privacy Control. We could not confirm IAB GPP.
How fast is CookieYes’ cookie banner?
Does it slow the page down?
No measurable delay95% interval −12 ms to 24 ms
Main content painted as fast as on the same page without a consent manager.
All 10 CMPs, best first
- Didomi−4 ms
- iubenda−4 ms
- CookieYes−4 ms
- Ketch0 ms
- Osano0 ms
- Usercentrics0 ms
- Enzuzo4 ms
- OneTrust4 ms
- Cookie Control8 ms
- c15t16 ms
How fast does a click respond?
16 msOne visit measured
Reject responded in 16 ms. Under 200 ms feels instant.
All 10 CMPs, best first
- c15t16 ms
- Cookie Control16 ms
- Didomi16 ms
- iubenda16 ms
- Usercentrics16 ms
- CookieYes16 ms
- Enzuzo24 ms
- OneTrust24 ms
- Osano32 ms
- Ketch40 ms
Does it block trackers until consent?
3 of 4consent checks passed
We could not confirm 1 of 4 checks either way.
All 10 CMPs, best first
- c15t100%
- Didomi100%
- Enzuzo100%
- iubenda100%
- Ketch100%
- OneTrust100%
- Osano100%
- Usercentrics100%
- Cookie Control75%
- CookieYes75%
Which standards and features does CookieYes support?
Each status comes from CookieYes’ 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 | Pro and Ultimate plans (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 | Pro and Ultimate plans (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Geo-targeted banners | Pro and Ultimate plans (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 | Proprietary (vendor documentation, opens in a new tab) |
| Self-hostable | Unknown |
| Headless UI | Unknown |
| TypeScript types | Unknown |
| Feature | Status |
|---|---|
| Free tier | 5,000 pageviews a month (vendor documentation, opens in a new tab) |
Which frameworks does CookieYes support?
- First-party SDKs
- None
- Script tag
- Supported
- Measured in this run
- Script tag, React, Next.js, Nuxt, Astro and TanStack Start
Support per CookieYes’ documentation.
CookieYes’ results by framework, desktop
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 | 284 ms | No measurable delay95% interval −4 ms to 24 ms | Under 16 msOne visit measured | 3 of 4 passed |
| React | 287 ms | No measurable delay95% interval −24 ms to 20 ms | 16 msOne visit measured | 3 of 4 passed |
| Next.jsShared with every CMPShown above | 387 ms | No measurable delay95% interval −12 ms to 24 ms | 16 msOne visit measured | 3 of 4 passed |
| Nuxt | 284 ms | No measurable delay95% interval −20 ms to 16 ms | Under 16 msOne visit measured | 3 of 4 passed |
| Astro | 282 ms | No measurable delay95% interval −24 ms to 12 ms | Under 16 msOne visit measured | 3 of 4 passed |
| TanStack Start | 279 ms | No measurable delay95% interval −12 ms to 16 ms | Under 16 msOne visit measured | 3 of 4 passed |
Were there problems testing CookieYes?
We show each missing answer as missing, never as zero.
Desktop
- CookieYes only renders on its registered host, so it ran in its own batch beside its own no-CMP page on that host.
- Its site configuration has no cookies assigned, so its bytes are probably a few KB lower than on a real site.
- Here CookieYes loads after the page hydrates: with its script in the head, accept, reject and save failed on mobile. This cell comes from a separate morning run, so compare it with its own no-CMP page rather than with CookieYes on other frameworks.
- There is no granular save-preferences flow to test.
Mobile (emulated)
- CookieYes only renders on its registered host, so it ran in its own batch beside its own no-CMP page on that host.
- Its site configuration has no cookies assigned, so its bytes are probably a few KB lower than on a real site.
- Here CookieYes loads after the page hydrates: with its script in the head, accept, reject and save failed on mobile. This cell comes from a separate morning run, so compare it with its own no-CMP page rather than with CookieYes on other frameworks.
- There is no granular save-preferences flow to test.
When does CookieYes 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 CookieYes start loading?
The banner was visible at 387 ms. The published results do not show when CookieYes started to load.
| Event | Time from navigation |
|---|---|
| First byte (TTFB) | 8 ms |
| First paint (FCP) | 64 ms |
| Largest paint (LCP) | 132 ms |
| Banner visible | 387 ms |
| 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 CookieYes | Difference |
|---|---|---|
| TTFBTime to first byte | 8 ms | No measurable difference95% interval −4 ms to 4 ms |
| FCPFirst Contentful Paint | 64 ms | No measurable difference95% interval −12 ms to 28 ms |
| LCPLargest Contentful Paint | 132 ms | No measurable difference95% interval −12 ms to 24 ms |
| CLSCumulative Layout Shift | 0.00 | No measurable difference95% interval: 0.00 |
| Primary content paintThe page’s main content, not the banner | 132 ms | No measurable difference95% interval −12 ms to 24 ms |
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 16 ms.
| Event | Time from the click |
|---|---|
| Screen responds | 16 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 CookieYes | Difference |
|---|---|---|
| Initial transferBytes before the page settles | 644 KB | +31 KB95% interval: 31 KB |
| Deferred transferBytes loaded later | Not compared | |
| RequestsAll requests | 19 | +9No interval reported |
| Third-party requestsRequests to other hosts | 9 | +9No 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 CookieYes | Difference |
|---|---|---|
| Long-task timeBlocking time during load | 0 ms | 0 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 387 ms, against 471 ms for the median of the 10 CMPs measured. On an emulated mid-tier phone, it appeared in a median 2.42 s, against 2.71 s for the median of the 10 CMPs measured.
On desktop it added no measurable delay to the main content. On an emulated mid-tier phone it delayed the main content by 176 ms (95% interval 148 ms to 212 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 3 of 4 checks on desktop and on an emulated mid-tier phone. We could not confirm the other check. A check fails if a tracker runs, the page sets a cookie or data leaves the page before the visitor chooses.
Per vendor docs, CookieYes supports IAB TCF, Google Consent Mode v2, Google CMP certification and Global Privacy Control. We could not confirm IAB GPP. Feature support comes from CookieYes’ documentation. CookieBench did not test these features itself.
