Performance fix guide
Excessive Script Count
Too many JavaScript files increase page load time through additional HTTP requests and parse/compile overhead.
Issue ID: PERF-SCRIPTS-001
Severity: medium
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
Too many JavaScript files increase page load time through additional HTTP requests and parse/compile overhead.
Why it matters
Too many JavaScript files increase page load time through additional HTTP requests and parse/compile overhead. 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 PERF-SCRIPTS-001 fails and the page evidence points to Dom body.
- 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 unused ones
- 2Bundle multiple scripts into fewer files
- 3Use defer or async attributes on non-critical scripts
- 4Consider using a tag manager to control script loading
How to re-check it
- Count script tags and confirm fewer than 15
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.