The short answer
A good cookie consent banner holds analytics and ad tags until the visitor agrees, puts Reject next to Accept with the same look, lets people into the site without saying yes, and leaves a way back so people can change their mind. On 26 October we tested 92 banners on European sites: 36 of 81 left no way back that we could find after a choice, 47 of 90 covered at least half of a phone screen, and 34 sent data to trackers before anyone clicked.
What a cookie consent banner is for
A cookie consent banner asks visitors whether your site may use cookies and tags that aren't needed to run it, such as analytics and advertising. Its real job happens out of sight: until the visitor says yes, those tags should wait.
What a good banner does
Most of this comes from EU law and its regulators, where the rules are strictest. The point about hidden links comes from the W3C's accessibility standard.
| A good banner | Why | Source |
|---|---|---|
| Holds analytics and ad tags until the visitor says yes | Consent has to come before the cookie or tag, not after | ePrivacy Directive, Art. 5(3) |
| Puts Reject on the first screen, as easy to press as Accept | Most EU regulators treat a banner with no Reject at any level as an infringement, and judge a Reject styled to be missed case by case. Offering it on the first screen is the simple fix | EDPB cookie banner taskforce, paras. 6 to 18 |
| Lets people into the site without saying yes | A site you can't enter until you press Accept isn't a free choice | EDPB Guidelines 05/2020, paras. 39 to 41 |
| Doesn't hide what the visitor is trying to use | A sticky banner that completely hides the link or field someone has tabbed to fails WCAG 2.2 | W3C, Success Criterion 2.4.11 |
| Leaves a way back after the choice | Withdrawing has to be as easy as agreeing, at any time | GDPR Art. 7(3). EDPB Guidelines 05/2020, paras. 113 and 114. EDPB taskforce, paras. 31 to 35 |
The GDPR cookie banner guide goes through the legal side of each row. This piece measures how banners behave.
What we found on 92 banners
On 26 October 2026 we drew 220 random sites from the Tranco list of popular domains (ranks 20,000 to 300,000, on EU country domains and .co.uk) and loaded each in a fresh browser set to the country's language, from a US connection.
183 loaded, and 92 showed us a banner with an Accept button. None were in our 14 October GDPR test.
We measured each banner at desktop size and at phone size (390 by 844). Then we pressed Reject (or Accept, where there was no Reject) and reloaded.
Next we looked for a way back: a floating button, a footer link, or a link on the site's cookie or privacy page. A candidate only counted if clicking it brought the choices back up.
| What we measured | Banners |
|---|---|
| Showed a banner to our visit | 92 |
| Reject (or "only necessary") on the first screen | 51 |
| No free Reject on the first screen | 41, two of them "accept or pay" |
| Sent data to a tracker, or set a tracking cookie, before any click | 34 |
| On a phone, covered half the screen or more | 47 of 90 |
| On a phone, blocked the page (a layer over it, or scrolling switched off) until a choice | 38 of 90 |
| Left a way back after the choice | 45 of 81 |
| ...from a floating button | 13 |
| ...from a link on the homepage, nearly always in the footer | 24 |
| ...only from the cookie or privacy page | 8 |
| Still sent tracking data after Reject and a reload | 13 of 40 |
The gap that surprised us was the way back. On 36 of the 81 sites where the banner went away after a choice, our check found no way to bring it back, on the homepage or on the first cookie or privacy page we followed. One privacy policy told visitors to withdraw by contacting the company.
A site may treat a US visitor differently from a European one, so the "before any click" count may overstate what a visitor in Europe gets.
Cookie banner design: layouts and buttons
Two choices do most of the work: where the banner sits and how its buttons look.
Layout
Most banners fall into four layouts. Here is what each cost a visitor in our test, with the median share of a phone screen it covered.
| Layout | Banners | Median phone cover | Free Reject on first screen | What it's like |
|---|---|---|---|---|
| A bar along the bottom or top | 24 | 36% | 16 | The site stays usable and the choice waits. The best fit for most sites |
| A box in a corner | 21 | 41% | 14 | Small on desktop. On a phone it becomes a bottom panel, often a big one |
| A box in the centre, with the page still usable | 9 | 86% | 5 | Hard to miss, and on a phone it fills most of the screen |
| A box over a layer that blocks the page | 38 | 59% | 16 | The visitor can't do anything until they choose. With a real Reject next to Accept, they still have a choice. Without one, it's a cookie wall |
A bar was the gentlest on phones. The GOV.UK Design System goes further: its banner sits at the top of the page, scrolls away with it, and isn't "sticky", so it can't hide a link someone is trying to reach.
What matters to regulators is access, not the layer itself. The European Data Protection Board's line: if the only way into the site is "Accept cookies", the visitor has no genuine choice.
Buttons: does it matter how Reject looks?
Someone on r/gdpr asked this about Amazon's banner: Accept stands out and Decline is quieter, so does the look matter, or only that both options are there?
The look matters, but there's no fixed rule. The EDPB's cookie banner taskforce agreed that no general standard for colour or contrast can be imposed, and that each banner is judged case by case on whether its colours are "obviously misleading". It named one clear case: a refuse button whose text is so faint it's "unreadable to virtually any user".
A Reject link sunk into the banner's text, with nothing to draw the eye, doesn't give valid consent either.
In our test we could read the style of both buttons on 43 banners. 12 gave Reject the same colour and size as Accept. On 19, Accept was the coloured button and Reject was white, light grey, an outline or plain text.
The easy answer is to give Reject all and Accept all the same style, so contrast never comes up. The GDPR cookie banner guide has the legal side.
The way back in
Withdrawing consent has to be as easy as giving it. Agreeing took one click, so changing your mind should be about that easy too.
The EDPB's cookie banner taskforce suggests two ways: "an icon (small hovering and permanently visible icon) or a link placed on a visible and standardized place". It stops short of requiring an icon, and each case is judged on whether withdrawing is as easy as agreeing.
In our test, the sites that got this right mostly used a footer link with a plain name ("Cookie settings", "Gérer mes cookies", "Cookie-Einstellungen"), or a small floating button in a corner. Both work. A link buried in a privacy policy works for the few who find it.
Check your own banner in five minutes
- Open your site in a private window on your phone, from a country where your banner shows. How much of the screen does it cover? Can you still read the page?
- Is "Reject all" on the first screen, and is it the same kind of button as "Accept all", in the same colour and size?
- Open developer tools on a computer (F12) › Network, reload, and look for requests to Google, Meta or TikTok before you click anything. How to check website cookies covers what a cookie list alone misses.
- Press Reject, reload, and check again.
- Now try to change your mind. Can you get back to the choices from the homepage in one click?
For the Google side of the check, how to check Consent Mode v2 is working shows what the gcs value in each request means. If your visitors are mostly in the US, do you need a cookie banner in the US? covers the opt-out rules there, and our accessibility checklist covers keyboards and screen readers.
Where TagSentry fits
TagSentry's banner comes in six looks, with colours and fonts taken from your site, on every plan. In every look, Reject all and Accept all sit side by side on the first screen as the same button, and nothing optional is pre-ticked.
Before any tag runs, it tells Google's tags that consent is denied, through Google Consent Mode (the signals Google's tags read to decide whether they may use cookies). On the first screen the visitor picks: Escape leaves the banner where it is, and the X, where the site shows one, counts as Reject all.
Visitors reopen their choices from our small button, or from a link in your footer if you pick "A link in my footer". Either one opens a short dialog with both choices at equal weight and the purposes one press away.
Each place gets the rules its law asks for: an ask-first banner in the EU and UK, and no banner by default in US states, where people opt out instead and the browser's privacy signal (Global Privacy Control) counts as an opt-out of advertising.
You can change the words and position per place and switch on any of 32 languages. How consent works shows the rules by country. Consent is free up to 10,000 page views a month.
Sources
- EDPB: Report of the work undertaken by the Cookie Banner Taskforce (17 January 2023)
- EDPB: Guidelines 05/2020 on consent under Regulation 2016/679
- EUR-Lex: General Data Protection Regulation (EU) 2016/679
- EUR-Lex: ePrivacy Directive 2002/58/EC, consolidated text as amended in 2009
- GOV.UK Design System: Cookie banner
- W3C: Understanding Success Criterion 2.4.11, Focus Not Obscured (Minimum)
- Tranco: a research-oriented top sites ranking
- r/gdpr: How are cookie banners like Amazon's GDPR compliant?