A consent banner has to behave correctly across several distinct visitor states — before any choice is made, after accepting, after declining, on a return visit — and it’s entirely possible for the banner to display perfectly while still failing at its actual job, such as continuing to load tracking scripts for a visitor who explicitly declined them, which is a compliance problem invisible from simply looking at the banner itself. This particular kind of failure is especially easy to miss because it produces no visible symptom at all for you as the site owner — the banner displays, dismisses, and behaves exactly as designed from a purely visual standpoint, while the actual script-blocking obligation underneath quietly fails to hold. That gap matters more than it might first seem, since a site owner who has never actually opened their browser’s network tools while clicking through the banner has no reliable way of knowing whether the scripts are really being blocked, right up until a privacy-conscious visitor checks for themselves or a regulator’s scanner flags it.
Why we test scripts, not just the banner’s appearance
A consent banner can dismiss smoothly and look entirely correct while doing nothing to actually stop the tracking scripts it’s meant to block — that gap only becomes visible by watching what scripts genuinely load in each consent state, not by watching the banner itself.
If you already know which specific scripts or tracking tools concern you most, mentioning them lets us prioritise confirming those directly.
It’s also worth thinking about whether your site has added any new marketing or analytics tool recently, since a newly added script is one of the most common ways a previously-working consent setup quietly stops covering everything it should.
Consent banner behaviour testing
Real visitor scenarios tested against your cookie consent banner — before consent, after accepting, after declining — to confirm it behaves correctly.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| You want consent behaviour tested across accept, decline, and return-visit states | This fix covers it |
| You already know a specific script loads regardless of consent and want it fixed | A more targeted repair, not this broader test |
| A cookie banner is visually blocking content rather than a behaviour concern | Cookie banner blocking content – fix, a different service |
| You want general cross-browser rendering tested, not consent behaviour | Cross-browser rendering audit & fix list, a different service |
| You need a full legal compliance review, not a technical behaviour test | Worth discussing with legal counsel; we test the technical behaviour specifically |
What we need from you
- Which consent or cookie management plugin, if any, is currently in use
- Any specific third-party scripts or tracking tools you’re particularly concerned about
- Whether you want issues fixed as found, or a full report before any changes
What we do
- Test the banner’s display and dismissal across the states a visitor can be in
- Check which scripts actually load in each consent state using browser network tools
- Confirm scripts categorised as non-essential are genuinely blocked before consent
- Test that a returning visitor’s previous choice is correctly remembered and honoured
- Document any discrepancy found, with the specific script and consent state involved
- Correct a mistagged script or a stale consent-plugin rule directly where it’s safe, and flag anything that would change what counts as essential for your own decision
What is included
- Testing of consent behaviour across accept, decline, and return-visit states
- Verification of which scripts actually load in each state, not just banner display
- Straightforward, low-risk issues fixed directly
- A written report covering findings, fixes made, and anything needing a decision
Not included
- Legal advice on what your specific compliance obligations actually require
- Drafting or rewriting your cookie policy or privacy notice text
- Fixing a third-party consent plugin’s own underlying bugs beyond a safe correction
- Ongoing testing as you add new tracking scripts in future
Questions about this fix
Can you tell me if my consent banner is legally compliant?
We test the technical behaviour thoroughly, but whether that meets your specific legal obligations is a legal question best confirmed with counsel familiar with your jurisdiction.
What if scripts are loading before consent even though the banner says otherwise?
That's precisely the kind of discrepancy this test is built to catch, since it's genuinely common for a banner's stated behaviour and its actual script-blocking to quietly drift apart.
Does this cover Google Analytics and advertising pixels specifically?
Yes, those are exactly the kind of non-essential scripts we check are properly gated behind consent, alongside any others you use.
Will this slow down my site by adding more scripts?
No — this is a testing service that checks existing behaviour, and any fixes made are aimed at correcting misconfiguration, not adding new tracking infrastructure.
Is this a one-time check, or does consent behaviour need retesting later?
Worth revisiting after adding a new tracking tool or switching consent plugins, since either change can quietly alter what's actually being blocked.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.