Performance fix guide
Third-Party Scripts Significantly Impact Performance
Third-party scripts (analytics, ads, widgets) contribute significantly to page load time and main thread blocking.
Issue ID: CWV-THIRD-PARTY-001
Severity: moderate
Impact: Med
Effort: M
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Third-party scripts (analytics, ads, widgets) contribute significantly to page load time and main thread blocking.
Why it matters
Third-party scripts (analytics, ads, widgets) contribute significantly to page load time and main thread blocking. This affects load speed, Core Web Vitals, and how many visitors stay long enough to convert.
How we detect it
- FreeSiteAudit flags this issue when the rule for CWV-THIRD-PARTY-001 fails and the page evidence points to Performance tool.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Audit third-party scripts and remove unnecessary ones
- 2Load third-party scripts with async or defer
- 3Use resource hints (preconnect, dns-prefetch) for critical third-party origins
- 4Consider self-hosting critical third-party resources
How to re-check it
- Check Lighthouse third-party summary and confirm reduced impact
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.