Third-Party Scripts
Checks the count and impact of third-party scripts (analytics, chat, ads).
What this check measures
We count <script> tags loading from non-first-party domains. 5+ third-party scripts on a page cost real performance — each adds to network, parse, and execute time.
Why it matters
Third-party scripts are the #1 performance debt on most sites. Every chat widget, analytics, ad tracker blocks main thread. They also leak data and degrade CSP posture.
How our audit detects it
Parse <script src> tags, group by domain. Count non-first-party origins.
Typical findings
- error_outlineAnalytics + 2 chat widgets + error tracker + 3 ad scripts = 7 third parties.
- error_outlineSame tag manager contains 15 scripts loaded serially.
How to fix
Audit: which third parties are actually used? Remove unused ones. Consolidate (e.g., use one analytics). Load all with async or defer. Consider a tag manager only if you use 5+ scripts.
Frequently asked questions
Can analytics be synchronous?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
LCP (Largest Contentful Paint)
Checks Largest Contentful Paint — how fast the main content appears. Target under 2.5s.
PerformanceCLS (Cumulative Layout Shift)
Checks Cumulative Layout Shift — how much the page jumps during load. Target under 0.1.
PerformanceINP (Interaction to Next Paint)
Checks Interaction to Next Paint — responsiveness to clicks/taps. Target under 200ms.
PerformanceFCP (First Contentful Paint)
Checks First Contentful Paint — when the first text or image appears. Target under 1.8s.