Skip to main content

CookieYes vs OneTrust: cookie banner speed and features compared

Results for

On emulated mobile, CookieYes showed its banner sooner, in a median 2.42 s against 3.92 s for OneTrust. CookieYes delayed the main content 300 ms less. 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 mobile (emulated) profile, Next.js 16
QuestionCookieYesOneTrustDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
2.42 sFast
3.92 sModerate

CookieYes’ banner appeared 1.50 s sooner.

Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager.
+176 ms95% interval 148 ms to 212 msSmall
+476 ms95% interval 444 ms to 508 msSmall

CookieYes delayed the main content 300 ms less.

Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant.
24 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.
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 mobile profile. Both CMPs ran on Next.js 16.

Page vitalsChange against the same page without a consent manager.
MetricCookieYesOneTrust
TTFBNo measurable delaypage 8 msNo measurable delaypage 6 ms
FCPNo measurable delaypage 264 msNo measurable delaypage 248 ms
LCP+176 mspage 3.64 s+476 mspage 3.93 s
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricCookieYesOneTrust
CMP script requested
CMP script loaded
Consent state known
Banner visible2.42 s3.92 s
After AcceptMilliseconds from the click.
MetricCookieYesOneTrust
Screen responds24 ms16 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
FeatureCookieYesOneTrust
Only CookieYes · 1
Free tierPricing5,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 GPPStandardsUnknownPer vendor docs (vendor documentation, opens in a new tab)
Self-hostableDeveloperUnknownScript only; hosted backend (vendor documentation, opens in a new tab)
Headless UIDeveloperUnknownMobile and CTV only (vendor documentation, opens in a new tab)
Same on both · 12
Features with the same status for CookieYes and OneTrust
FeatureCookieYesOneTrust
IAB TCFStandardsPro 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 v2StandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Google-certified CMPStandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Global Privacy ControlStandardsPro and Ultimate plans (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliancePro and Ultimate plans (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Script blockingCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Consent recordsCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Cookie scanningCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Open sourceDeveloperProprietary (vendor documentation, opens in a new tab)Proprietary (vendor documentation, opens in a new tab)
TypeScript typesDeveloperUnknownUnknown
Script tagFrameworksPer 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 StartScript tag only (vendor documentation, opens in a new tab)Script tag only (vendor documentation, opens in a new tab)

Should you choose CookieYes or OneTrust?

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

Choose CookieYes if

  • You want a free tier
  • A fast banner matters to you: CookieYes’ banner appeared 1.50 s sooner
  • Page load time matters to you: CookieYes delayed the main content 300 ms less
  • Page weight matters to you: CookieYes added 180 KB less to the first load

Choose OneTrust if

  • Nothing measured or documented here favours OneTrust. Decide on price, support and the tools that you already use

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

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

On the emulated mobile profile, CookieYes’ banner appeared in a median 2.42 s and OneTrust’s in 3.92 s. CookieYes delayed the main content 300 ms less.