Skip to main content

Osano vs Usercentrics: cookie banner speed and features compared

Results for

On emulated mobile, Osano showed its banner sooner, in a median 2.15 s against 4.16 s for Usercentrics. Osano delayed the main content 420 ms less. Osano failed 2 of 4 checks: the accept check failed and the reject check failed. Usercentrics failed none. Per vendor docs, only Osano offers open-source code.

OsanoOsano

Osano Tested: Hosted
All Osano results

UsercentricsUsercentrics

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.

Osano and Usercentrics on the mobile (emulated) profile, Next.js 16
QuestionOsanoUsercentricsDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
2.15 sFast
4.16 sSlow

Osano’s banner appeared 2.01 s sooner.

Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager.
+424 ms95% interval 420 ms to 428 msSmall
+844 ms95% interval 836 ms to 864 msNoticeable

Osano delayed the main content 420 ms less.

Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant.
128 msOne visit measuredFast

No comparison. Usercentrics has no result here, so we call neither one better.

Blocks trackersChecks that no tracker runs, the page sets no cookie and no data leaves the page before the visitor chooses.
2 of 4 checks passed2 failed: the accept check failed, the reject check failedLeaked
4 of 4 checks passedBlocked

Osano failed 2 of 4 checks: the accept check failed and the reject check failed. Usercentrics failed none.

Adds to pageExtra data transferred during the first load, compared with the same page without a consent manager.
+85 KB95% interval: 85 KBLight
+164 KB95% interval: 164 KBModerate

Osano added 79 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 mobile profile. Both CMPs ran on Next.js 16.

Page vitalsChange against the same page without a consent manager.
MetricOsanoUsercentrics
TTFBNo measurable delaypage 5 msNo measurable delaypage 7 ms
FCPNo measurable delaypage 248 msNo measurable delaypage 252 ms
LCP+424 mspage 3.87 s+844 mspage 4.30 s
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricOsanoUsercentrics
CMP script requested
CMP script loaded
Consent state known
Banner visible2.15 s4.16 s
After AcceptMilliseconds from the click.
MetricOsanoUsercentrics
Screen responds128 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
Features that differ between Osano and Usercentrics, from vendor docs
FeatureOsanoUsercentrics
Only Osano · 1
Open sourceDeveloperOlder 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 UIDeveloperUnknownPer vendor docs (vendor documentation, opens in a new tab)
Same on both · 14
Features with the same status for Osano and Usercentrics
FeatureOsanoUsercentrics
IAB TCFStandardsTCF v2 (vendor documentation, opens in a new tab)Pro plan and up (vendor documentation, opens in a new tab)
IAB GPPStandardsPer vendor docs (vendor documentation, opens in a new tab)v3 script tag (vendor documentation, opens in a new tab)
Google Consent Mode v2StandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Google-certified CMPStandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Global Privacy ControlStandardsPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliancePer vendor docs (vendor documentation, opens in a new tab)Plus plan and up (vendor documentation, opens in a new tab)
Script blockingCompliancePaid plans (vendor documentation, opens in a new tab)Paid plans (vendor documentation, opens in a new tab)
Consent recordsCompliancePaid plans (vendor documentation, opens in a new tab)Kept 12 months (vendor documentation, opens in a new tab)
Cookie scanningCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Self-hostableDeveloperHosted script (vendor documentation, opens in a new tab)Hosted backend (vendor documentation, opens in a new tab)
TypeScript typesDeveloperReact Native SDK only (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Free tierPricingAbout 5,000 pageviews a month (vendor documentation, opens in a new tab)1,000 sessions a month (vendor documentation, opens in a new tab)
Script tagFrameworksPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
First-party SDKsReact, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack StartScript tag only (vendor documentation, opens in a new tab)Script tag only (vendor documentation, opens in a new tab)

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
  • A fast banner matters to you: Osano’s banner appeared 2.01 s sooner
  • Page load time matters to you: Osano delayed the main content 420 ms less
  • Page weight matters to you: Osano added 79 KB less to the first load

Choose Usercentrics if

  • You want the one that failed fewer tracker-blocking checks in this run

What was tested?

Deployment
Both ran from their vendor-hosted services. Network distance to each vendor is part of the result.

How we test: methodology cookiebench-v3.2.4

Questions about Osano and Usercentrics

Answers come from the benchmark run and from each vendor’s documentation.

On the emulated mobile profile, Osano’s banner appeared in a median 2.15 s and Usercentrics’ in 4.16 s. Osano delayed the main content 420 ms less.