Skip to main contentThe fastest cookie banners (2026)
Tags that need consent, such as analytics, ads and A/B tests, wait until a visitor chooses. A visitor can choose only when your banner is on screen.
Pick your framework. Each page ranks up to 10 consent managers by how fast the banner is on screen.
- October 2026
- 6
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.
The top three on each framework
| Framework | Top three on desktop | Top three on mobile |
|---|---|---|
| Next.js | c15t (27 ms), Cookie Control (385 ms) and CookieYes (387 ms) | c15t (240 ms), Osano (2.15 s) and CookieYes (2.42 s) |
| React | c15t (223 ms), CookieYes (287 ms) and Cookie Control (376 ms) | CookieYes (1.04 s), c15t (1.13 s) and Osano (1.75 s) |
| Nuxt | c15t (17 ms), CookieYes (284 ms) and Cookie Control (397 ms) | c15t (241 ms), CookieYes (1.24 s) and Osano (1.97 s) |
| Astro | c15t (15 ms), CookieYes (282 ms) and Cookie Control (402 ms) | c15t (260 ms), CookieYes (1.07 s) and Osano (1.79 s) |
| TanStack Start | c15t (25 ms), CookieYes (279 ms) and Cookie Control (380 ms) | c15t (261 ms), CookieYes (1.19 s) and Osano (2.00 s) |
| Script tag | c15t (240 ms), CookieYes (284 ms) and Cookie Control (395 ms) | CookieYes (1.08 s), c15t (1.50 s) and Osano (1.76 s) |
inth, the team behind c15t, maintains CookieBench. We hold c15t to the same rules as every other consent manager. Who maintains CookieBench?
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.
It can. Visitors who leave before the banner is on screen do not consent, so your ad platforms get less conversion data. With less data, each conversion can cost more.
It depends on your framework and on the device. On desktop, c15t is first on 6 of 6 frameworks. On mobile, c15t is first on 4 of 6 frameworks and CookieYes on 2.
The top three on desktop are c15t (27 ms), Cookie Control (385 ms) and CookieYes (387 ms). The top three on mobile are c15t (240 ms), Osano (2.15 s) and CookieYes (2.42 s).
The top three on desktop are c15t (223 ms), CookieYes (287 ms) and Cookie Control (376 ms). The top three on mobile are CookieYes (1.04 s), c15t (1.13 s) and Osano (1.75 s).
The top three on desktop are c15t (17 ms), CookieYes (284 ms) and Cookie Control (397 ms). The top three on mobile are c15t (241 ms), CookieYes (1.24 s) and Osano (1.97 s).
The top three on desktop are c15t (15 ms), CookieYes (282 ms) and Cookie Control (402 ms). The top three on mobile are c15t (260 ms), CookieYes (1.07 s) and Osano (1.79 s).
The top three on desktop are c15t (25 ms), CookieYes (279 ms) and Cookie Control (380 ms). The top three on mobile are c15t (261 ms), CookieYes (1.19 s) and Osano (2.00 s).
The top three on desktop are c15t (240 ms), CookieYes (284 ms) and Cookie Control (395 ms). The top three on mobile are CookieYes (1.08 s), c15t (1.50 s) and Osano (1.76 s).