Do OneTrust and Didomi both support IAB TCF?

Both document it. Statuses come from vendor docs.

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

OneTrust vs Didomi: cookie banner speed and features compared

Results forFramework

On emulated mobile, OneTrust and Didomi showed their banners in about the same time. The medians were 3.92 s for OneTrust and 4.41 s for Didomi. OneTrust delayed the main content 804 ms less. Both held trackers back in every check. Their documented features are the same in this comparison.

OneTrustOneTrust

OneTrust Tested: Hosted
All OneTrust results

DidomiDidomi

Didomi Tested: Hosted
All Didomi results

Which is faster, OneTrust or Didomi?

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

OneTrust and Didomi on the mobile (emulated) profile, Next.js 16
Question	OneTrust	Didomi	Difference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.	3.92 sModerate	4.41 sSlow	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.	+476 ms95% interval 444 ms to 508 msSmall	+1.28 s95% interval 1.26 s to 1.29 sLarge	OneTrust delayed the main content 804 ms less.
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.	+211 KB95% interval: 211 KBModerate	+253 KB95% interval: 253 KBHeavy	OneTrust added 42 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 mobile profile. Both CMPs ran on Next.js 16.

Page vitalsChange against the same page without a consent manager.
Metric	OneTrust	Didomi
TTFB	No measurable delaypage 6 ms	No measurable delaypage 5 ms
FCP	No measurable delaypage 248 ms	No measurable delaypage 248 ms
LCP	+476 mspage 3.93 s	+1.28 spage 4.72 s
CLS	No measurable shiftpage 0.00	No measurable shiftpage 0.00

Load timesMilliseconds from navigation.
Metric	OneTrust	Didomi
CMP script requested
CMP script loaded
Consent state known
Banner visible	3.92 s	4.41 s

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

Which features differ between OneTrust and Didomi?

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 OneTrust and Didomi, from vendor docs
Feature	OneTrustOneTrust	DidomiDidomi
Only Didomi · 1
First-party SDKsFrameworks	Script tag only (vendor documentation, opens in a new tab)	React (vendor documentation, opens in a new tab)
Not confirmed for one side · 1
TypeScript typesDeveloper	Unknown	React SDK only (vendor documentation, opens in a new tab)

Same on both · 15

Should you choose OneTrust or Didomi?

The CookieBench maintainers wrote these lists from the results and features above.

Choose OneTrust if

Your privacy team already runs other OneTrust modules
Mobile load time on slow phones is a priority

Choose Didomi if

You want a dedicated consent and preference platform
Desktop banner speed matters more than page weight

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 OneTrust and Didomi

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. OneTrust delayed the main content 804 ms less.

All comparisons

Feature	OneTrustOneTrust	DidomiDidomi
IAB TCFStandards	TCF v2.2 and v2.3 (vendor documentation, opens in a new tab)	TCF v2.2 (vendor documentation, opens in a new tab)
IAB GPPStandards	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (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)	Per vendor docs (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliance	Per vendor docs (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Script blockingCompliance	Per vendor docs (vendor documentation, opens in a new tab)	Tag-based (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)
Self-hostableDeveloper	Script only; hosted backend (vendor documentation, opens in a new tab)	Assets through your domain (vendor documentation, opens in a new tab)
Headless UIDeveloper	Mobile and CTV only (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Free tierPricing	Quote-based pricing (vendor documentation, opens in a new tab)	Contact sales (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)