Osano vs OneTrust: cookie banner speed and features compared
On desktop, Osano and OneTrust showed their banners in about the same time. The medians were 644 ms for Osano and 629 ms for OneTrust. Neither added a measurable delay. Both held trackers back in every check. Per vendor docs, only Osano offers open-source code and a free tier. Per vendor docs, only OneTrust offers self-hosting.
Osano Tested: Hosted
All Osano results
OneTrust Tested: Hosted
All OneTrust results
Which is faster, Osano 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. | 644 ms | 629 ms | About the same. They are less than 16 ms apart. |
| Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager. | No measurable delay95% interval −20 ms to 20 ms | No measurable delay95% interval −20 ms to 20 ms | Neither added a measurable delay. |
| Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant. | 32 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. | +87 KB95% interval 85 KB to 87 KB | +211 KB95% interval: 211 KB | Osano added 124 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 | Osano | OneTrust |
|---|---|---|
| TTFB | No measurable delaypage 6 ms | No measurable delaypage 6 ms |
| FCP | No measurable delaypage 68 ms | No measurable delaypage 60 ms |
| LCP | No measurable delaypage 120 ms | No measurable delaypage 124 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | Osano | OneTrust |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | ||
| Banner visible | 644 ms | 629 ms |
| Metric | Osano | OneTrust |
|---|---|---|
| Screen responds | 32 ms | 24 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between Osano 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 | Osano | OneTrust |
|---|---|---|
| Only Osano · 2 | ||
| Open sourceDeveloper | Older library only (vendor documentation, opens in a new tab) | Proprietary (vendor documentation, opens in a new tab) |
| Free tierPricing | About 5,000 pageviews a month (vendor documentation, opens in a new tab) | Quote-based pricing (vendor documentation, opens in a new tab) |
| Only OneTrust · 1 | ||
| Self-hostableDeveloper | Hosted script (vendor documentation, opens in a new tab) | Script only; hosted backend (vendor documentation, opens in a new tab) |
| Not confirmed for one side · 2 | ||
| Headless UIDeveloper | Unknown | Mobile and CTV only (vendor documentation, opens in a new tab) |
| TypeScript typesDeveloper | React Native SDK only (vendor documentation, opens in a new tab) | Unknown |
Same on both · 11
Should you choose Osano or OneTrust?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose Osano if
- You want open-source code and a free tier
- Page weight matters to you: Osano added 124 KB less to the first load
Choose OneTrust if
- You want self-hosting
What was tested?
- Deployment
- Both ran from their vendor-hosted services. Network distance to each vendor is part of the result.
Questions about Osano and OneTrust
Answers come from the benchmark run and from each vendor’s documentation.
Not in a way this run can separate. Their banner times were about the same. They are less than 16 ms apart. Neither added a measurable delay.
Both document it. Statuses come from vendor docs.
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 570 ms sooner · 1 standard differs
c15tvs
Osanoc15t’s banner 584 ms sooner · 1 standard differsOneTrustvs
DidomiDidomi’s banner 164 ms sooner · 1 framework SDK differs
CookieYesvsOneTrustCookieYes’ banner 242 ms sooner · 1 feature differs
OneTrustvs
UsercentricsBanner times about the same · 2 features differ
KetchvsOneTrustOneTrust’s banner 1.05 s sooner · 3 features differ