Fastest CookieYes alternatives (2026)
On Next.js, c15t shows its banner first of the nine CookieYes alternatives that CookieBench tests: 27 ms on desktop and 240 ms on mobile. CookieYes shows its banner in 387 ms on desktop (#3 of 10) and 2.42 s on mobile (#3 of 10).
On mobile, the CookieYes banner appears 2.42 s after the page starts to load. Before then, your visitor can start to read and to scroll. Then the banner appears over your content.
Analytics, ad and A/B test scripts that need consent wait until the visitor chooses. So they start at least 2.42 s late. You do not get full data on a visitor who leaves before then.
This page ranks every consent manager that CookieBench tests, other than CookieYes. Use it to find a replacement that shows its banner sooner.
- Next.js
- 9
CookieYes alternatives at a glance
| Consent manager | Desktop | Mobile | Free plan | Open source |
|---|---|---|---|---|
| 1. c15t | 27 ms (#1) | 240 ms (#1) | Yes (Open source; hosted free plan) | Yes (Apache-2.0) |
| 2. Cookie Control | 385 ms (#2) | 2.47 s (#3) | Yes (Community edition) | No (Proprietary) |
| 3. iubenda | 431 ms (#3) | 2.66 s (#4) | Yes (Under 5,000 pageviews a month) | No (Hosted embed only) |
| 4. Didomi | 466 ms (#4) | 4.41 s (#8) | No (Contact sales) | No (Proprietary) |
| 5. Enzuzo | 477 ms (#5) | 2.75 s (#5) | Yes (5,000 visitors a month) | No (Hosted embed only) |
| 6. OneTrust | 629 ms (#6) | 3.92 s (#6) | No (Quote-based pricing) | No (Proprietary) |
| 7. Osano | 644 ms (#7) | 2.15 s (#2) | Yes (About 5,000 pageviews a month) | Partial (Older library only) |
| 8. Usercentrics | 672 ms (#8) | 4.16 s (#7) | Yes (1,000 sessions a month) | No (Commercial licence) |
| 9. Ketch | 1.68 s (#9) | 7.95 s (#9) | Yes (5,000 users) | Partial (SDKs and samples only) |
How CookieBench ranks them
1. Speed on the same Next.js page
CookieBench loads each consent manager 15 times on the same Next.js test page, on each device profile. The list order is the median time until the banner is on screen, on desktop.
2. Speed on mobile
Each entry also gives its time on emulated mobile, which has a slower CPU and a slower network. The order on mobile can be different.
3. Facts from vendor pages
The free plan, IAB TCF, Google certification and licence come from the public pages of each vendor. The feature matrix links each fact to its source.
4. The same rules for c15t
Inth builds c15t and maintains CookieBench. c15t gets the same test page, the same number of visits and the same rules as every other consent manager.
All 9 CookieYes alternatives, in order
The list is in desktop order. Each entry also gives its mobile time and place.
1. c15t
Open-source consent manager with framework SDKs and a self-hostable backend.
- 27 ms (#1)
- 240 ms (#1)
- First-party SDK
- Yes (Open source; hosted free plan)
- Yes
- No (Not on Google’s list)
- Yes (Apache-2.0)
2. Cookie Control
Script-based cookie consent tool from Civic UK.
- 385 ms (#2)
- 2.47 s (#3)
- Script tag
- Yes (Community edition)
- Yes (TCF v2.3)
- Yes
- No (Proprietary)
3. iubenda
Compliance suite covering cookie consent, policies and terms.
- 431 ms (#3)
- 2.66 s (#4)
- Script tag
- Yes (Under 5,000 pageviews a month)
- Yes (TCF v2.2)
- Yes
- No (Hosted embed only)
4. Didomi
Consent and preference management platform with a hosted web SDK.
- 466 ms (#4)
- 4.41 s (#8)
- Script tag
- No (Contact sales)
- Yes (TCF v2.2)
- Yes
- No (Proprietary)
- 477 ms (#5)
- 2.75 s (#5)
- Script tag
- Yes (5,000 visitors a month)
- Yes (Growth plan and up)
- Yes
- No (Hosted embed only)
6. OneTrust
Enterprise privacy suite with a hosted cookie consent module.
- 629 ms (#6)
- 3.92 s (#6)
- Script tag
- No (Quote-based pricing)
- Yes (TCF v2.2 and v2.3)
- Yes
- No (Proprietary)
- 644 ms (#7)
- 2.15 s (#2)
- Script tag
- Yes (About 5,000 pageviews a month)
- Yes (TCF v2)
- Yes
- Partial (Older library only)
- 672 ms (#8)
- 4.16 s (#7)
- Script tag
- Yes (1,000 sessions a month)
- Yes (Pro plan and up)
- Yes
- No (Commercial licence)
- 1.68 s (#9)
- 7.95 s (#9)
- Script tag
- Yes (5,000 users)
- Yes (TCF v2.2)
- Yes
- Partial (SDKs and samples only)
Why does banner speed matter?
1. Your tags wait for the banner
In the EU and the UK, analytics, ad and marketing tags that use cookies must wait for consent. A late banner makes all of those tags late.
2. You lose data on visitors who leave first
Some visitors leave before your banner is on screen. They never consent, so you do not get full data on their visit. Your reports then undercount the traffic from your ads.
3. Your ad platforms get less data
Ad platforms use conversion data to set bids and to find buyers. When fewer visitors consent in time, the platforms get less data. Each conversion can then cost more.
4. A/B tests and personalisation start late
A/B test and personalisation tools that need consent also wait for the banner. Until the visitor chooses, the visitor sees your default page.
5. A late banner interrupts your visitors
A visitor starts to read, or moves to click. Then the banner appears over your content. A click for your page can land on the banner.
6. Interruptions can make visitors leave
A visitor from an ad or a search result decides fast to stay or to go. A banner that appears late gives that visitor one more reason to go. Your bounce rate can go up.
CookieBench tests ten consent managers. Cookiebot is not one of them yet. Suggest a consent manager
Other rankings
inth, the team behind c15t, maintains CookieBench. We hold c15t to the same rules as every other consent manager. Who maintains CookieBench?
On Next.js, c15t shows its banner first of the nine CookieYes alternatives that CookieBench tests: 27 ms on desktop and 240 ms on mobile.
Yes. Seven of the nine alternatives have a free plan: c15t (Open source; hosted free plan), Cookie Control (Community edition), iubenda (Under 5,000 pageviews a month), Enzuzo (5,000 visitors a month), Osano (About 5,000 pageviews a month), Usercentrics (1,000 sessions a month) and Ketch (5,000 users). Check the pricing page of each vendor for the full terms.
Yes. One of the nine alternatives is open source: c15t (Apache-2.0). Osano (Older library only) and Ketch (SDKs and samples only) are open source in part.
By speed. CookieBench loads each consent manager 15 times on the same Next.js test page, on each device profile. The list order is the median time until the banner is on screen, on desktop.
A late banner delays every tag that needs consent, such as analytics, ads and A/B tests. It also appears over content that visitors started to read. Some of those visitors leave.
Inth maintains CookieBench and builds c15t. c15t gets the same test page, the same number of visits and the same rules as every other consent manager. The method, the source code and the data are public.
On 12 October 2026, with run matrix-2026-10-12. The list changes when CookieBench publishes new results.