Inth vs Cookie Control: cookie banner speed and features compared
On desktop, Inth showed its banner sooner, in a median 25 ms against 375 ms for Cookie Control. Their delay to the main content was about the same. The 95% intervals overlap. Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for Cookie Control. Per vendor docs, only Inth offers open-source code and self-hosting. Per vendor docs, only Cookie Control offers a Google-certified CMP.
Inth Tested: 3.0.0
All Inth results
Cookie Control Tested: v9, hosted
All Cookie Control results
Which is faster, Inth or Cookie Control?
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 | 375 ms | Inth’s banner appeared 350 ms 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 | No measurable delay95% interval −12 ms to 12 ms | About the same. The 95% intervals overlap. |
| Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant. | 40 msOne visit measured | 48 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 | 3 of 4 checks passed1 could not be checked | Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for Cookie Control. |
| Adds to pageExtra data transferred during the first load, compared with the same page without a consent manager. | +104 KB95% interval: 104 KB | +99 KB95% interval: 99 KB | Cookie Control added 6 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 | Cookie Control |
|---|---|---|
| TTFB | +5 mspage 8 ms | +0 mspage 3 ms |
| FCP | +12 mspage 40 ms | 0 mspage 28 ms |
| LCP | +16 mspage 92 ms | No measurable delaypage 72 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | Inth | Cookie Control |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | 76 ms | |
| Banner visible | 25 ms | 375 ms |
| Metric | Inth | Cookie Control |
|---|---|---|
| Screen responds | 40 ms | 48 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between Inth and Cookie Control?
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 | Cookie Control |
|---|---|---|
| Only Inth · 3 | ||
| Open sourceDeveloper | Apache-2.0 (vendor documentation, opens in a new tab) | Proprietary (vendor documentation, opens in a new tab) |
| 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 Cookie Control · 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) |
| Not confirmed for one side · 2 | ||
| IAB GPPStandards | GPP 1.1 (vendor documentation, opens in a new tab) | Unknown |
| TypeScript typesDeveloper | Per vendor docs (vendor documentation, opens in a new tab) | Unknown |
Same on both · 10
Should you choose Inth or Cookie Control?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose Inth if
- You want open-source code and 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 350 ms sooner
Choose Cookie Control if
- You need a Google-certified CMP
- Page weight matters to you: Cookie Control added 6 KB less to the first load
What was tested?
- Deployment
- Both ran as hosted services. Inth ran against its hosted backend, not a local mock. Cookie Control ran from its vendor-hosted service. Network distance to each vendor is part of the result.
Questions about Inth and Cookie Control
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 Cookie Control’s in 375 ms. Their delay to the main content was about the same. The 95% intervals overlap.
No, per vendor docs. Cookie Control documents Google-certified CMP support. Inth does not.
Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for Cookie Control. 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