c15t vs Osano: cookie banner speed and features compared
On desktop, c15t showed its banner sooner, in a median 27 ms against 644 ms for Osano. Their delay to the main content was about the same. They are less than 16 ms apart. Both held trackers back in every check. Per vendor docs, only c15t offers self-hosting. Per vendor docs, only Osano offers a Google-certified CMP.
c15t Tested: 3.0.0-alpha.11
All c15t results
Osano Tested: Hosted
All Osano results
Which is faster, c15t or Osano?
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. | 27 ms | 644 ms | c15t’s banner appeared 617 ms sooner. |
| Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager. | +8 ms95% interval 8 ms to 16 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. | 40 msOne visit measured | 32 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 | +87 KB95% interval 85 KB to 87 KB | Osano added 17 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 | Osano |
|---|---|---|
| TTFB | +6 mspage 9 ms | No measurable delaypage 6 ms |
| FCP | +12 mspage 44 ms | No measurable delaypage 68 ms |
| LCP | +8 mspage 92 ms | No measurable delaypage 120 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | c15t | Osano |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | 81 ms | |
| Banner visible | 27 ms | 644 ms |
| Metric | c15t | Osano |
|---|---|---|
| Screen responds | 40 ms | 32 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between c15t and Osano?
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 | Osano |
|---|---|---|
| Only c15t · 2 | ||
| Self-hostableDeveloper | Per vendor docs (vendor documentation, opens in a new tab) | Hosted script (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 Osano · 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 | ||
| Headless UIDeveloper | Per vendor docs (vendor documentation, opens in a new tab) | Unknown |
Same on both · 12
Should you choose c15t or Osano?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose c15t 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: c15t’s banner appeared 617 ms sooner
Choose Osano if
- You need a Google-certified CMP
- Page weight matters to you: Osano added 17 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. Osano ran from its vendor-hosted service. Network distance to each vendor is part of the result.
Questions about c15t and Osano
Answers come from the benchmark run and from each vendor’s documentation.
On the desktop profile, c15t’s banner appeared in a median 27 ms and Osano’s in 644 ms. Their delay to the main content was about the same. They are less than 16 ms apart.
No, per vendor docs. Osano 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
OneTrustc15t’s banner 603 ms sooner · 1 standard differs
c15tvs
CookieYesc15t’s banner 361 ms sooner · 1 standard differsc15tvs
Usercentricsc15t’s banner 645 ms sooner · 1 standard differsc15tvs
Didomic15t’s banner 439 ms sooner · 1 standard differsc15tvs
iubendac15t’s banner 405 ms sooner · 1 standard differsc15tvs
Ketchc15t’s banner 1.65 s sooner · 1 standard differs