c15t vs Cookie Control: cookie banner speed and features compared
On desktop, c15t showed its banner sooner, in a median 60 ms against 385 ms for Cookie Control. Their delay to the main content was about the same. They are less than 16 ms apart. Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for Cookie Control. Per vendor docs, only c15t offers open-source code and self-hosting. Per vendor docs, only Cookie Control offers a Google-certified CMP.
c15t Tested: 3.0.0-alpha.10
All c15t results
Cookie Control Tested: v9, hosted
All Cookie Control results
Which is faster, c15t 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. | 60 ms | 385 ms | c15t’s banner appeared 325 ms sooner. |
| Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager. | +16 ms95% interval 8 ms to 40 ms | No measurable delay95% interval −16 ms to 20 ms | About the same. They are less than 16 ms apart. |
| Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant. | 16 msOne visit measured | 16 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. | +112 KB95% interval: 112 KB | +99 KB95% interval: 99 KB | Cookie Control added 13 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 | c15t | Cookie Control |
|---|---|---|
| TTFB | +17 mspage 22 ms | No measurable delaypage 6 ms |
| FCP | +28 mspage 92 ms | No measurable delaypage 64 ms |
| LCP | +16 mspage 148 ms | No measurable delaypage 128 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | c15t | Cookie Control |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | 166 ms | |
| Banner visible | 60 ms | 385 ms |
| Metric | c15t | Cookie Control |
|---|---|---|
| Screen responds | 16 ms | 16 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between c15t 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 | c15t | Cookie Control |
|---|---|---|
| Only c15t · 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 c15t or Cookie Control?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose c15t 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: c15t’s banner appeared 325 ms sooner
Choose Cookie Control if
- You need a Google-certified CMP
- Page weight matters to you: Cookie Control added 13 KB less to the first load
What was tested?
- Deployment
- Both ran as hosted services. c15t ran against the hosted inth 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 c15t and Cookie Control
Answers come from the benchmark run and from each vendor’s documentation.
On the desktop profile, c15t’s banner appeared in a median 60 ms and Cookie Control’s in 385 ms. Their delay to the main content was about the same. They are less than 16 ms apart.
No, per vendor docs. Cookie Control documents Google-certified CMP support. c15t 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
c15tvs
OneTrustc15t’s banner 570 ms sooner · 1 standard differs
c15tvs
CookieYesc15t’s banner 327 ms sooner · 1 standard differsc15tvs
Usercentricsc15t’s banner 612 ms sooner · 1 standard differsc15tvs
Didomic15t’s banner 406 ms sooner · 1 standard differsc15tvs
Osanoc15t’s banner 584 ms sooner · 1 standard differsc15tvs
iubendac15t’s banner 371 ms sooner · 1 standard differs