Legal & privacyUsually critical

Does my cookie banner's Reject button work? Check what still loads

A Reject button that doesn't stop anything is worse than no button at all. It tells visitors you asked and then ignored the answer. ShipPatrol clicks Reject, reloads the page and records what still loads.

Why it matters

Consent only counts if refusing it actually works. If trackers fire after someone has said no, you are processing their data without a lawful basis and your banner is misleading them. It also tends to be the screenshot that ends up in a complaint.

How Patch checks

In a fresh browser we find your banner's first-layer Reject (or Decline, or Necessary only) button, click it, reload the page and record every request and cookie. Anything on our list of services that need consent counts as still firing.

How to fix it

  1. Find where the trackers Patch found are loaded. If they are hard-coded in your HTML or a layout component, move them behind your consent tool's "statistics" or "marketing" category.
  2. Make sure the tool reads the saved choice on every page load, not only when the banner is shown.
  3. Test it: open a private window, click Reject, reload, and check that their domains no longer appear in the network tab.

Your own report goes further: it names the exact pages, services and settings Patch found on your site, and with a full report you get a fix prompt to paste into Lovable, Bolt or Cursor.

Where this applies

Applies to visitors in the UK and the EU.

Free scan

Check this on your site.

Patch runs "Trackers still load after the visitor clicks Reject" along with every other check, from the UK, the EU and the US. Free, no signup.

No signup needed. Not legal advice; every check names its source.

All checks