How fast does the banner appear?
Median of 15 visits.
All 6 integrations, best first
- Script tag7.52 s
- React7.54 s
- Astro7.67 s
- Nuxt7.68 s
- TanStack Start7.85 s
- Next.js7.95 s
In our tests with its Script tag integration, Ketch showed its cookie banner in a median 7.52 s on an emulated mid-tier phone. It delayed the main content by 1.90 s. Accept responded in 32 ms and Reject in 32 ms. It held trackers back in all 4 consent checks.
On desktop, the banner took 1.65 s. Per vendor docs, Ketch supports IAB TCF, IAB GPP, Google Consent Mode v2, Google CMP certification and Global Privacy Control.
On Script tag. We measured other CMPs on Next.js only, so this comparison uses Ketch’s other integrations.
Median of 15 visits.
Compared with the same page without a consent manager. There were too few paired visits to calculate an interval.
Reject responded in 32 ms. Under 200 ms feels instant.
No tracker ran and the page set no cookie before the visitor chose.
Each status comes from Ketch’s documentation. CookieBench does not test these features unless a line says so.
| Feature | Status |
|---|---|
| IAB TCF | TCF v2.2 (vendor documentation, opens in a new tab) |
| IAB GPP | Per vendor docs (vendor documentation, opens in a new tab) |
| Google Consent Mode v2 | Per vendor docs (vendor documentation, opens in a new tab) |
| Google-certified CMP | Per vendor docs (vendor documentation, opens in a new tab) |
| Global Privacy Control | Per vendor docs (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Geo-targeted banners | Per vendor docs (vendor documentation, opens in a new tab) |
| Script blocking | Tag orchestration (vendor documentation, opens in a new tab) |
| Consent records | Per vendor docs (vendor documentation, opens in a new tab) |
| Cookie scanning | Per vendor docs (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Open source | SDKs and samples only (vendor documentation, opens in a new tab) |
| Self-hostable | Hosted service (vendor documentation, opens in a new tab) |
| Headless UI | Per vendor docs (vendor documentation, opens in a new tab) |
| TypeScript types | Per vendor docs (vendor documentation, opens in a new tab) |
| Feature | Status |
|---|---|
| Free tier | 5,000 users (vendor documentation, opens in a new tab) |
Support per Ketch’s documentation.
Each row is a separate app. We measured each one against the same app without a consent manager. The rows compare integrations, not frameworks.
| Framework | Banner appears | Page slowed by | Click responds in | Trackers blocked |
|---|---|---|---|---|
| Script tagShown above | 7.52 s | +1.90 s | 32 msOne visit measured | 4 of 4 passed |
| React | 7.54 s | +1.62 s | 32 msOne visit measured | 4 of 4 passed |
| Next.jsShared with every CMP | 7.95 s | +1.74 s | 40 msOne visit measured | 4 of 4 passed |
| Nuxt | 7.68 s | +1.75 s | 32 msOne visit measured | 4 of 4 passed |
| Astro | 7.67 s | +1.95 s | 40 msOne visit measured | 4 of 4 passed |
| TanStack Start | 7.85 s | +1.75 s | 32 msOne visit measured | 4 of 4 passed |
Lab detail for engineers. All Core Web Vitals are here. The summary leaves some of them out.
The banner was visible at 7.52 s. The published results do not show when Ketch started to load.
| Event | Time from navigation |
|---|---|
| First byte (TTFB) | 2 ms |
| First paint (FCP) | 244 ms |
| Largest paint (LCP) | 4.77 s |
| Banner visible | 7.52 s |
| CMP requested | |
| CMP loaded | |
| Consent state known |
Each row shows the value on the page with the consent manager. It also shows how far the value moved from the same page without one.
| Measure | With Ketch | Difference |
|---|---|---|
| TTFBTime to first byte | 2 ms | +0 msNo interval reported |
| FCPFirst Contentful Paint | 244 ms | +8 msNo interval reported |
| LCPLargest Contentful Paint | 4.77 s | +1.90 sNo interval reported |
| CLSCumulative Layout Shift | 0.00 | 0.00No interval reported |
| Primary content paintThe page’s main content, not the banner | 4.77 s | +1.90 sNo interval reported |
LCP times the largest element on screen. If that is the banner, LCP measures the banner instead of the page.
There is no LCP attribution for this profile and framework.
The screen responded to Accept in 32 ms.
| Event | Time from the click |
|---|---|
| Screen responds | 32 ms |
| Banner gone | |
| Consent applied | |
| Analytics active |
Initial transfer happens before the page settles. Deferred transfer comes after.
| Measure | With Ketch | Difference |
|---|---|---|
| Initial transferBytes before the page settles | 1.03 MB | +532 KBNo interval reported |
| Deferred transferBytes loaded later | Not compared | |
| RequestsAll requests | 15 | +9No interval reported |
| Third-party requestsRequests to other hosts | 9 | +9No interval reported |
Long tasks are stretches over 50 ms when the page cannot respond to taps or keys.
| Measure | With Ketch | Difference |
|---|---|---|
| Long-task timeBlocking time during load | 976 ms | +976 msNo interval reported |
A visitor who accepted on an earlier visit comes back. We check that the banner stays hidden.
matrix-2026-10-11On desktop, it appeared in a median 1.68 s, against 471 ms for the median of the 10 CMPs measured. On an emulated mid-tier phone, it appeared in a median 7.95 s, against 2.71 s for the median of the 10 CMPs measured.
On desktop it delayed the main content by 0 ms. On an emulated mid-tier phone it delayed the main content by 1.74 s. Delay is the extra time before the main content appears. We compare Largest Contentful Paint on the same page, with and without a consent manager.
It passed 4 of 4 checks on desktop and on an emulated mid-tier phone. A check fails if a tracker runs, the page sets a cookie or data leaves the page before the visitor chooses.
Per vendor docs, Ketch supports IAB TCF, IAB GPP, Google Consent Mode v2, Google CMP certification and Global Privacy Control. Feature support comes from Ketch’s documentation. CookieBench did not test these features itself.