Free tools / Tracking script checker
Tracking script page-speed checker
Paste a URL. This lists every script the page loads and measures the real transfer size of each — not an estimate — and flags the ones that match a known analytics, session-replay, ad-pixel or consent-management vendor.
Scripts loaded on this page
| Vendor | Category | Loaded from | Size |
|---|
Total measured transfer weight of scripts shown above: —. For comparison, UserTapes' own tracker is ~16KB uncompressed (~6KB gzipped) and sets no cookies.
Why this matters beyond privacy
Most tracking-script audits are framed around cookies and consent, which matters, but misses a second cost: every one of these scripts is bytes your visitor downloads and code their browser executes before the page is usable. A page running four or five analytics and support widgets stacked on top of each other can easily add several hundred kilobytes and multiple render-blocking or main-thread-hogging scripts — a real, measurable hit to Core Web Vitals, and one that's invisible until you actually list what's loading.
What "known tracking script" means here
Every script the page loads gets listed, with its real transfer size. Where the hostname matches our curated vendor list — analytics platforms, session-replay tools, ad pixels, chat widgets, A/B testing libraries and consent-management platforms — you get a name and category too. A script we don't recognize still shows up, just without that label, so the result is always what's actually loading, not only the subset we happen to have on file.
What to do with the result
If the list is long, the fix usually isn't "remove analytics" — it's consolidation. A support widget, a heatmap tool, a session-replay tool and a marketing pixel are frequently answering overlapping questions. UserTapes' own tracker is deliberately single-purpose and lightweight — see the cookieless privacy page for how it's built to stay that way, and what it doesn't do that the heavier tools in this category do.
FAQ
What does this tool actually check?
It fetches the page you paste in, reads every <script src="…"> tag it loads, and fetches the real transfer size of each one. Hostnames are also matched against a curated list of known analytics, session-replay, ad-pixel and consent-management vendors — a match gets a name and category, but every script loaded is shown either way.
Is the byte size measured or estimated?
Measured — this tool fetches each matched script and reads its actual Content-Length (or the real bytes transferred if that header's missing), not a guessed average. What's an estimate is the page-speed impact of that weight, which depends on your connection, caching and where in the page the script loads.
Do you only show scripts you recognize?
No — every script the page loads is listed, with its measured size. Scripts matching our curated vendor list (analytics, session-replay, ad pixels, chat, A/B testing, consent management) get a name and category on top of that; everything else still shows up, just without one, since a page loading nothing from our list is still worth seeing in full.
Does this tool store the URLs people check?
No — the scan runs, returns a result, and nothing about the target URL is persisted.