Inth vs Ketch: cookie banner speed and features compared
On desktop, Inth showed its banner sooner, in a median 25 ms against 1.82 s for Ketch. Ketch delayed the main content 16 ms less. Both held trackers back in every check. Per vendor docs, only Inth offers self-hosting. Per vendor docs, only Ketch offers a Google-certified CMP.
Inth Tested: 3.0.0
All Inth results
Ketch Tested: Hosted
All Ketch results
Which is faster, Inth or Ketch?
Shorter bars are better. The exception is tracker blocking, where the bar shows the share of checks passed.
| Question | Difference | ||
|---|---|---|---|
| Banner appearsTime from navigation until the banner is visible on screen. Lower is better. | 25 ms | 1.82 s | Inth’s banner appeared 1.80 s sooner. |
| Page slowed byExtra time before the main content paints, compared with the same page without a consent manager. | +16 ms95% interval 4 ms to 24 ms | 0 ms | Ketch delayed the main content 16 ms less. |
| Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant. | 40 msOne visit measured | 40 msOne visit measured | 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. | 4 of 4 checks passed | 4 of 4 checks passed | Both held trackers back in every check. |
| Adds to pageExtra data transferred during the first load, compared with the same page without a consent manager. | +104 KB95% interval: 104 KB | +534 KB | Inth added 430 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.
| Metric | Inth | Ketch |
|---|---|---|
| TTFB | +5 mspage 8 ms | +0 mspage 3 ms |
| FCP | +12 mspage 40 ms | 0 mspage 28 ms |
| LCP | +16 mspage 92 ms | 0 mspage 72 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | Inth | Ketch |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | 76 ms | |
| Banner visible | 25 ms | 1.82 s |
| Metric | Inth | Ketch |
|---|---|---|
| Screen responds | 40 ms | 40 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between Inth and Ketch?
Statuses come from each vendor’s documentation. Each status links to its source.
- Verified by test
- Per vendor docs
- Partial
- Not supported
- Unknown
| Feature | Inth | Ketch |
|---|---|---|
| Only Inth · 2 | ||
| Self-hostableDeveloper | Per vendor docs (vendor documentation, opens in a new tab) | Hosted service (vendor documentation, opens in a new tab) |
| First-party SDKsFrameworks | React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start (vendor documentation, opens in a new tab) | Script tag only (vendor documentation, opens in a new tab) |
| Only Ketch · 1 | ||
| Google-certified CMPStandards | Not on Google’s list (vendor documentation, opens in a new tab) | Per vendor docs (vendor documentation, opens in a new tab) |
Same on both · 13
Should you choose Inth or Ketch?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose Inth if
- You want self-hosting
- You want a first-party SDK for React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack Start
- A fast banner matters to you: Inth’s banner appeared 1.80 s sooner
- Page weight matters to you: Inth added 430 KB less to the first load
Choose Ketch if
- You need a Google-certified CMP
- Page load time matters to you: Ketch delayed the main content 16 ms less
What was tested?
- Deployment
- Both ran as hosted services. Inth ran against its hosted backend, not a local mock. Ketch ran from its vendor-hosted service. Network distance to each vendor is part of the result.
Questions about Inth and Ketch
Answers come from the benchmark run and from each vendor’s documentation.
On the desktop profile, Inth’s banner appeared in a median 25 ms and Ketch’s in 1.82 s. Ketch delayed the main content 16 ms less.
No, per vendor docs. Ketch documents Google-certified CMP support. Inth does not.
Both held trackers back in every check. 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.
Other comparisons
InthvsOneTrustInth’s banner 615 ms sooner · 1 standard differs
Inthvs
CookieYesInth’s banner 368 ms sooner · 1 standard differs
Inthvs
UsercentricsInth’s banner 679 ms sooner · 1 standard differs
Inthvs
DidomiInth’s banner 430 ms sooner · 1 standard differs
Inthvs
OsanoInth’s banner 600 ms sooner · 1 standard differs
Inthvs
iubendaInth’s banner 384 ms sooner · 1 standard differs