--- title: "Ketch vs CookieYes" canonical: "https://cookiebench.com/compare/ketch-vs-cookieyes" last-updated: "2026-10-12" --- # Ketch vs CookieYes: cookie banner speed and features 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. We measured both in the same run, in a Next.js app. We measured each against the same page without a consent manager. They also share Script tag, React, Nuxt, Astro, TanStack Start integrations. ## Which is faster on desktop? Desktop profile: 1365 × 768 · No CPU slowdown · 12.5 MB/s, no added latency. | Question | Ketch | CookieYes | Difference | | --- | --- | --- | --- | | How fast does the banner appear? | 1.68 s | 387 ms | CookieYes’ banner appeared 1.29 s sooner. | | Does it slow the page down? | 0 ms | No measurable change | Ketch delayed the main content by 0 ms. CookieYes added no measurable delay. | | How fast does a click respond? | 40 ms | 16 ms | CookieYes responded 24 ms sooner. Both are under 200 ms, which feels instant. | | Does it block trackers until consent? | 4 of 4 checks passed | 3 of 4 checks passed. We could not check the other 1 | Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. | | How much does it add to the page? | +532 KB | +31 KB (95% interval: 31 KB) | CookieYes added 501 KB less to the first load. | ## Which is faster on mobile? Mobile (emulated) profile: 390 × 844, DPR 3 · Mid-tier phone CPU (4× slowdown) · 200 KB/s, 150 ms latency. On emulated mobile, CookieYes showed its banner sooner, in a median 2.42 s against 7.95 s for Ketch. CookieYes delayed the main content 1.57 s less. 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. | Question | Ketch | CookieYes | Difference | | --- | --- | --- | --- | | How fast does the banner appear? | 7.95 s | 2.42 s | CookieYes’ banner appeared 5.53 s sooner. | | Does it slow the page down? | +1.74 s | +176 ms (95% interval 148 ms to 212 ms) | CookieYes delayed the main content 1.57 s less. | | How fast does a click respond? | 40 ms | 24 ms | CookieYes responded 16 ms sooner. Both are under 200 ms, which feels instant. | | Does it block trackers until consent? | 4 of 4 checks passed | 3 of 4 checks passed. We could not check the other 1 | Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. | | How much does it add to the page? | +532 KB | +31 KB (95% interval: 31 KB) | CookieYes added 501 KB less to the first load. | ## Which features differ? | Feature | Ketch | CookieYes | | --- | --- | --- | | IAB TCF | Per vendor docs (TCF v2.2) | Per vendor docs (Pro and Ultimate plans) | | IAB GPP | Per vendor docs | Unknown | | Google Consent Mode v2 | Per vendor docs | Per vendor docs | | Google-certified CMP | Per vendor docs | Per vendor docs | | Global Privacy Control | Per vendor docs | Per vendor docs (Pro and Ultimate plans) | | Geo-targeted banners | Per vendor docs | Per vendor docs (Pro and Ultimate plans) | | Script blocking | Per vendor docs (Tag orchestration) | Per vendor docs | | Consent records | Per vendor docs | Per vendor docs | | Cookie scanning | Per vendor docs | Per vendor docs | | Open source | Partial (SDKs and samples only) | Not supported (Proprietary) | | Self-hostable | Not supported (Hosted service) | Unknown | | Headless UI | Per vendor docs | Unknown | | TypeScript types | Per vendor docs | Unknown | | Free tier | Per vendor docs (5,000 users) | Per vendor docs (5,000 pageviews a month) | | Script tag | Per vendor docs | Per vendor docs | | React SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Next.js SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Vue SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Nuxt SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Svelte SDK | Not supported (Script tag only) | Not supported (Script tag only) | | SvelteKit SDK | Not supported (Script tag only) | Not supported (Script tag only) | | Astro SDK | Not supported (Script tag only) | Not supported (Script tag only) | | TanStack Start SDK | Not supported (Script tag only) | Not supported (Script tag only) | ## Which should you choose? ### 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 ## Questions about this pair ### Is Ketch slower than CookieYes? 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. ### Do Ketch and CookieYes both support IAB TCF? Both document it. Statuses come from vendor docs. ### Do Ketch 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. ## Related comparisons - [c15t vs CookieYes](https://cookiebench.com/compare/c15t-vs-cookieyes.md) - [c15t vs Ketch](https://cookiebench.com/compare/c15t-vs-ketch.md) - [CookieYes vs OneTrust](https://cookiebench.com/compare/cookieyes-vs-onetrust.md) - [iubenda vs CookieYes](https://cookiebench.com/compare/iubenda-vs-cookieyes.md) - [Ketch vs OneTrust](https://cookiebench.com/compare/ketch-vs-onetrust.md) - [Cookie Control vs CookieYes](https://cookiebench.com/compare/cookie-control-vs-cookieyes.md) Run `matrix-2026-10-12`, published 2026-10-12. Methodology [cookiebench-v3.2.4](https://cookiebench.com/methodology). inth, the team behind c15t, maintains CookieBench. c15t is one of the consent managers we measure ([disclosure](https://cookiebench.com/methodology)). Feature support comes from vendor documentation unless a row says "Verified by test".