Do Didomi and CookieYes both support IAB TCF?

Both document it. Statuses come from vendor docs.

Do Didomi 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.

Didomi vs CookieYes: cookie banner speed and features compared

Results forFramework

On desktop, Didomi and CookieYes showed their banners in about the same time. The medians were 466 ms for Didomi 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. Per vendor docs, only CookieYes offers a free tier.

DidomiDidomi

Didomi Tested: Hosted
All Didomi results

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

Which is faster, Didomi or CookieYes?

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

Didomi and CookieYes on the desktop profile, Next.js 16
Question	Didomi	CookieYes	Difference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.	466 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.	+253 KB95% interval: 253 KBHeavy	+31 KB95% interval: 31 KBLight	CookieYes added 222 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.
Metric	Didomi	CookieYes
TTFB	No measurable delaypage 6 ms	No measurable delaypage 8 ms
FCP	No measurable delaypage 68 ms	No measurable delaypage 64 ms
LCP	No measurable delaypage 120 ms	No measurable delaypage 132 ms
CLS	No measurable shiftpage 0.00	No measurable shiftpage 0.00

Load timesMilliseconds from navigation.
Metric	Didomi	CookieYes
CMP script requested
CMP script loaded
Consent state known
Banner visible	466 ms	387 ms

After AcceptMilliseconds from the click.
Metric	Didomi	CookieYes
Screen responds	16 ms	16 ms
Banner gone
Consent applied
Analytics active

Which features differ between Didomi 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 Didomi and CookieYes, from vendor docs
Feature	DidomiDidomi	CookieYesCookieYes
Only Didomi · 1
First-party SDKsFrameworks	React (vendor documentation, opens in a new tab)	Script tag only (vendor documentation, opens in a new tab)
Only CookieYes · 1
Free tierPricing	Contact sales (vendor documentation, opens in a new tab)	5,000 pageviews a month (vendor documentation, opens in a new tab)
Not confirmed for one side · 4
IAB GPPStandards	Per vendor docs (vendor documentation, opens in a new tab)	Unknown
Self-hostableDeveloper	Assets through your domain (vendor documentation, opens in a new tab)	Unknown
Headless UIDeveloper	Per vendor docs (vendor documentation, opens in a new tab)	Unknown
TypeScript typesDeveloper	React SDK only (vendor documentation, opens in a new tab)	Unknown

Same on both · 11

Features with the same status for Didomi and CookieYes
Feature	DidomiDidomi	CookieYesCookieYes
IAB TCFStandards	TCF v2.2 (vendor documentation, opens in a new tab)	Pro and Ultimate plans (vendor documentation, opens in a new tab)
Google Consent Mode v2Standards	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Google-certified CMPStandards	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Global Privacy ControlStandards	Per vendor docs (vendor documentation, opens in a new tab)	Pro and Ultimate plans (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliance	Per vendor docs (vendor documentation, opens in a new tab)	Pro and Ultimate plans (vendor documentation, opens in a new tab)
Script blockingCompliance	Tag-based (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Consent recordsCompliance	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Cookie scanningCompliance	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Open sourceDeveloper	Proprietary (vendor documentation, opens in a new tab)	Proprietary (vendor documentation, opens in a new tab)
Script tagFrameworks	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
First-party SDKsNext.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start	Script tag only (vendor documentation, opens in a new tab)	Script tag only (vendor documentation, opens in a new tab)

Should you choose Didomi or CookieYes?

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

Choose Didomi if

You want a first-party SDK for React

Choose CookieYes if

You want a free tier
Page weight matters to you: CookieYes added 222 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 Didomi and CookieYes

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

Report a correction

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.