Do Osano and CookieYes both support IAB TCF?

Both document it. Statuses come from vendor docs.

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

Osano vs CookieYes: cookie banner speed and features compared

Results forFramework

On desktop, CookieYes showed its banner sooner, in a median 387 ms against 644 ms for Osano. 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 Osano offers open-source code.

OsanoOsano

Osano Tested: Hosted
All Osano results

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

Which is faster, Osano or CookieYes?

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

Osano and CookieYes on the desktop profile, Next.js 16
Question	Osano	CookieYes	Difference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.	644 msModerate	387 msModerate	CookieYes’ banner appeared 257 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 −20 ms to 20 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.	32 msOne visit measuredFast	16 msOne visit measuredFast	CookieYes responded 16 ms sooner. Both are under 200 ms, which feels instant.
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.	+87 KB95% interval 85 KB to 87 KBLight	+31 KB95% interval: 31 KBLight	CookieYes added 56 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	Osano	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	Osano	CookieYes
CMP script requested
CMP script loaded
Consent state known
Banner visible	644 ms	387 ms

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

Which features differ between Osano 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 Osano and CookieYes, from vendor docs
Feature	OsanoOsano	CookieYesCookieYes
Only Osano · 1
Open sourceDeveloper	Older library only (vendor documentation, opens in a new tab)	Proprietary (vendor documentation, opens in a new tab)
Not confirmed for one side · 3
IAB GPPStandards	Per vendor docs (vendor documentation, opens in a new tab)	Unknown
Self-hostableDeveloper	Hosted script (vendor documentation, opens in a new tab)	Unknown
TypeScript typesDeveloper	React Native SDK only (vendor documentation, opens in a new tab)	Unknown

Same on both · 12

Features with the same status for Osano and CookieYes
Feature	OsanoOsano	CookieYesCookieYes
IAB TCFStandards	TCF v2 (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	Paid plans (vendor documentation, opens in a new tab)	Per vendor docs (vendor documentation, opens in a new tab)
Consent recordsCompliance	Paid plans (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)
Headless UIDeveloper	Unknown	Unknown
Free tierPricing	About 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 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)