Overview
The Broken Script Loads section tracks instances where JavaScript files fail to load or execute correctly. Since scripts are critical for functionality, interactivity, and tracking, failures here can significantly impact both user experience and business outcomes.
This section helps you understand the scale, frequency, and impact of script-related issues across your site.
Metrics Explained
1. Broken Script Loads (Total)
This metric represents the total number of failed script load attempts within the selected time period.
Use this when you want to:
Measure the overall volume of script failures
Detect spikes caused by deployments or third-party issues
Identify large-scale outages or misconfigurations
2. Broken Script Loads Rate
This metric shows the percentage of failed script loads out of all script load attempts.
Formula:
Broken Script Loads Rate = (Broken Script Loads / Total Script Loads) × 100
Use this when you want to:
Understand the relative impact of failures
Compare performance across different time periods
Evaluate improvements independent of traffic or script volume
3. Broken Script Loads (Per Day)
This metric shows the average or total number of broken script loads per day over the selected period.
Use this when you want to:
Track consistency of issues over time
Identify recurring daily problems
Smooth out spikes to understand ongoing trends
Common Causes of Broken Script Loads
Incorrect or outdated script URLs
Missing or deleted script files
CDN or hosting failures
Network errors or timeouts
JavaScript execution errors
Blocked scripts (e.g. ad blockers, browser restrictions)
Third-party service outages
CORS or permission issues
How to Use This Section
Monitor trends across all metrics
Look for increases in total, rate, or daily averages to detect issues early.
Compare rate vs total
High total + low rate → likely increased traffic or script usage
High rate → real degradation in script reliability
Use daily metric for pattern detection
Identify whether issues are constant, growing, or tied to specific days/events.
Correlate with releases and third-party dependencies
Script failures often originate from recent changes or external services.
Best Practices
Ensure script URLs are valid and properly versioned
Use reliable hosting/CDN providers
Implement error handling and fallbacks where possible
Minimize reliance on unstable third-party scripts
Monitor critical scripts (e.g. checkout, analytics, core UX) closely