Skip to main content

iubenda vs CookieYes: cookie banner speed and features compared

Results for

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.

iubendaiubenda

iubenda Tested: Hosted
All iubenda results

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

Which is faster, iubenda or CookieYes?

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

iubenda and CookieYes on the desktop profile, Next.js 16
QuestioniubendaCookieYesDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
431 msModerate
387 msModerate

About the same. The gap is under 20%, within run-to-run noise.

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

Neither added a measurable delay.

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
3 of 4 checks passed1 could not be checkedPartly checked

Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes.

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

CookieYes added 91 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.
MetriciubendaCookieYes
TTFBNo measurable delaypage 6 msNo measurable delaypage 8 ms
FCPNo measurable delaypage 64 msNo measurable delaypage 64 ms
LCPNo measurable delaypage 120 msNo measurable delaypage 132 ms
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetriciubendaCookieYes
CMP script requested
CMP script loaded
Consent state known
Banner visible431 ms387 ms
After AcceptMilliseconds from the click.
MetriciubendaCookieYes
Screen responds16 ms16 ms
Banner gone
Consent applied
Analytics active

Which features differ between iubenda and CookieYes?

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 iubenda and CookieYes, from vendor docs
FeatureiubendaCookieYes
Not confirmed for one side · 3
IAB GPPStandardsPer vendor docs (vendor documentation, opens in a new tab)Unknown
Self-hostableDeveloperHosted embed only (vendor documentation, opens in a new tab)Unknown
Headless UIDeveloperExperimental (vendor documentation, opens in a new tab)Unknown
Same on both · 13
Features with the same status for iubenda and CookieYes
FeatureiubendaCookieYes
IAB TCFStandardsTCF v2.2 (vendor documentation, opens in a new tab)Pro and Ultimate plans (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)
Google-certified CMPStandardsPer 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)Pro and Ultimate plans (vendor documentation, opens in a new tab)
Geo-targeted bannersComplianceAdvanced and Ultimate plans (vendor documentation, opens in a new tab)Pro 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 recordsCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Cookie scanningCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Open sourceDeveloperHosted embed only (vendor documentation, opens in a new tab)Proprietary (vendor documentation, opens in a new tab)
TypeScript typesDeveloperUnknownUnknown
Free tierPricingUnder 5,000 pageviews a month (vendor documentation, opens in a new tab)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)
First-party SDKsReact, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack StartScript tag only (vendor documentation, opens in a new tab)Script tag only (vendor documentation, opens in a new tab)

Should you choose iubenda or CookieYes?

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

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

What was tested?

Deployment
Both ran from their vendor-hosted services. Network distance to each vendor is part of the result.

How we test: methodology cookiebench-v3.2.4

Questions about iubenda and CookieYes

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

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.