What is your page loading behind their back?
Trackers arrive one at a time, each with a good reason, and none of them ever leave.
Nobody has read the list in years
Every tracker on your site was added deliberately by somebody who needed it. The problem is cumulative: five years of good reasons, and no moment at which anyone goes back and asks what is still on the page.
Scripts from people you no longer work with
An agency's pixel, a tool you trialled, an experiment nobody turned off. Each one still runs with full access to your page and still reports to whoever owns it.
The banner that protects nothing
A consent tool that is installed but not set to block anything asks the question, records the answer, and lets everything load before it was shown. That is the common configuration, not the rare one.
You are answerable for all of it
It is your domain and your visitors. If a script you forgot about is collecting identifiers without consent, the liability is not the vendor's.
A page in, its passengers out
Copy the page as it ends up
Developer tools, Elements, right-click the top html line, Copy, Copy outerHTML. Not View Source.
Paste it here
It runs in your browser, so a page that may contain session data goes nowhere.
Read the list
Every third party, grouped by what it is for, and where consent stands.
What it looks for
The whole inventory
Analytics, advertising, session recording, support widgets and testing tools, each named and grouped by what it is there to do.
Which ones identify people
The distinction that decides whether you need consent at all. A site on privacy-first analytics with no banner is doing nothing wrong, and is not nagged here.
Whether anything waits for consent
Whether a consent tool is present, and whether any script is actually marked to be held until it answers. Those are two different things and only one is usually true.
Session recording
It captures mouse movement, clicks and, unless configured otherwise, what people type. On a page with a form, the form contents leave your site.
Tools doing the same job twice
Three analytics scripts will disagree with each other, and the disagreement is what teaches a team to stop trusting all three.
How much of the page is other people's code
Every script is a fetch, a parse and a run before the page settles, and the third-party ones are on someone else's connection.
Straight talk about what it cannot see
It reads the markup you give it. Two of its limits change what you should paste, so they are worth reading before the report.
Paste the page as it ends up
Most sites add trackers with JavaScript after loading, so the served HTML contains none of them. If nothing is found on a busy page, the report says so rather than calling it clean.
It sees what, not when
Whether a tracker actually waited for consent is decided while the page runs. Only your network tab can settle that, and the report says which question it is answering.
It knows the trackers it knows
Anything self-hosted, proxied through your own domain, or from an obscure network is invisible to it. Nothing found is not the same as nothing there.
It is not legal advice
It tells you what your page carries and who it reports to. Whether your particular use needs consent is a question for someone qualified to answer it.
Read the list once a year
It takes five minutes and it is usually the shortest route to a faster page and a smaller problem.