One scan. Four things your shoppers notice.

We visit like a new shopper, click your banner and test your pages. Numbers show how many of 168 European shops had each problem.

Dark patterns

Is saying no as easy as saying yes?

Regulators expect Reject to be as easy as Accept. We compare both choices on the first layer: whether Reject is there, how big and visible it is, and whether boxes are ticked for the shopper. We also flag countdowns that restart for every visitor and “was” prices that weren’t charged in the 30 days before a sale.

No “Reject” on the first layerAccept is a full button. Saying no takes two more clicks behind “Settings”. Example.
Withdrawal and shop rules

Can buyers cancel the way EU law now asks?

Since 19 June 2026, EU online shops need a clear withdrawal function, such as a button labelled “Withdraw from contract here”. We look for it on your pages in 11 languages, and read your privacy policy for the topics it has to cover, in 7 languages.

Shop footer
No withdrawal buttonexampleWe show where it should go and the wording to use. Found missing on 32 of 168 shops.
Accessibility

Can every shopper find, read and buy?

We check up to 500 pages a site against WCAG 2.2 AA, the web accessibility standard. On paid plans we then shop your key pages with only a keyboard, at 200% zoom and at phone width, with an AI review of what screen readers hear. Each issue shows the element, the rule and the fix.

Button has no nameWCAG 4.1.2A screen reader says “button” and nothing else on your cart icon.
<button class="cart"><svg …/></button>
Fix
<button class="cart" aria-label="Open cart"><svg …/></button>
Found on 59 of 162 shops we checked. Every one of the 162 had at least one accessibility issue.

How a scan runs

  1. Arrive as a new shopperNo cookies, no history, nothing ticked.
  2. Watch before any clickEvery request, cookie and pixel, with its timing.
  3. Click Reject, watch againThen reload and check it was remembered.
  4. Accept, then change our mindSaying no later must stop the tracking too.
  5. Shop with a keyboardPlus zoom and phone width, on paid plans. WCAG rules run on every plan.
  • Not tested is never a pass. Checks we couldn’t run are marked “not tested” in the report.
  • We say where we visited from. Banners can change by country, so each scan shows its region.
  • AI findings are labelled. They read “likely” or “check by hand”, never as fact.
  • A record, not a certificate. Reports show what we saw. They aren’t legal advice.

Common questions

How long does a scan take?

About a minute for your homepage. Paid plans test up to 6 key pages in one scan, which takes a few minutes.

Do you touch my visitors’ data?

No. We visit with our own browser, like a new shopper. Nothing is installed on your store and your visitors aren’t involved.

Which platforms does it work with?

Any site with a public address: Shopify, WooCommerce, WordPress, Webflow or a custom build. We test what the browser receives.

Which cookie banners can you read?

Any banner a visitor can click. We recognise the common consent tools and give step-by-step fixes for OneTrust, Cookiebot, Usercentrics, Didomi and CookieYes.

Do you check pages behind a login?

On Pro (3 pages) and Agency (10 pages) the accessibility check can visit logged-in pages like the account area.

What if my store blocks automated visitors?

Some shops use bot protection that stops any scanner. When that happens the scan says so plainly instead of guessing a grade.

See all four on your own store.

Free, no signup, about a minute for your homepage.