One page, checked the way a first-time visitor from an ad meets it. It's for pages you own or may test. If you want to know whether someone else's shop is safe to buy from, this isn't that tool.
Updated
We open your page in a real browser as a first-time visitor, with no login and no cookies from earlier visits, on a desktop screen and again on a phone-sized one. We read what the page shows and loads: whether the connection is secure, which site builder it seems to run on, whether it has a main heading, a button near the top, a form that asks for an email, a booking tool, a chat, or a phone number in the header, and whether a cookie banner shows. We look for Meta, Google Analytics 4, Google Tag Manager and Google Ads tags on a plain visit and, where there is a cookie banner, after accepting it, so "found" means the tag's code is there, not that it records a lead. Google PageSpeed Insights gives the phone speed. We never submit your form. Anything we couldn't measure says "not measured". This answer is the short version. The free report goes further, and your email unlocks every finding in it.
| Check | How we measure it |
|---|---|
| Certificate and insecure (http) files | One real secure connection, and what the page loaded |
| Site builder, main heading, a button near the top | What the page shows a desktop visitor |
| Form, booking tool, chat, phone number in the header | What the page shows a visitor |
| Meta, Google Analytics 4, Tag Manager and Google Ads tags | Tag code found in the page and its files, on a plain visit and, where there is a cookie banner, after accepting it |
| Cookie banner | What our browser saw on load |
| When the main content shows on a phone | Google PageSpeed Insights, phone lab test |
It's a free check of one page, followed by a free report on what we found, with one fix explained in full. The step-by-step fixes for the rest come with the paid Deep Audit, which is optional.
That the tag's code is in the page or its files. It doesn't prove the tag sends the right events, or that it waits for a visitor's cookie choice: we look on a plain visit and, where there is a cookie banner, after accepting it.
We look at the page itself. If your tracking runs from your server (Meta's Conversions API, for example) or only loads for visitors in some countries, a visit like ours won't see it. Meta Events Manager shows which events reach Meta from this page.
No. We check what a visitor and an ad meet on the page, not rankings or backlinks.
No, we never submit your form. We don't log in or create accounts either, and the ad tracking on your page is stopped inside our browser, so our check isn't counted as a lead in your ad accounts.
Only with their permission. The check is for pages you own or may test, and you confirm that before it runs.
The scan, including a copy of the page's visible text, the addresses it loads and a picture of its first screen on a phone, for up to 18 months, then it is anonymised. The picture is never published; it can appear only inside your report. The privacy page has the details and how to ask us to delete it sooner.
Each tool tests from its own browser, place and phone profile, and many roll everything into one score. We report each measurement on its own and say which ones we couldn't take.