Skip to main content

Osano vs Usercentrics: cookie banner speed and features compared

Results for

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.

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 desktop profile, Next.js 16
QuestionOsanoUsercentricsDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
644 msModerate
672 msModerate

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 msNone
No measurable delay95% interval −16 ms to 16 msNone

Neither added a measurable delay.

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

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 passedBlocked
4 of 4 checks passedBlocked

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 KBLight
+164 KB95% interval: 164 KBModerate

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.

Page vitalsChange against the same page without a consent manager.
MetricOsanoUsercentrics
TTFBNo measurable delaypage 6 msNo measurable delaypage 5 ms
FCPNo measurable delaypage 68 msNo measurable delaypage 64 ms
LCPNo measurable delaypage 120 msNo measurable delaypage 120 ms
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricOsanoUsercentrics
CMP script requested
CMP script loaded
Consent state known
Banner visible644 ms672 ms
After AcceptMilliseconds from the click.
MetricOsanoUsercentrics
Screen responds32 ms16 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
  • 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.

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.

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.