Skip to main content

Ketch vs CookieYes: cookie banner speed and features compared

Results for

On desktop, CookieYes showed its banner sooner, in a median 387 ms against 1.68 s for Ketch. Ketch delayed the main content by 0 ms. CookieYes added no 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 Ketch offers open-source code.

KetchKetch

Ketch Tested: Hosted
All Ketch results

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

Which is faster, Ketch or CookieYes?

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

Ketch and CookieYes on the desktop profile, Next.js 16
QuestionKetchCookieYesDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
1.68 sSlow
387 msModerate

CookieYes’ banner appeared 1.29 s sooner.

Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager.
0 msSmall
No measurable delay95% interval −12 ms to 24 msNone

Ketch delayed the main content by 0 ms. CookieYes added no measurable delay.

Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant.
40 msOne visit measuredFast
16 msOne visit measuredFast

CookieYes responded 24 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.
+532 KBHeavy
+31 KB95% interval: 31 KBLight

CookieYes added 501 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.
MetricKetchCookieYes
TTFB0 mspage 5 msNo measurable delaypage 8 ms
FCP−4 mspage 60 msNo measurable delaypage 64 ms
LCP0 mspage 116 msNo measurable delaypage 132 ms
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricKetchCookieYes
CMP script requested
CMP script loaded
Consent state known
Banner visible1.68 s387 ms
After AcceptMilliseconds from the click.
MetricKetchCookieYes
Screen responds40 ms16 ms
Banner gone
Consent applied
Analytics active

Which features differ between Ketch 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 Ketch and CookieYes, from vendor docs
FeatureKetchCookieYes
Only Ketch · 1
Open sourceDeveloperSDKs and samples only (vendor documentation, opens in a new tab)Proprietary (vendor documentation, opens in a new tab)
Not confirmed for one side · 4
IAB GPPStandardsPer vendor docs (vendor documentation, opens in a new tab)Unknown
Self-hostableDeveloperHosted service (vendor documentation, opens in a new tab)Unknown
Headless UIDeveloperPer vendor docs (vendor documentation, opens in a new tab)Unknown
TypeScript typesDeveloperPer vendor docs (vendor documentation, opens in a new tab)Unknown
Same on both · 11
Features with the same status for Ketch and CookieYes
FeatureKetchCookieYes
IAB TCFStandardsTCF v2.2 (vendor documentation, opens in a new tab)Pro and Ultimate plans (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 ControlStandardsPer vendor docs (vendor documentation, opens in a new tab)Pro and Ultimate plans (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliancePer vendor docs (vendor documentation, opens in a new tab)Pro and Ultimate plans (vendor documentation, opens in a new tab)
Script blockingComplianceTag orchestration (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)
Free tierPricing5,000 users (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 Ketch or CookieYes?

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

Choose Ketch if

  • You want open-source code

Choose CookieYes if

  • A fast banner matters to you: CookieYes’ banner appeared 1.29 s sooner
  • Page load time matters to you: Ketch delayed the main content by 0 ms. CookieYes added no measurable delay
  • Page weight matters to you: CookieYes added 501 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 Ketch and CookieYes

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

On the desktop profile, CookieYes’ banner appeared in a median 387 ms and Ketch’s in 1.68 s. Ketch delayed the main content by 0 ms. CookieYes added no measurable delay.