This is one blocker configuration. The scan uses uBlock Origin with default lists, rather than a sample of your actual visitors. Firefox's default protection and Safari's ITP work differently — they mostly restrict the cookies behind a request rather than dropping the request itself, so the session is counted but a returning visitor is misattributed as new. The scan measures outright blocking, which is the more visible failure but not the only one.
It describes one page, at one moment. Tags that fire only at checkout, after a consent choice, or on a different template won't appear. Scanning a landing page and a conversion page usually tells you more than scanning either alone.
A clean result deserves a second look. Nothing blocked is good news only if your tags were there to be blocked. If a page carries no third-party analytics at all, the scan cannot tell you whether its analytics integration is working.
To investigate broader gaps, compare equivalent analytics and server-side metrics over the same period. The scan identifies blocked requests. A log comparison is a diagnostic starting point; account for bots, consent choices, and differences between requests and sessions.
Sources: Backlinko — Ad Blocker Usage Statistics · Brave — Shields · WebKit — Intelligent Tracking Prevention · Mozilla — Enhanced Tracking Protection in Firefox