CookieYes vs OneTrust: cookie banner speed and features compared
On emulated mobile, CookieYes showed its banner sooner, in a median 2.42 s against 3.92 s for OneTrust. CookieYes delayed the main content 300 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 CookieYes offers a free tier.
CookieYes Tested: Hosted
All CookieYes results
OneTrust Tested: Hosted
All OneTrust results
Which is faster, CookieYes or OneTrust?
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. | 2.42 s | 3.92 s | CookieYes’ banner appeared 1.50 s sooner. |
| Page slowed byExtra time before the main content paints (LCP), compared with the same page without a consent manager. | +176 ms95% interval 148 ms to 212 ms | +476 ms95% interval 444 ms to 508 ms | CookieYes delayed the main content 300 ms less. |
| Click responds inTime from pressing Accept until the screen updates. Under 200 ms feels instant. | 24 msOne visit measured | 16 msOne visit measured | About the same. They are less than 16 ms apart. |
| Blocks trackersChecks that no tracker runs, the page sets no cookie and no data leaves the page before the visitor chooses. | 3 of 4 checks passed1 could not be checked | 4 of 4 checks passed | 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. | +31 KB95% interval: 31 KB | +211 KB95% interval: 211 KB | CookieYes added 180 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.
| Metric | CookieYes | OneTrust |
|---|---|---|
| TTFB | No measurable delaypage 8 ms | No measurable delaypage 6 ms |
| FCP | No measurable delaypage 264 ms | No measurable delaypage 248 ms |
| LCP | +176 mspage 3.64 s | +476 mspage 3.93 s |
| CLS | No measurable shiftpage 0.00 | No measurable shiftpage 0.00 |
| Metric | CookieYes | OneTrust |
|---|---|---|
| CMP script requested | ||
| CMP script loaded | ||
| Consent state known | ||
| Banner visible | 2.42 s | 3.92 s |
| Metric | CookieYes | OneTrust |
|---|---|---|
| Screen responds | 24 ms | 16 ms |
| Banner gone | ||
| Consent applied | ||
| Analytics active |
Which features differ between CookieYes and OneTrust?
Statuses come from each vendor’s documentation. Each status links to its source.
- Verified by test
- Per vendor docs
- Partial
- Not supported
- Unknown
| Feature | CookieYes | OneTrust |
|---|---|---|
| Only CookieYes · 1 | ||
| Free tierPricing | 5,000 pageviews a month (vendor documentation, opens in a new tab) | Quote-based pricing (vendor documentation, opens in a new tab) |
| Not confirmed for one side · 3 | ||
| IAB GPPStandards | Unknown | Per vendor docs (vendor documentation, opens in a new tab) |
| Self-hostableDeveloper | Unknown | Script only; hosted backend (vendor documentation, opens in a new tab) |
| Headless UIDeveloper | Unknown | Mobile and CTV only (vendor documentation, opens in a new tab) |
Same on both · 12
Should you choose CookieYes or OneTrust?
We built these lists from the measured and documented differences above. Neither list is a recommendation.
Choose CookieYes if
- You want a free tier
- A fast banner matters to you: CookieYes’ banner appeared 1.50 s sooner
- Page load time matters to you: CookieYes delayed the main content 300 ms less
- Page weight matters to you: CookieYes added 180 KB less to the first load
Choose OneTrust if
- Nothing measured or documented here favours OneTrust. 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 CookieYes and OneTrust
Answers come from the benchmark run and from each vendor’s documentation.
On the emulated mobile profile, CookieYes’ banner appeared in a median 2.42 s and OneTrust’s in 3.92 s. CookieYes delayed the main content 300 ms less.
Both document it. Statuses come from vendor docs.
Neither leaked a tracker in the checks that ran. We could not run 1 of 4 checks for CookieYes. 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
OneTrustc15t’s banner 3.67 s sooner · 1 standard differs
c15tvs
CookieYesc15t’s banner 2.18 s sooner · 1 standard differsOneTrustvs
DidomiBanner times about the same · 1 framework SDK differsOneTrustvs
UsercentricsBanner times about the same · 2 features differ
OsanovsOneTrustOsano’s banner 1.76 s sooner · 3 features differ
iubendavs
CookieYesBanner times about the same · Same documented features