Tracker Performance Audit
Audit every third-party script on your site for privacy risk, page weight, blocking time, and consent requirements.
How to Use Tracker Performance Audit
- 1Enter your website URL to scan.
- 2Review the list of detected third-party scripts.
- 3Check each script's privacy risk score, size, and blocking time.
- 4Follow the per-script recommendations (keep, optimize, replace, or remove).
ZenovayAnalytics
See who's on your site right now.
- Real-time visitor tracking
- Privacy-first, no cookie banner
- Set up in two minutes
Related Tools
GA4 Health Checker
Audit your Google Analytics 4 setup for duplicate tracking, consent mode issues, deprecated UA scripts, and data layer problems.Analytics Advisor
Compare 14+ analytics platforms on pricing, privacy compliance, features, and GDPR readiness. Find the right tool for your needs.Privacy Policy Auditor
Detect third-party scripts on your site and check if each one is properly disclosed in your privacy policy. Get a compliance score.Privacy Law Checker
Analyze your website to determine which privacy laws (GDPR, CCPA, LGPD, PIPEDA, APPI) apply based on audience signals.Frequently Asked Questions
How are privacy risk scores calculated?▾
Each script is rated 1-5 based on the type and amount of data it collects, whether it shares data with third parties, its data jurisdiction, and whether it uses cookies or fingerprinting. A score of 5 means extensive cross-site tracking and data sharing.
How accurate are the KB and ms estimates?▾
The estimates are based on typical script sizes and blocking times measured across many sites. Actual values vary depending on configuration, caching, and network conditions. They provide a directional guide for optimization priorities.
What does each recommendation mean?▾
Keep: script is acceptable. Optimize: reduce impact through lazy loading or configuration. Replace: switch to a lighter or more privacy-friendly alternative. Remove: script has high risk with limited value -- consider removing it entirely.
How are the grades calculated?▾
Privacy grade is based on average risk score across all detected scripts (A=best, F=worst). Performance grade is based on total script weight in KB. Both use standard grading thresholds.
Why does consent matter for performance?▾
Scripts requiring consent cannot load until the user accepts cookies. This creates two problems: users who reject get no tracking (data loss), and users who accept experience delayed script loading (performance hit).
What are good alternatives for high-risk scripts?▾
For analytics, use Plausible or Zenovay (no cookies, GDPR-compliant). For session recording, Microsoft Clarity is free and lightweight. For advertising pixels, use server-side conversion APIs to reduce client-side impact.