Skip to main content

Inth vs Didomi: cookie banner speed and features compared

Results for

On emulated mobile, Inth showed its banner sooner, in a median 252 ms against 4.27 s for Didomi. Inth delayed the main content 964 ms less. Both held trackers back in every check. Per vendor docs, only Inth offers open-source code and a free tier. Per vendor docs, only Didomi offers a Google-certified CMP.

InthInth

Inth Tested: 3.0.0
All Inth results

DidomiDidomi

Didomi Tested: Hosted
All Didomi results

Which is faster, Inth or Didomi?

Shorter bars are better. The exception is tracker blocking, where the bar shows the share of checks passed.

Inth and Didomi on the mobile (emulated) profile, Next.js 16
QuestionInthDidomiDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
252 msFast
4.27 sSlow

Inth’s banner appeared 4.02 s sooner.

Page slowed byExtra time before the main content paints, compared with the same page without a consent manager.
+400 ms95% interval 396 ms to 408 msSmall
+1.36 s95% interval 1.28 s to 1.37 sLarge

Inth delayed the main content 964 ms less.

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

Didomi responded 32 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.
+104 KB95% interval: 104 KBModerate
+270 KB95% interval 254 KB to 271 KBHeavy

Inth added 166 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.
MetricInthDidomi
TTFB+5 mspage 8 ms+0 mspage 3 ms
FCP+12 mspage 232 ms+4 mspage 224 ms
LCP+400 mspage 3.82 s+1.36 spage 4.79 s
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricInthDidomi
CMP script requested
CMP script loaded
Consent state known1.82 s
Banner visible252 ms4.27 s
After AcceptMilliseconds from the click.
MetricInthDidomi
Screen responds80 ms48 ms
Banner gone
Consent applied
Analytics active

Which features differ between Inth and Didomi?

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 Inth and Didomi, from vendor docs
FeatureInthDidomi
Only Inth · 3
Open sourceDeveloperApache-2.0 (vendor documentation, opens in a new tab)Proprietary (vendor documentation, opens in a new tab)
Free tierPricingOpen source; hosted free plan (vendor documentation, opens in a new tab)Contact sales (vendor documentation, opens in a new tab)
First-party SDKsFrameworksNext.js, Vue, Nuxt, Svelte, SvelteKit, Astro, TanStack Start (vendor documentation, opens in a new tab)Script tag only (vendor documentation, opens in a new tab)
Only Didomi · 1
Google-certified CMPStandardsNot on Google’s list (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Same on both · 13
Features with the same status for Inth and Didomi
FeatureInthDidomi
IAB TCFStandardsPer vendor docs (vendor documentation, opens in a new tab)TCF v2.2 (vendor documentation, opens in a new tab)
IAB GPPStandardsGPP 1.1 (vendor documentation, opens in a new tab)Per vendor docs (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)
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)Per vendor docs (vendor documentation, opens in a new tab)
Script blockingCompliancePer vendor docs (vendor documentation, opens in a new tab)Tag-based (vendor documentation, opens in a new tab)
Consent recordsComplianceWith a backend (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Cookie scanningComplianceVia Inth Website Audit (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
Self-hostableDeveloperPer vendor docs (vendor documentation, opens in a new tab)Assets through your domain (vendor documentation, opens in a new tab)
Headless UIDeveloperPer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (vendor documentation, opens in a new tab)
TypeScript typesDeveloperPer vendor docs (vendor documentation, opens in a new tab)React SDK only (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 SDKsFrameworksReact (vendor documentation, opens in a new tab)React (vendor documentation, opens in a new tab)

Should you choose Inth or Didomi?

We built these lists from the measured and documented differences above. Neither list is a recommendation.

Choose Inth if

  • You want open-source code and a free tier
  • You want a first-party SDK for Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack Start
  • A fast banner matters to you: Inth’s banner appeared 4.02 s sooner
  • Page load time matters to you: Inth delayed the main content 964 ms less

Choose Didomi if

  • You need a Google-certified CMP

What was tested?

Deployment
Both ran as hosted services. Inth ran against its hosted backend, not a local mock. Didomi ran from its vendor-hosted service. Network distance to each vendor is part of the result.

How we test: methodology cookiebench-v3.2.4

Questions about Inth and Didomi

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

On the emulated mobile profile, Inth’s banner appeared in a median 252 ms and Didomi’s in 4.27 s. Inth delayed the main content 964 ms less.