Osano vs Usercentrics: cookie banner speed and features compared
On desktop, Osano and Usercentrics showed their banners in about the same time. The medians were 644 ms for Osano and 672 ms for Usercentrics. Neither added a measurable delay. Both held trackers back in every check. Per vendor docs, only Osano offers open-source code.
Osano Tested: Hosted
All Osano results
Usercentrics Tested: Hosted
All Usercentrics results
Which is faster, Osano or Usercentrics?
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 | 672 ms | About the same. The gap is under 20%, within run-to-run noise. |
| 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 −16 ms to 16 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 | 16 msOne visit measured | Usercentrics responded 16 ms sooner. Both are under 200 ms, which feels instant. |
| 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 | +164 KB95% interval: 164 KB | Osano added 77 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 | Usercentrics |
|---|---|---|
| TTFB | No measurable delaypage 6 ms | No measurable delaypage 5 ms |
| FCP | No measurable delaypage 68 ms | No measurable delaypage 64 ms |
| LCP | No measurable delaypage 120 ms | No measurable delaypage 120 ms |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | Osano | Usercentrics |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | ||
| Banner visible | 644 ms | 672 ms |
| Metric | Osano | Usercentrics |
|---|---|---|
| Screen responds | 32 ms | 16 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between Osano and Usercentrics?
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 | Usercentrics |
|---|---|---|
| Only Osano · 1 | ||
| Open sourceDeveloper | Older library only (vendor documentation, opens in a new tab) | Commercial licence (vendor documentation, opens in a new tab) |
| Not confirmed for one side · 1 | ||
| Headless UIDeveloper | Unknown | Per vendor docs (vendor documentation, opens in a new tab) |
Same on both · 14
Should you choose Osano or Usercentrics?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose Osano if
- You want open-source code
- Page weight matters to you: Osano added 77 KB less to the first load
Choose Usercentrics if
- Nothing measured or documented here favours Usercentrics. Decide on price, support and the tools that you already use
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 Usercentrics
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. The gap is under 20%, within run-to-run noise. 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
Usercentricsc15t’s banner 645 ms sooner · 1 standard differsc15tvs
Osanoc15t’s banner 617 ms sooner · 1 standard differsOneTrustvs
UsercentricsBanner times about the same · 2 features differ
OsanovsOneTrustBanner times about the same · 3 features differ
Didomivs
UsercentricsDidomi’s banner 206 ms sooner · 2 features differc15tvs
OneTrustc15t’s banner 603 ms sooner · 1 standard differs