SH006 – Script Blocking Detection
Overview
Flags render-blocking scripts and inline scripts in head; encourages async/defer and consolidation.
Probability that AI systems use this signal: Crawlers and generative AI pipelines consume structured and visible page signals for training and inference. Assessment-specific signals (e.g. schema, canonicals, trust cues) affect how likely a page is indexed and surfaced. The probability that this assessment's signal influences AI behavior is high when the page is in a product or compliance context.
Impact on geo compliance: Passing this assessment supports geo compliance by ensuring machine-readable and visible content meet standards that reduce the risk of wrong locale, pricing, or trust in AI-generated answers. Failing can lead to non-compliant or misleading surfacing.
What We Check
- All `<script>`. **_analyze_scripts:** with src and (async or defer) → non_blocking; with src and no async/defer → blocking; no src → inline.
- **Blocking scripts:** −30 per. **Inline in head:** count of script in <head> without src; −20 per. **Total scripts > 10:** −15.
Pass / Fail and Score
- **PASSED** if score >= 60.
How to Fix When It Fails
- Use async or defer for non-critical scripts; move inline scripts to external or body; consolidate scripts.
Common Issues
- Scripts in head without async/defer; many inline scripts in head; high script count.
Dependencies
None.
How to Verify
- List script tags; check head for inline and blocking external.
Additional Resources
- Critical rendering path; async/defer