Do Osano and CookieYes both support IAB TCF?

Both document it. Statuses come from vendor docs.

Do Osano and CookieYes block trackers before consent?

Osano failed 2 of 4 checks: the accept check failed and the reject check failed. CookieYes failed none. 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 emulated mobile, Osano and CookieYes showed their banners in about the same time. The medians were 2.15 s for Osano and 2.42 s for CookieYes. CookieYes delayed the main content 248 ms less. Osano failed 2 of 4 checks: the accept check failed and the reject check failed. CookieYes failed none. 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 mobile (emulated) profile, Next.js 16
Question	Osano	CookieYes	Difference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.	2.15 sFast	2.42 sFast	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.	+424 ms95% interval 420 ms to 428 msSmall	+176 ms95% interval 148 ms to 212 msSmall	CookieYes delayed the main content 248 ms less.
Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant.	128 msOne visit measuredFast	24 msOne visit measuredFast	CookieYes responded 104 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.	2 of 4 checks passed2 failed: the accept check failed, the reject check failedLeaked	3 of 4 checks passed1 could not be checkedPartly checked	Osano failed 2 of 4 checks: the accept check failed and the reject check failed. CookieYes failed none.
Adds to pageExtra data transferred during the first load, compared with the same page without a consent manager.	+85 KB95% interval: 85 KBLight	+31 KB95% interval: 31 KBLight	CookieYes added 54 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	Osano	CookieYes
TTFB	No measurable delaypage 5 ms	No measurable delaypage 8 ms
FCP	No measurable delaypage 248 ms	No measurable delaypage 264 ms
LCP	+424 mspage 3.87 s	+176 mspage 3.64 s
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	2.15 s	2.42 s

After AcceptMilliseconds from the click.
Metric	Osano	CookieYes
Screen responds	128 ms	24 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)

Should you choose Osano or CookieYes?

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

Choose Osano if

You want open-source code

Choose CookieYes if

Page load time matters to you: CookieYes delayed the main content 248 ms less
You want the one that failed fewer tracker-blocking checks in this run
Page weight matters to you: CookieYes added 54 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 Osano 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. CookieYes delayed the main content 248 ms less.