What happens after you click Reject
We drove the cookie banner on 55 real websites and recorded what each site did after Reject, and before any choice. These are the observations, not judgements.
32% of sites we could check kept loading third-party trackers after Reject.
Based on 47 of 55 sites; 8 could not be determined and are not counted.
26% set non-essential cookies before any choice was made.
Based on 47 of 55 sites; 8 could not be determined and are not counted.
- Not observed
- 0%
- Worth a look
- 34%
- Needs attention
- 66%
- Could not determine
- 8 (not counted)
| CMP family | Sites checked | Trackers after Reject | Non-essential cookies before choice | Could not determine |
|---|---|---|---|---|
| OneTrust | 4 | 1 | 1 | 1 |
| Other | 43 | 14 | 11 | 7 |
OneTrust
- Sites checked
- 4
- Trackers after Reject
- 1
- Non-essential cookies before choice
- 1
- Could not determine
- 1
Other
- Sites checked
- 43
- Trackers after Reject
- 14
- Non-essential cookies before choice
- 11
- Could not determine
- 7
Groups under 5 sites are combined into Other. No site is named.
We picked 55 public websites across could not determine and opened each in a real browser with no stored cookies. For each site we recorded three runs: accept, reject, and no choice. "Trackers after Reject" means requests to known tracking domains, or non-essential cookies, observed after the Reject button was used. Where the banner could not be found or driven, the result is "could not determine" and is left out of every percentage. Results show what we observed on the day; sites change. Full method: /methodology. Last updated 12 October 2026.
Curious about your own site? Run the free check.
Your visitors click No.
Find out what your site does next.
Check your site freeOnly check sites you have the right to test.