# iubenda vs CookieYes: cookie banner speed and features On desktop, iubenda and CookieYes showed their banners in about the same time. The medians were 431 ms for iubenda and 387 ms for CookieYes. Neither added a measurable delay. Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. 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 | CookieYes | Difference | | --- | --- | --- | --- | | How fast does the banner appear? | 431 ms | 387 ms | About the same. The gap is under 20%, within run-to-run noise. | | 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 | 3 of 4 checks passed. We could not check the other 1 | Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. | | How much does it add to the page? | +122 KB (95% interval: 122 KB) | +31 KB (95% interval: 31 KB) | CookieYes added 91 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 and CookieYes showed their banners in about the same time. The medians were 2.66 s for iubenda and 2.42 s for CookieYes. CookieYes delayed the main content 436 ms less. Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. Their documented features are the same in this comparison. | Question | iubenda | CookieYes | Difference | | --- | --- | --- | --- | | How fast does the banner appear? | 2.66 s | 2.42 s | About the same. The gap is under 20%, within run-to-run noise. | | Does it slow the page down? | +612 ms (95% interval 600 ms to 624 ms) | +176 ms (95% interval 148 ms to 212 ms) | CookieYes delayed the main content 436 ms less. | | How fast does a click respond? | 32 ms | 24 ms | About the same. They are less than 16 ms apart. | | Does it block trackers until consent? | 4 of 4 checks passed | 3 of 4 checks passed. We could not check the other 1 | Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. | | How much does it add to the page? | +122 KB (95% interval: 122 KB) | +31 KB (95% interval: 31 KB) | CookieYes added 91 KB less to the first load. | ## Which features differ? | Feature | iubenda | CookieYes | | --- | --- | --- | | IAB TCF | Per vendor docs (TCF v2.2) | Per vendor docs (Pro and Ultimate plans) | | IAB GPP | Per vendor docs | Unknown | | 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 (Pro and Ultimate plans) | | Geo-targeted banners | Per vendor docs (Advanced and Ultimate plans) | Per vendor docs (Pro and Ultimate plans) | | Script blocking | Per vendor docs | Per vendor docs | | Consent records | Per vendor docs | Per vendor docs | | Cookie scanning | Per vendor docs | Per vendor docs | | Open source | Not supported (Hosted embed only) | Not supported (Proprietary) | | Self-hostable | Not supported (Hosted embed only) | Unknown | | Headless UI | Partial (Experimental) | Unknown | | TypeScript types | Unknown | Unknown | | Free tier | Per vendor docs (Under 5,000 pageviews a month) | Per vendor docs (5,000 pageviews 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 - Nothing measured or documented here favours iubenda. Decide on price, support and the tools that you already use ### Choose CookieYes if - Page weight matters to you: CookieYes added 91 KB less to the first load ## Questions about this pair ### Is iubenda faster than CookieYes? Not in a way this run can separate. Their banner times were about the same. The gap is under 20%, within run-to-run noise. Neither added a measurable delay. ### Do iubenda and CookieYes both support IAB TCF? Both document it. Statuses come from vendor docs. ### Do iubenda and CookieYes block trackers before consent? Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. 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 CookieYes](https://cookiebench.com/compare/c15t-vs-cookieyes.md) - [c15t vs iubenda](https://cookiebench.com/compare/c15t-vs-iubenda.md) - [CookieYes vs OneTrust](https://cookiebench.com/compare/cookieyes-vs-onetrust.md) - [Cookie Control vs CookieYes](https://cookiebench.com/compare/cookie-control-vs-cookieyes.md) - [c15t vs OneTrust](https://cookiebench.com/compare/c15t-vs-onetrust.md) - [c15t vs Usercentrics](https://cookiebench.com/compare/c15t-vs-usercentrics.md) 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".