Several scripts block the page from rendering
The document head loads three or more external scripts with neither async nor defer, so the browser must stop, download, and run each one before it can show anything — directly delaying first paint.
Why it matters
The document head loads three or more external scripts with neither async nor defer, so the browser must stop, download, and run each one before it can show anything — directly delaying first paint. Add the defer attribute to scripts that build the page (they still run in order, but after parsing) and async to independent third-party scripts, or move non-critical scripts to the end of the body. (Count in the evidence.)
How ShipReady detects it
Markup hygiene read straight from the fetched HTML — no extra requests. Page-scoped because images and scripts differ between routes.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.0.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
Your document head loads three or more external scripts with neither async nor defer, so the browser stops parsing to download and run each one before it can paint anything. For scripts that build the page, add the defer attribute (they still execute in order, but after the HTML is parsed). For independent third-party scripts (analytics, chat, tag managers), add async. Anything not needed for the initial view is better moved to the end of the <body> or loaded on interaction. Re-check that the head no longer contains a synchronous <script src> without async or defer.
Frequently asked questions
- What does "Several scripts block the page from rendering" mean?
- The document head loads three or more external scripts with neither async nor defer, so the browser must stop, download, and run each one before it can show anything — directly delaying first paint.
- How serious is it?
- ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.
Related checks
- Images have no width and heightlow
- A JavaScript bundle is large enough to make the page feel slowmedium
- An image is large enough to be slowing the page downmedium
- Real visitors wait too long to see your main contentmedium
- The page is served without compressionmedium
- The page is slow to respond when people tap or clickmedium
Run this check on your site
ShipReady checks this and 193 other things across up to ten pages of your site, with an AI-ready fix for each. Free, no signup.