Cookie checker — what fires before anyone agrees?
See every cookie and tracker your site sets, and which of them run before the visitor has consented to anything. Free, no signup, thirty seconds.
No signup · No commitment · Result in 30 seconds
Almost every site owner underestimates what their pages load. An embedded video, a map, a chat widget and a font served from someone else’s domain each add requests, and several set cookies without anyone thinking of them as tracking. This checker loads your site in a real browser and reports what actually ran — not what your tag manager says should run.
What the check reports
- Every cookie set on a first visit, with its name, its origin and how long it lives
- Which third-party trackers load — analytics, advertising pixels, session recorders, embedded players and chat widgets
- Crucially: which of them fire before the visitor has agreed to anything
- Whether a consent banner exists at all, and whether it is a real consent platform or a notice that only informs
- Whether refusing is as easy as accepting, which is where most banners fail
The line that matters: before or after
Consent given after a tracker has already fired is worth nothing — the data left before anyone agreed. This is the failure regulators actually sanction, and it is invisible from inside your own admin panel: the banner appears, the message is correct, and analytics loaded two hundred milliseconds earlier.
Which is why the useful question about a consent banner is not what it says but what it prevents. A banner that displays a notice and records a choice, while every script loads regardless, changes nothing about your exposure.
How it works
- Enter your address. The checker loads your site in a real browser and records every request it makes.
- Read what fired: each cookie and tracker is listed, with the ones that ran before consent marked out.
- Fix the blocking first: a banner that only displays a message changes nothing — what matters is what it prevents from loading.
Where this fits
This page answers what your site sets. Its neighbours answer the rest: the privacy policy checker reads the policy you publish and scores what it actually contains, and the full compliance scan combines both with your other legal pages and your company identification into a single score out of 100. If the check finds trackers running too early, our free cookie banner blocks them until consent.
Cookie checker — FAQ
Why does it matter what fires before consent?
Because that is what regulators sanction. Consent obtained after a tracker has already run is worth nothing: the data left before anyone agreed. A banner that appears while Google Analytics is already loading is decoration, not compliance.
I have a cookie banner. Is that enough?
Only if it blocks. Many banners display a message and set consent state without preventing a single script from loading. The check reports what actually ran, which is the only way to tell the two apart from outside.
What counts as a tracker here?
Any third-party request made by your pages: analytics, advertising pixels, session recorders, embedded video, map widgets, chat boxes and fonts served from someone else’s domain. Several of these set cookies without anyone thinking of them as tracking.
Does the check itself set cookies or collect my data?
No. It loads your site the way a visitor would and reports what it observed. No signup, no card, and nothing personal is stored about you.
What do I do about the ones that fire too early?
Block them until consent. Our own cookie banner does this by default and is free to use; any properly configured consent platform will do the same. The point is the blocking, not the banner.