Skip to main content

Cookie Control vs CookieYes: cookie banner speed and features compared

Results for

On emulated mobile, Cookie Control and CookieYes showed their banners in about the same time. The medians were 2.47 s for Cookie Control and 2.42 s for CookieYes. CookieYes delayed the main content 316 ms less. Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for Cookie Control and 1 of 4 checks for CookieYes. Their documented features are the same in this comparison.

Cookie ControlCivic

Cookie Control Tested: v9, hosted
All Cookie Control results

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

Which is faster, Cookie Control or CookieYes?

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

Cookie Control and CookieYes on the mobile (emulated) profile, Next.js 16
QuestionCookie ControlCookieYesDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
2.47 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.
+492 ms95% interval 484 ms to 504 msSmall
+176 ms95% interval 148 ms to 212 msSmall

CookieYes delayed the main content 316 ms less.

Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant.
24 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
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 Cookie Control and 1 of 4 checks for CookieYes.

Adds to pageExtra data transferred during the first load, compared with the same page without a consent manager.
+99 KB95% interval: 99 KBLight
+31 KB95% interval: 31 KBLight

CookieYes added 68 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.
MetricCookie ControlCookieYes
TTFBNo measurable delaypage 7 msNo measurable delaypage 8 ms
FCPNo measurable delaypage 248 msNo measurable delaypage 264 ms
LCP+492 mspage 3.94 s+176 mspage 3.64 s
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricCookie ControlCookieYes
CMP script requested
CMP script loaded
Consent state known
Banner visible2.47 s2.42 s
After AcceptMilliseconds from the click.
MetricCookie ControlCookieYes
Screen responds24 ms24 ms
Banner gone
Consent applied
Analytics active

Which features differ between Cookie Control 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 Cookie Control and CookieYes, from vendor docs
FeatureCookie ControlCookieYes
Not confirmed for one side · 2
Self-hostableDeveloperHosted service (vendor documentation, opens in a new tab)Unknown
Headless UIDeveloperJavaScript methods only (vendor documentation, opens in a new tab)Unknown
Same on both · 14
Features with the same status for Cookie Control and CookieYes
FeatureCookie ControlCookieYes
IAB TCFStandardsTCF v2.3 (vendor documentation, opens in a new tab)Pro and Ultimate plans (vendor documentation, opens in a new tab)
IAB GPPStandardsUnknownUnknown
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 ControlStandardsPer vendor docs (vendor documentation, opens in a new tab)Pro and Ultimate plans (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliancePaid editions (vendor documentation, opens in a new tab)Pro and Ultimate plans (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 scanningCompliancePaid editions (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
Free tierPricingCommunity edition (vendor documentation, opens in a new tab)5,000 pageviews a month (vendor documentation, opens in a new tab)
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 Cookie Control or CookieYes?

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

Choose Cookie Control if

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

Choose CookieYes if

  • Page load time matters to you: CookieYes delayed the main content 316 ms less
  • Page weight matters to you: CookieYes added 68 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 Cookie Control and CookieYes

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

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 316 ms less.