free · no signup
Universal Analytics checker
Check if your site still loads Universal Analytics (analytics.js or ga.js). UA stopped processing data in July 2023, so the script is dead weight.
Scans the page's HTML in seconds. It also reports every other tracking script it finds.
about Universal Analytics
Why it breaks quietly.
Universal Analytics was Google's analytics before GA4, loaded through analytics.js or the older ga.js and configured with a UA- property ID. Google stopped processing new data in standard UA properties in July 2023.
Plenty of sites still load it. The script downloads, runs and sets cookies on every page view, and none of it goes anywhere you can see. If it is still on your site, it is costing load time and may be the only analytics someone thinks is running.
what the free scan checks
Whether Universal Analytics is in the page
The scan fetches the page's HTML and matches the vendor's script URL and install snippet.
Whether it's dead weight
Universal Analytics stopped processing data in July 2023 — this script does nothing.
Whether it blocks rendering
A script tag without async or defer delays the page from painting. Marketing scripts never need to.
Whether it's installed more than once
Duplicate installs usually send every event twice and inflate conversions.
How exposed the page is to blockers
A server-side readiness grade: whether tags load from domains blocklists target, and whether conversions have a server-side path.
It reads the HTML, so tags injected later (inside GTM, for example) don't show up, and it can't see events fire. That's what verification is for.
common failures
How Universal Analytics goes dark.
The script loads and records nothing
analytics.js and ga.js still download and execute, but Google no longer processes the hits. It is pure page weight.
Nobody migrated the events
Custom UA events and goals were never rebuilt in GA4. The data people relied on stopped in 2023 and the gap only shows when someone asks for a year-over-year report.
A plugin or theme keeps adding it
An old WordPress plugin, theme setting or CMS field still injects the UA snippet even after someone removed it from the template.
A gtag snippet still configured with a UA- ID
Sites that moved to gtag.js but kept a UA- ID in the config call are sending hits to a dead property. This scan reports that snippet as a Google tag, so check the ID by hand.
by hand
Check it yourself, step by step.
- 1
View the page source and search for analytics.js, ga.js, ga('create' and _gaq to find every UA install.
- 2
Search for UA- in the source to find any gtag config calls still pointing at a Universal Analytics property.
- 3
Check plugins, theme settings and tag manager containers for UA tags, then remove them.
- 4
Confirm GA4 is installed with a G- measurement ID and collecting data in the Realtime report.
questions
Asked and answered.
Can this check tell me if Universal Analytics events are firing?+
It can tell you the UA script is in your page's HTML, and it flags it as dead weight. It cannot see UA tags injected at runtime by GTM. Whether hits fire no longer matters, because Google stopped processing standard UA data in July 2023.
Does Universal Analytics still work?+
No. Standard properties stopped processing data in July 2023 and Google has since shut down access to UA properties. Use GA4 instead.
Is it safe to remove the UA script?+
Yes, once GA4 is collecting the data you need. Removing it only removes page weight and dead cookies.
check other tags
Know Universal Analytics is firing, every hour of every day.
Verification watches each tag on real traffic and emails you the moment one goes silent. 14-day trial, no card.