---
title: "Inth vs Didomi"
canonical: "https://cookiebench.com/compare/inth-vs-didomi"
last-updated: "2026-11-14"
---

# Inth vs Didomi: cookie banner speed and features

On desktop, Inth showed its banner sooner, in a median 25 ms against 456 ms for Didomi. Their delay to the main content was about the same. The 95% intervals overlap. Both held trackers back in every check. Per vendor docs, only Inth offers open-source code and a free tier. Per vendor docs, only Didomi offers a Google-certified CMP.

We measured both in the same run, in a Next.js app. We measured each against the same page without a consent manager. They also share Script tag, React, Nuxt, Astro, TanStack Start integrations.

## Which is faster on desktop?

Desktop profile: 1365 × 768 · No CPU slowdown · 12.5 MB/s, no added latency.

| Question | Inth | Didomi | Difference |
| --- | --- | --- | --- |
| How fast does the banner appear? | 25 ms | 456 ms | Inth’s banner appeared 430 ms sooner. |
| Does it slow the page down? | +16 ms (95% interval 4 ms to 24 ms) | No measurable change | About the same. The 95% intervals overlap. |
| How fast does a click respond? | 40 ms | 40 ms | About the same. They are less than 16 ms apart. |
| Does it block trackers until consent? | 4 of 4 checks passed | 4 of 4 checks passed | Both held trackers back in every check. |
| How much does it add to the page? | +104 KB (95% interval: 104 KB) | +275 KB (95% interval 275 KB to 276 KB) | Inth added 171 KB less to the first load. |

## Which is faster on mobile?

Mobile (emulated) profile: 390 × 844, DPR 3 · Mid-tier phone CPU (4× slowdown) · 200 KB/s, 150 ms latency.

On emulated mobile, Inth showed its banner sooner, in a median 252 ms against 4.27 s for Didomi. Inth delayed the main content 964 ms less. Both held trackers back in every check. Per vendor docs, only Inth offers open-source code and a free tier. Per vendor docs, only Didomi offers a Google-certified CMP.

| Question | Inth | Didomi | Difference |
| --- | --- | --- | --- |
| How fast does the banner appear? | 252 ms | 4.27 s | Inth’s banner appeared 4.02 s sooner. |
| Does it slow the page down? | +400 ms (95% interval 396 ms to 408 ms) | +1.36 s (95% interval 1.28 s to 1.37 s) | Inth delayed the main content 964 ms less. |
| How fast does a click respond? | 80 ms | 48 ms | Didomi responded 32 ms sooner. Both are under 200 ms, which feels instant. |
| Does it block trackers until consent? | 4 of 4 checks passed | 4 of 4 checks passed | Both held trackers back in every check. |
| How much does it add to the page? | +104 KB (95% interval: 104 KB) | +270 KB (95% interval 254 KB to 271 KB) | Inth added 166 KB less to the first load. |

## Which features differ?

| Feature | Inth | Didomi |
| --- | --- | --- |
| IAB TCF | Per vendor docs | Per vendor docs (TCF v2.2) |
| IAB GPP | Per vendor docs (GPP 1.1) | Per vendor docs |
| Google Consent Mode v2 | Per vendor docs | Per vendor docs |
| Google-certified CMP | Not supported (Not on Google’s list) | Per vendor docs |
| Global Privacy Control | Per vendor docs | Per vendor docs |
| Geo-targeted banners | Per vendor docs | Per vendor docs |
| Script blocking | Per vendor docs | Per vendor docs (Tag-based) |
| Consent records | Per vendor docs (With a backend) | Per vendor docs |
| Cookie scanning | Per vendor docs (Via Inth Website Audit) | Per vendor docs |
| Open source | Per vendor docs (Apache-2.0) | Not supported (Proprietary) |
| Self-hostable | Per vendor docs | Partial (Assets through your domain) |
| Headless UI | Per vendor docs | Per vendor docs |
| TypeScript types | Per vendor docs | Partial (React SDK only) |
| Free tier | Per vendor docs (Open source; hosted free plan) | Not supported (Contact sales) |
| Script tag | Per vendor docs | Per vendor docs |
| React SDK | Per vendor docs (First-party SDK) | Per vendor docs (First-party SDK) |
| Next.js SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Vue SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Nuxt SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Svelte SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| SvelteKit SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Astro SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| TanStack Start SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |

## Which should you choose?

### Choose Inth if

- You want open-source code and a free tier
- You want a first-party SDK for Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack Start
- A fast banner matters to you: Inth’s banner appeared 430 ms sooner
- Page weight matters to you: Inth added 171 KB less to the first load

### Choose Didomi if

- You need a Google-certified CMP

## Questions about this pair

### Is Didomi slower than Inth?

On the desktop profile, Inth’s banner appeared in a median 25 ms and Didomi’s in 456 ms. Their delay to the main content was about the same. The 95% intervals overlap.

### Does Inth support Google-certified CMP like Didomi?

No, per vendor docs. Didomi documents Google-certified CMP support. Inth does not.

### Do Inth and Didomi block trackers before consent?

Both held trackers back in every check. Each check loads the page. Then it looks for trackers that ran, cookies that the page set or data that left the page before the visitor chose.

## Related comparisons

- [Inth vs OneTrust](https://cookiebench.com/compare/inth-vs-onetrust.md)
- [Inth vs CookieYes](https://cookiebench.com/compare/inth-vs-cookieyes.md)
- [Inth vs Usercentrics](https://cookiebench.com/compare/inth-vs-usercentrics.md)
- [Inth vs Osano](https://cookiebench.com/compare/inth-vs-osano.md)
- [Inth vs iubenda](https://cookiebench.com/compare/inth-vs-iubenda.md)
- [Inth vs Ketch](https://cookiebench.com/compare/inth-vs-ketch.md)

Run `matrix-2026-10-15`, published 2026-11-14.

Methodology [cookiebench-v3.2.4](https://cookiebench.com/methodology). Inth maintains CookieBench, and its own consent manager is one of the consent managers we measure ([disclosure](https://cookiebench.com/methodology)). Feature support comes from vendor documentation unless a row says "Verified by test".
