--- title: "iubenda vs Usercentrics" canonical: "https://cookiebench.com/compare/iubenda-vs-usercentrics" last-updated: "2026-10-12" --- # iubenda vs Usercentrics: cookie banner speed and features On desktop, iubenda showed its banner sooner, in a median 431 ms against 672 ms for Usercentrics. Neither added a measurable delay. Both held trackers back in every check. Their documented features are the same in this comparison. 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 | iubenda | Usercentrics | Difference | | --- | --- | --- | --- | | How fast does the banner appear? | 431 ms | 672 ms | iubenda’s banner appeared 241 ms sooner. | | Does it slow the page down? | No measurable change | No measurable change | Neither added a measurable delay. | | How fast does a click respond? | 16 ms | 16 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? | +122 KB (95% interval: 122 KB) | +164 KB (95% interval: 164 KB) | iubenda added 43 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, iubenda showed its banner sooner, in a median 2.66 s against 4.16 s for Usercentrics. iubenda delayed the main content 232 ms less. Both held trackers back in every check. Their documented features are the same in this comparison. | Question | iubenda | Usercentrics | Difference | | --- | --- | --- | --- | | How fast does the banner appear? | 2.66 s | 4.16 s | iubenda’s banner appeared 1.49 s sooner. | | Does it slow the page down? | +612 ms (95% interval 600 ms to 624 ms) | +844 ms (95% interval 836 ms to 864 ms) | iubenda delayed the main content 232 ms less. | | How fast does a click respond? | 32 ms | Not measured (The click worked, but the browser reported no timing for it. That is not zero, and not proof it took under 16 ms) | No comparison. Usercentrics has no result here, so we call neither one better. | | 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? | +122 KB (95% interval: 122 KB) | +164 KB (95% interval: 164 KB) | iubenda added 43 KB less to the first load. | ## Which features differ? | Feature | iubenda | Usercentrics | | --- | --- | --- | | IAB TCF | Per vendor docs (TCF v2.2) | Per vendor docs (Pro plan and up) | | IAB GPP | Per vendor docs | Per vendor docs (v3 script tag) | | Google Consent Mode v2 | Per vendor docs | Per vendor docs | | Google-certified CMP | Per vendor docs | Per vendor docs | | Global Privacy Control | Per vendor docs | Per vendor docs | | Geo-targeted banners | Per vendor docs (Advanced and Ultimate plans) | Per vendor docs (Plus plan and up) | | Script blocking | Per vendor docs | Per vendor docs (Paid plans) | | Consent records | Per vendor docs | Per vendor docs (Kept 12 months) | | Cookie scanning | Per vendor docs | Per vendor docs | | Open source | Not supported (Hosted embed only) | Not supported (Commercial licence) | | Self-hostable | Not supported (Hosted embed only) | Not supported (Hosted backend) | | Headless UI | Partial (Experimental) | Per vendor docs | | TypeScript types | Unknown | Per vendor docs | | Free tier | Per vendor docs (Under 5,000 pageviews a month) | Per vendor docs (1,000 sessions a month) | | Script tag | Per vendor docs | Per vendor docs | | React SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Next.js SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Vue SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Nuxt SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Svelte SDK | Not supported (Script tag only) | Not supported (Script tag only) | | SvelteKit SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Astro SDK | Not supported (Script tag only) | Not supported (Script tag only) | | TanStack Start SDK | Not supported (Script tag only) | Not supported (Script tag only) | ## Which should you choose? ### Choose iubenda if - A fast banner matters to you: iubenda’s banner appeared 241 ms sooner - Page weight matters to you: iubenda added 43 KB less to the first load ### Choose Usercentrics if - Nothing measured or documented here favours Usercentrics. Decide on price, support and the tools that you already use ## Questions about this pair ### Is Usercentrics slower than iubenda? On the desktop profile, iubenda’s banner appeared in a median 431 ms and Usercentrics’ in 672 ms. Neither added a measurable delay. ### Do iubenda and Usercentrics both support IAB TCF? Both document it. Statuses come from vendor docs. ### Do iubenda and Usercentrics 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 - [c15t vs Usercentrics](https://cookiebench.com/compare/c15t-vs-usercentrics.md) - [c15t vs iubenda](https://cookiebench.com/compare/c15t-vs-iubenda.md) - [OneTrust vs Usercentrics](https://cookiebench.com/compare/onetrust-vs-usercentrics.md) - [iubenda vs CookieYes](https://cookiebench.com/compare/iubenda-vs-cookieyes.md) - [Didomi vs Usercentrics](https://cookiebench.com/compare/didomi-vs-usercentrics.md) - [c15t vs OneTrust](https://cookiebench.com/compare/c15t-vs-onetrust.md) Run `matrix-2026-10-12`, published 2026-10-12. Methodology [cookiebench-v3.2.4](https://cookiebench.com/methodology). inth, the team behind c15t, maintains CookieBench. c15t 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".