Skip to main content

Inth vs CookieYes: cookie banner speed and features compared

Results for

On emulated mobile, Inth showed its banner sooner, in a median 252 ms against 2.32 s for CookieYes. CookieYes delayed the main content 220 ms less. Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. Per vendor docs, only Inth offers open-source code. Per vendor docs, only CookieYes offers a Google-certified CMP.

InthInth

Inth Tested: 3.0.0
All Inth results

CookieYesCookieYes

CookieYes Tested: Hosted
All CookieYes results

Which is faster, Inth or CookieYes?

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

Inth and CookieYes on the mobile (emulated) profile, Next.js 16
QuestionInthCookieYesDifference
Banner appearsTime from navigation until the banner is visible on screen. Lower is better.
252 msFast
2.32 sFast

Inth’s banner appeared 2.07 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
+180 ms95% interval 160 ms to 192 msSmall

CookieYes delayed the main content 220 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

CookieYes 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
3 of 4 checks passed1 could not be checkedPartly checked

Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes.

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

CookieYes added 73 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.
MetricInthCookieYes
TTFB+5 mspage 8 ms+0 mspage 4 ms
FCP+12 mspage 232 ms−4 mspage 224 ms
LCP+400 mspage 3.82 s+180 mspage 3.61 s
CLSNo measurable shiftpage 0.00No measurable shiftpage 0.00
Load timesMilliseconds from navigation.
MetricInthCookieYes
CMP script requested
CMP script loaded
Consent state known1.82 s
Banner visible252 ms2.32 s
After AcceptMilliseconds from the click.
MetricInthCookieYes
Screen responds80 ms48 ms
Banner gone
Consent applied
Analytics active

Which features differ between Inth and CookieYes?

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 CookieYes, from vendor docs
FeatureInthCookieYes
Only Inth · 2
Open sourceDeveloperApache-2.0 (vendor documentation, opens in a new tab)Proprietary (vendor documentation, opens in a new tab)
First-party SDKsFrameworksReact, Next.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 CookieYes · 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)
Not confirmed for one side · 4
IAB GPPStandardsGPP 1.1 (vendor documentation, opens in a new tab)Unknown
Self-hostableDeveloperPer vendor docs (vendor documentation, opens in a new tab)Unknown
Headless UIDeveloperPer vendor docs (vendor documentation, opens in a new tab)Unknown
TypeScript typesDeveloperPer vendor docs (vendor documentation, opens in a new tab)Unknown
Same on both · 9
Features with the same status for Inth and CookieYes
FeatureInthCookieYes
IAB TCFStandardsPer vendor docs (vendor documentation, opens in a new tab)Pro and Ultimate plans (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)Pro and Ultimate plans (vendor documentation, opens in a new tab)
Geo-targeted bannersCompliancePer vendor docs (vendor documentation, opens in a new tab)Pro and Ultimate plans (vendor documentation, opens in a new tab)
Script blockingCompliancePer vendor docs (vendor documentation, opens in a new tab)Per vendor docs (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)
Free tierPricingOpen source; hosted free plan (vendor documentation, opens in a new tab)5,000 pageviews 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)

Should you choose Inth or CookieYes?

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

Choose Inth if

  • You want open-source code
  • You want a first-party SDK for React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack Start
  • A fast banner matters to you: Inth’s banner appeared 2.07 s sooner

Choose CookieYes if

  • You need a Google-certified CMP
  • Page load time matters to you: CookieYes delayed the main content 220 ms less
  • Page weight matters to you: CookieYes added 73 KB less to the first load

What was tested?

Deployment
Both ran as hosted services. Inth ran against its hosted backend, not a local mock. CookieYes 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 CookieYes

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 CookieYes’ in 2.32 s. CookieYes delayed the main content 220 ms less.