What it is
Synchronous scripts in the head stop the browser parsing and painting until they load. Deferring or async-loading non-critical scripts lets the page render sooner. Blocking scripts delay render. Slows paint/LCP. Defer/async non-critical JS. Low-medium. Inferred.
Why does render-blocking synchronous js in head matter for AI search?
Slows paint/LCP.
How do you fix it?
Defer/async non-critical JS.
How do you find it on your site?
- Run Lighthouse and read the render-blocking resources list.
- Find synchronous scripts in the head.
- Add defer or async, or move them, where safe.
- Re-measure first paint.
Which ranking and citation factors does it touch?
Render-blocking head scripts delay paint and LCP. Deferring them is a reliable speed win.
What is the impact?
Low-medium. Inferred.
What is the evidence?
Reduce render-blocking JS. web.dev, Core Web Vitals (Google); Google Search Central, Understanding page experience in Google Search results
Sources
Frequently asked questions about render-blocking synchronous js in head
What does "Render-blocking synchronous JS in head" mean?
Blocking scripts delay render.
How do you fix render-blocking synchronous JS in head?
Defer/async non-critical JS.