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

# Inth vs Enzuzo: cookie banner speed and features

On desktop, Inth showed its banner sooner, in a median 25 ms against 449 ms for Enzuzo. Enzuzo delayed the main content 16 ms less. Both held trackers back in every check. Per vendor docs, only Inth offers open-source code and self-hosting. Per vendor docs, only Enzuzo 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 | Enzuzo | Difference |
| --- | --- | --- | --- |
| How fast does the banner appear? | 25 ms | 449 ms | Inth’s banner appeared 424 ms sooner. |
| Does it slow the page down? | +16 ms (95% interval 4 ms to 24 ms) | 0 ms | Enzuzo delayed the main content 16 ms less. |
| How fast does a click respond? | 40 ms | 48 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) | +153 KB | Inth added 49 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 2.63 s for Enzuzo. Inth delayed the main content 368 ms less. Both held trackers back in every check. Per vendor docs, only Inth offers open-source code and self-hosting. Per vendor docs, only Enzuzo offers a Google-certified CMP.

| Question | Inth | Enzuzo | Difference |
| --- | --- | --- | --- |
| How fast does the banner appear? | 252 ms | 2.63 s | Inth’s banner appeared 2.37 s sooner. |
| Does it slow the page down? | +400 ms (95% interval 396 ms to 408 ms) | +768 ms | Inth delayed the main content 368 ms less. |
| How fast does a click respond? | 80 ms | 96 ms | About the same. The gap is under 20%, within run-to-run noise. |
| 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) | +153 KB | Inth added 49 KB less to the first load. |

## Which features differ?

| Feature | Inth | Enzuzo |
| --- | --- | --- |
| IAB TCF | Per vendor docs | Per vendor docs (Growth plan and up) |
| IAB GPP | Per vendor docs (GPP 1.1) | Unknown |
| 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 (Growth plan and up) |
| Script blocking | Per vendor docs | Per vendor docs |
| 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 (Hosted embed only) |
| Self-hostable | Per vendor docs | Not supported (Hosted embed only) |
| Headless UI | Per vendor docs | Per vendor docs (Enterprise plan) |
| TypeScript types | Per vendor docs | Unknown |
| Free tier | Per vendor docs (Open source; hosted free plan) | Per vendor docs (5,000 visitors a month) |
| Script tag | Per vendor docs | Per vendor docs |
| React SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| 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 self-hosting
- You want a first-party SDK for React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack Start
- A fast banner matters to you: Inth’s banner appeared 424 ms sooner
- Page weight matters to you: Inth added 49 KB less to the first load

### Choose Enzuzo if

- You need a Google-certified CMP
- Page load time matters to you: Enzuzo delayed the main content 16 ms less

## Questions about this pair

### Is Enzuzo slower than Inth?

On the desktop profile, Inth’s banner appeared in a median 25 ms and Enzuzo’s in 449 ms. Enzuzo delayed the main content 16 ms less.

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

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

### Do Inth and Enzuzo 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 Didomi](https://cookiebench.com/compare/inth-vs-didomi.md)
- [Inth vs Osano](https://cookiebench.com/compare/inth-vs-osano.md)
- [Inth vs iubenda](https://cookiebench.com/compare/inth-vs-iubenda.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".
