Fail

Trackers load before consent

The short version

Load tracking scripts only after a visitor agrees.

What it means

On a first visit, before anyone clicked anything, the page loaded analytics, advertising, social or tag-manager services from our catalog, or set their tracking cookies. The result lists each service, its category and the domains it was loaded from.

Why it matters

In the EU and UK, the ePrivacy rules and the GDPR generally require consent before setting non-essential cookies or similar tracking, and regulators have fined sites for loading trackers before a choice was made. Beyond the law, visitors who decline expect not to be tracked. We report what happened on one visit; whether it's allowed for your site is a question for your legal adviser.

How to fix it

  1. Configure your consent platform to block the listed services until the matching category is accepted (most platforms have an automatic blocking or prior consent mode).
  2. In a tag manager, fire tracking tags on a consent trigger instead of on page load.
  3. Move hard-coded tracking snippets from your templates into the tag manager or consent platform.
  4. If you use Google's consent mode, start with every storage type denied.
  5. Check that declining keeps them blocked on every later page too.

Check it worked

Run the cookie scan again in a fresh scan (tick fresh if your last scan was in the last 15 minutes). The trackers should no longer appear before consent. These are technical observations, not legal advice.