# c15t vs Osano: cookie banner speed and features

On desktop, c15t showed its banner sooner, in a median 60 ms against 644 ms for Osano. Their delay to the main content was about the same. The 95% intervals overlap. 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.

We measured both in the same run, in a Next.js app. We measured each against the same page without a consent manager. They also share Script tag, React, Nuxt, Astro, TanStack Start integrations.

## Which is faster on desktop?

Desktop profile: 1365 × 768 · No CPU slowdown · 12.5 MB/s, no added latency.

| Question | c15t | Osano | Difference |
| --- | --- | --- | --- |
| How fast does the banner appear? | 60 ms | 644 ms | c15t’s banner appeared 584 ms sooner. |
| Does it slow the page down? | +16 ms (95% interval 8 ms to 40 ms) | No measurable change | About the same. The 95% intervals overlap. |
| How fast does a click respond? | 16 ms | 32 ms | c15t responded 16 ms sooner. Both are under 200 ms, which feels instant. |
| Does it block trackers until consent? | 4 of 4 checks passed | 4 of 4 checks passed | Both held trackers back in every check. |
| How much does it add to the page? | +112 KB (95% interval: 112 KB) | +87 KB (95% interval 85 KB to 87 KB) | Osano added 25 KB less to the first load. |

## Which is faster on mobile?

Mobile (emulated) profile: 390 × 844, DPR 3 · Mid-tier phone CPU (4× slowdown) · 200 KB/s, 150 ms latency.

On emulated mobile, c15t showed its banner sooner, in a median 240 ms against 2.15 s for Osano. Their delay to the main content was about the same. The 95% intervals overlap. Osano failed 2 of 4 checks: the accept check failed and the reject check failed. c15t failed none. Per vendor docs, only c15t offers self-hosting. Per vendor docs, only Osano offers a Google-certified CMP.

| Question | c15t | Osano | Difference |
| --- | --- | --- | --- |
| How fast does the banner appear? | 240 ms | 2.15 s | c15t’s banner appeared 1.91 s sooner. |
| Does it slow the page down? | +408 ms (95% interval 396 ms to 420 ms) | +424 ms (95% interval 420 ms to 428 ms) | About the same. The 95% intervals overlap. |
| How fast does a click respond? | 32 ms | 128 ms | c15t responded 96 ms sooner. Both are under 200 ms, which feels instant. |
| Does it block trackers until consent? | 4 of 4 checks passed | 2 of 4 checks passed. 2 failed: the accept check failed, the reject check failed | Osano failed 2 of 4 checks: the accept check failed and the reject check failed. c15t failed none. |
| How much does it add to the page? | +112 KB (95% interval: 112 KB) | +85 KB (95% interval: 85 KB) | Osano added 27 KB less to the first load. |

## Which features differ?

| Feature | c15t | Osano |
| --- | --- | --- |
| IAB TCF | Per vendor docs | Per vendor docs (TCF v2) |
| IAB GPP | Per vendor docs (GPP 1.1) | Per vendor docs |
| Google Consent Mode v2 | Per vendor docs | Per vendor docs |
| Google-certified CMP | Not supported (Not on Google’s list) | Per vendor docs |
| Global Privacy Control | Per vendor docs | Per vendor docs |
| Geo-targeted banners | Per vendor docs | Per vendor docs |
| Script blocking | Per vendor docs | Per vendor docs (Paid plans) |
| Consent records | Per vendor docs (With a backend) | Per vendor docs (Paid plans) |
| Cookie scanning | Per vendor docs (Via Inth Website Audit) | Per vendor docs |
| Open source | Per vendor docs (Apache-2.0) | Partial (Older library only) |
| Self-hostable | Per vendor docs | Not supported (Hosted script) |
| Headless UI | Per vendor docs | Unknown |
| TypeScript types | Per vendor docs | Partial (React Native SDK only) |
| Free tier | Per vendor docs (Open source; hosted free plan) | Per vendor docs (About 5,000 pageviews a month) |
| Script tag | Per vendor docs | Per vendor docs |
| React SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Next.js SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Vue SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Nuxt SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Svelte SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| SvelteKit SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| Astro SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |
| TanStack Start SDK | Per vendor docs (First-party SDK) | Not supported (Script tag only) |

## Which should you choose?

### 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 584 ms sooner

### Choose Osano if

- You need a Google-certified CMP
- Page weight matters to you: Osano added 25 KB less to the first load

## Questions about this pair

### Is Osano slower than c15t?

On the desktop profile, c15t’s banner appeared in a median 60 ms and Osano’s in 644 ms. Their delay to the main content was about the same. The 95% intervals overlap.

### Does c15t support Google-certified CMP like Osano?

No, per vendor docs. Osano documents Google-certified CMP support. c15t does not.

### Do c15t and Osano block trackers before consent?

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.

## Related comparisons

- [c15t vs OneTrust](https://cookiebench.com/compare/c15t-vs-onetrust.md)
- [c15t vs CookieYes](https://cookiebench.com/compare/c15t-vs-cookieyes.md)
- [c15t vs Usercentrics](https://cookiebench.com/compare/c15t-vs-usercentrics.md)
- [c15t vs Didomi](https://cookiebench.com/compare/c15t-vs-didomi.md)
- [c15t vs iubenda](https://cookiebench.com/compare/c15t-vs-iubenda.md)
- [c15t vs Ketch](https://cookiebench.com/compare/c15t-vs-ketch.md)

Methodology [cookiebench-v3.2.4](https://cookiebench.com/methodology). inth, the team behind c15t, maintains CookieBench. c15t is one of the consent managers we measure ([disclosure](https://cookiebench.com/methodology)). Feature support comes from vendor documentation unless a row says "Verified by test".