Skip to main content

c15t vs iubenda: cookie banner speed and features compared

Results for

On desktop, c15t showed its banner sooner, in a median 60 ms against 431 ms for iubenda. 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 c15t offers open-source code and self-hosting. Per vendor docs, only iubenda offers a Google-certified CMP.

c15tinth

c15t Tested: 3.0.0-alpha.10
All c15t results

iubendaiubenda

iubenda Tested: Hosted
All iubenda results

Which is faster, c15t or iubenda?

Shorter bars are better. The exception is tracker blocking, where the bar shows the share of checks passed.

c15t and iubenda on the desktop profile, Next.js 16
Questionc15tiubendaDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
60 msFast
431 msModerate

c15t’s banner appeared 371 ms sooner.

Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager.
+16 ms95% interval 8 ms to 40 msSmall
No measurable delay95% interval −16 ms to 12 msNone

About the same. The 95% intervals overlap.

Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant.
16 msOne visit measuredFast
16 msOne visit measuredFast

About the same. They are less than 16 ms apart.

Blocks trackersChecks that no tracker runs, the page sets no cookie and no data leaves the page before the visitor chooses.
4 of 4 checks passedBlocked
4 of 4 checks passedBlocked

Both held trackers back in every check.

Adds to pageExtra data transferred during the first load, compared with the same page without a consent manager.
+112 KB95% interval: 112 KBModerate
+122 KB95% interval: 122 KBModerate

c15t added 10 KB less to the first load.

“About the same” means that the two results fall within each other’s spread. We measure both against the same page without a consent manager. We do not publish a direct head-to-head interval yet.

Page vitals and load times

Lab detail for engineers. All values are medians on the desktop profile. Both CMPs ran on Next.js 16.

Page vitalsChange against the same page without a consent manager.
Metricc15tiubenda
TTFB+17 mspage 22 msNo measurable delaypage 6 ms
FCP+28 mspage 92 msNo measurable delaypage 64 ms
LCP+16 mspage 148 msNo measurable delaypage 120 ms
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
Metricc15tiubenda
CMP script requested
CMP script loaded
Consent state known166 ms
Banner visible60 ms431 ms
After AcceptMilliseconds from the click.
Metricc15tiubenda
Screen responds16 ms16 ms
Banner gone
Consent applied
Analytics active

Which features differ between c15t and iubenda?

Statuses come from each vendor’s documentation. Each status links to its source.

  • Verified by test
  • Per vendor docs
  • Partial
  • Not supported
  • Unknown
Features that differ between c15t and iubenda, from vendor docs
Featurec15tiubenda
Only c15t · 3
Open sourceDeveloperApache-2.0 (vendor documentation, opens in a new tab)Hosted embed only (vendor documentation, opens in a new tab)
Self-hostableDeveloperPer vendor docs (vendor documentation, opens in a new tab)Hosted embed only (vendor documentation, opens in a new tab)
First-party SDKsFrameworksReact, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start (vendor documentation, opens in a new tab)Script tag only (vendor documentation, opens in a new tab)
Only iubenda · 1
Google-certified CMPStandardsNot on Google’s list (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Not confirmed for one side · 1
TypeScript typesDeveloperPer vendor docs (vendor documentation, opens in a new tab)Unknown
Same on both · 11
Features with the same status for c15t and iubenda
Featurec15tiubenda
IAB TCFStandardsPer vendor docs (vendor documentation, opens in a new tab)TCF v2.2 (vendor documentation, opens in a new tab)
IAB GPPStandardsGPP 1.1 (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Google Consent Mode v2StandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Global Privacy ControlStandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliancePer vendor docs (vendor documentation, opens in a new tab)Advanced and Ultimate plans (vendor documentation, opens in a new tab)
Script blockingCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Consent recordsComplianceWith a backend (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Cookie scanningComplianceVia Inth Website Audit (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Headless UIDeveloperPer vendor docs (vendor documentation, opens in a new tab)Experimental (vendor documentation, opens in a new tab)
Free tierPricingOpen source; hosted free plan (vendor documentation, opens in a new tab)Under 5,000 pageviews a month (vendor documentation, opens in a new tab)
Script tagFrameworksPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)

Should you choose c15t or iubenda?

We built these lists from the measured and documented differences above. Neither list is a recommendation.

Choose c15t 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: c15t’s banner appeared 371 ms sooner
  • Page weight matters to you: c15t added 10 KB less to the first load

Choose iubenda if

  • You need a Google-certified CMP

What was tested?

Deployment
Both ran as hosted services. c15t ran against the hosted inth backend, not a local mock. iubenda ran from its vendor-hosted service. Network distance to each vendor is part of the result.

How we test: methodology cookiebench-v3.2.4

Questions about c15t and iubenda

Answers come from the benchmark run and from each vendor’s documentation.

On the desktop profile, c15t’s banner appeared in a median 60 ms and iubenda’s in 431 ms. Their delay to the main content was about the same. The 95% intervals overlap.