Skip to main contentHow fast does the banner appear?
472 ms
Median of 15 visits.
All 6 integrations, best first
- Astro433 ms
- TanStack Start447 ms
- Script tag457 ms
- React458 ms
- Next.js466 ms
- Nuxt472 ms
DidomiDidomiDidomi cookie banner: speed and features
In our tests with its Nuxt integration, Didomi showed its cookie banner in a median 472 ms on desktop. It added no measurable delay to the main content. Accept responded in 16 ms and Reject in under 16 ms. It held trackers back in all 4 consent checks.
On an emulated mid-tier phone, the banner took 3.97 s. Per vendor docs, Didomi supports IAB TCF, IAB GPP, Google Consent Mode v2, Google CMP certification and Global Privacy Control.
How fast is Didomi’s cookie banner?
On Nuxt. We measured other CMPs on Next.js only, so this comparison uses Didomi’s other integrations.
Does it slow the page down?
No measurable delay95% interval −8 ms to 20 ms
Main content painted as fast as on the same page without a consent manager.
All 6 integrations, best first
- Next.js−4 ms
- TanStack Start−4 ms
- Script tag0 ms
- Nuxt4 ms
- React4 ms
- Astro12 ms
How fast does a click respond?
16 msOne visit measured
Reject responded in under 16 ms. Under 200 ms feels instant.
All 6 integrations, best first
- Next.js16 ms
- Nuxt16 ms
- Astro16 ms
- TanStack Start16 ms
- React16 ms
- Script tag16 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 6 integrations, best first
- Next.js100%
- Nuxt100%
- Astro100%
- TanStack Start100%
- React100%
- Script tag100%
Which standards and features does Didomi support?
Each status comes from Didomi’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 | TCF v2.2 (vendor documentation, opens in a new tab) |
| IAB GPP | Per vendor docs (vendor documentation, opens in a new tab) |
| 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 | Per vendor docs (vendor documentation, opens in a new tab) |
| Script blocking | Tag-based (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 | Assets through your domain (vendor documentation, opens in a new tab) |
| Headless UI | Per vendor docs (vendor documentation, opens in a new tab) |
| TypeScript types | React SDK only (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Free tier | Contact sales (vendor documentation, opens in a new tab) |
Which frameworks does Didomi support?
- First-party SDKs
- React
- Script tag
- Supported
- Measured in this run
- Script tag, React, Next.js, Nuxt, Astro and TanStack Start
Support per Didomi’s documentation.
Didomi’s 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 | 457 ms | No measurable delay95% interval −8 ms to 24 ms | Under 16 msOne visit measured | 4 of 4 passed |
| React | 458 ms | No measurable delay95% interval −12 ms to 20 ms | Under 16 msOne visit measured | 4 of 4 passed |
| Next.jsShared with every CMP | 466 ms | No measurable delay95% interval −16 ms to 12 ms | 16 msOne visit measured | 4 of 4 passed |
| NuxtShown above | 472 ms | No measurable delay95% interval −8 ms to 20 ms | 16 msOne visit measured | 4 of 4 passed |
| Astro | 433 ms | No measurable delay95% interval 0 ms to 40 ms | 16 msOne visit measured | 4 of 4 passed |
| TanStack Start | 447 ms | No measurable delay95% interval −20 ms to 20 ms | 16 msOne visit measured | 4 of 4 passed |
When does Didomi 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 Didomi start loading?
The banner was visible at 472 ms. The published results do not show when Didomi started to load.
| Event | Time from navigation |
|---|---|
| First byte (TTFB) | 6 ms |
| First paint (FCP) | 56 ms |
| Largest paint (LCP) | 112 ms |
| Banner visible | 472 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 Didomi | Difference |
|---|---|---|
| TTFBTime to first byte | 6 ms | No measurable difference95% interval −1 ms to 3 ms |
| FCPFirst Contentful Paint | 56 ms | No measurable difference95% interval −24 ms to 24 ms |
| LCPLargest Contentful Paint | 112 ms | No measurable difference95% interval −8 ms to 20 ms |
| CLSCumulative Layout Shift | 0.00 | No measurable difference95% interval: 0.00 |
| Primary content paintThe page’s main content, not the banner | 112 ms | No measurable difference95% interval −8 ms to 20 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 Didomi | Difference |
|---|---|---|
| Initial transferBytes before the page settles | 806 KB | +253 KB95% interval: 253 KB |
| Deferred transferBytes loaded later | Not compared | |
| RequestsAll requests | 15 | +6No interval reported |
| Third-party requestsRequests to other hosts | 6 | +6No 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 Didomi | Difference |
|---|---|---|
| Long-task timeBlocking time during load | 59 ms | +59 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- Issues
- None recorded in this run
On desktop, it appeared in a median 466 ms, against 471 ms for the median of the 10 CMPs measured. On an emulated mid-tier phone, it appeared in a median 4.41 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 1.28 s (95% interval 1.26 s to 1.29 s). 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, Didomi supports IAB TCF, IAB GPP, Google Consent Mode v2, Google CMP certification and Global Privacy Control. Feature support comes from Didomi’s documentation. CookieBench did not test these features itself.
