c15t vs OneTrust: cookie banner speed and features compared
On desktop, c15t showed its banner in a median 65 ms, against 672 ms for OneTrust. c15t added 32 ms before the main content appeared (95% interval 16–48 ms); OneTrust added no measurable delay. OneTrust transferred 211 KB more than a page without a consent manager, c15t 114 KB.
c15t Tested: 3.0.0-alpha.10
All c15t results
OneTrust Tested: Hosted
All OneTrust results
Which is faster, c15t or OneTrust?
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 | 629 ms | c15t’s banner appeared 570 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 −20 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 | 24 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. | +112 KB95% interval: 112 KB | +211 KB95% interval: 211 KB | c15t added 99 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 | OneTrust |
|---|---|---|
| TTFB | +17 mspage 22 ms | No measurable delaypage 6 ms |
| FCP | +28 mspage 92 ms | No measurable delaypage 60 ms |
| LCP | +16 mspage 148 ms | No measurable delaypage 124 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | c15t | OneTrust |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | 166 ms | |
| Banner visible | 60 ms | 629 ms |
| Metric | c15t | OneTrust |
|---|---|---|
| Screen responds | 16 ms | 24 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between c15t and OneTrust?
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 | OneTrust |
|---|---|---|
| Only c15t · 3 | ||
| Open sourceDeveloper | Apache-2.0 (vendor documentation, opens in a new tab) | Proprietary (vendor documentation, opens in a new tab) |
| Free tierPricing | Open source; hosted free plan (vendor documentation, opens in a new tab) | Quote-based pricing (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 OneTrust · 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 · 1 | ||
| TypeScript typesDeveloper | Per vendor docs (vendor documentation, opens in a new tab) | Unknown |
Same on both · 11
Should you choose c15t or OneTrust?
The CookieBench maintainers wrote these lists from the results and features above.
Choose c15t if
- Banner speed matters on content pages
Choose OneTrust if
- Your privacy team already runs other OneTrust modules
What was tested?
- Deployment
- Both ran as hosted services. c15t ran against the hosted inth backend, not a local mock. OneTrust ran from its vendor-hosted service. Network distance to each vendor is part of the result.
Questions about c15t and OneTrust
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 OneTrust’s in 629 ms. Their delay to the main content was about the same. They are less than 16 ms apart.
No, per vendor docs. OneTrust documents Google-certified CMP support. c15t 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
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 differsc15tvs
Ketchc15t’s banner 1.62 s sooner · 1 standard differs