Tracking runs with no consent notice
41.4%
of the 3,044 free scans considered in the last 30 days raised this finding. That is 1,261 scans across 1,254 distinct sites. 95% interval 38.7% to 44.2%.
What it means
Analytics or advertising tags fire before any consent choice exists, and no cookie or consent mechanism was found. Tags that run before consent are a frequently litigated pattern under US state privacy laws and the EU rules, and the exposure is counted per visitor.
How to fix it
Gate marketing and session tags behind a consent choice, disclose them in the privacy policy, and load only the strictly necessary ones before the visitor decides.
How to check it yourself
Open DevTools, go to Network, reload the page before clicking anything, and watch for analytics or ad requests firing before any consent banner appears.
What fixed looks like
Analytics and advertising requests wait in the Network panel until a visitor makes a consent choice.
How we measured this
Go Voltic scans a site and records which findings it raises. The share above is over every free four-page scan in the last 30 days that loaded at least one page, which is 3,044 scans. Deep scans of paid reports and of the research sweep read a site at a different depth and are a separate population, never in this denominator. It is not a survey and it is not an estimate: it is a count of what our own scanner found. Sites are counted once each in the distinct-sites figure, so a site scanned twice does not weigh double there.
The interval is a 95% Wilson interval. A share printed without its sample size reads as certainty and is indistinguishable from a guess, so both are always shown. Figures on this page were computed on 2026-09-08.
The same share sits beside every other finding on the benchmarks page, which also carries the whole table as CSV and JSON and says how to cite it.
Check your own site
The free scan reads four pages and reports every finding it raises, including this one. It takes about ten seconds and asks for nothing but the address.