Do CookieYes and OneTrust both support IAB TCF?

Both document it. Statuses come from vendor docs.

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

CookieYes vs OneTrust: cookie banner speed and features compared

Results forFramework

On desktop, CookieYes showed its banner sooner, in a median 387 ms against 629 ms for OneTrust. 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.

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

OneTrustOneTrust

OneTrust Tested: Hosted
All OneTrust results

Which is faster, CookieYes or OneTrust?

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

CookieYes and OneTrust on the desktop profile, Next.js 16
Question	CookieYes	OneTrust	Difference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.	387 msModerate	629 msModerate	CookieYes’ banner appeared 242 ms sooner.
Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager.	No measurable delay95% interval −12 ms to 24 msNone	No measurable delay95% interval −20 ms to 20 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	24 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.	3 of 4 checks passed1 could not be checkedPartly checked	4 of 4 checks passedBlocked	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.	+31 KB95% interval: 31 KBLight	+211 KB95% interval: 211 KBModerate	CookieYes added 180 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	CookieYes	OneTrust
TTFB	No measurable delaypage 8 ms	No measurable delaypage 6 ms
FCP	No measurable delaypage 64 ms	No measurable delaypage 60 ms
LCP	No measurable delaypage 132 ms	No measurable delaypage 124 ms
CLS	No measurable shiftpage 0.00	No measurable shiftpage 0.00

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

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

Which features differ between CookieYes and OneTrust?

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 CookieYes and OneTrust, from vendor docs
Feature	CookieYesCookieYes	OneTrustOneTrust
Only CookieYes · 1
Free tierPricing	5,000 pageviews a month (vendor documentation, opens in a new tab)	Quote-based pricing (vendor documentation, opens in a new tab)
Not confirmed for one side · 3
IAB GPPStandards	Unknown	Per vendor docs (vendor documentation, opens in a new tab)
Self-hostableDeveloper	Unknown	Script only; hosted backend (vendor documentation, opens in a new tab)
Headless UIDeveloper	Unknown	Mobile and CTV only (vendor documentation, opens in a new tab)

Same on both · 12

Features with the same status for CookieYes and OneTrust
Feature	CookieYesCookieYes	OneTrustOneTrust
IAB TCFStandards	Pro and Ultimate plans (vendor documentation, opens in a new tab)	TCF v2.2 and v2.3 (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	Pro and Ultimate plans (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliance	Pro and Ultimate plans (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)	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)
TypeScript typesDeveloper	Unknown	Unknown
Script tagFrameworks	Per 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 Start	Script tag only (vendor documentation, opens in a new tab)	Script tag only (vendor documentation, opens in a new tab)