What are render-blocking resources?
A browser needs content and its required presentation information before it can paint a usable page. A stylesheet can hold that paint while the browser downloads and processes its rules. The browser can continue discovering work during that wait.
“Render-blocking” is often used loosely for anything delaying visible content. For diagnosis, distinguish a paint dependency from an HTML parsing pause, a slow server response and a later font swap. The critical rendering path explanation separates these mechanisms.
Which user experience is delayed?
Waiting for an essential resource can postpone visible content, including the largest content element. That makes render-blocking a useful performance investigation, but not a measured ranking penalty or a fixed number of lost seconds.
Google’s Core Web Vitals documentation identifies LCP, INP and CLS. First Contentful Paint is a different diagnostic metric, not a fourth Core Web Vital. Google uses Core Web Vitals in its ranking systems, but good page-experience measurements do not guarantee top rankings.
Painting and parsing are different
The browser builds a document structure from HTML, combines it with style information, calculates layout and paints. CSS can delay painting without itself stopping the HTML parser. A classic synchronous script pauses parsing because executing it can change the document.
If that script sits before the page’s main content, the parser cannot yet reach that content. It can therefore delay the initial paint as a consequence. This does not make parser-blocking and explicit render-blocking identical browser features.
MDN’s script element documentation describes the explicit blocking="render" attribute separately. Only scripts in the head can use that attribute to block rendering; it is not the default classification of every script.
Selected loading behaviors
| Resource | Behavior | Important qualification |
|---|---|---|
| Applicable head stylesheet | Can hold initial painting until styles are ready. | A nonmatching media condition differs; inspect the actual link. |
| Classic script without async or defer | Pauses HTML parsing for execution. | Placement determines which content has been parsed. |
| Deferred external classic script | Downloads alongside parsing and executes after parsing. | Execution still takes work and delays DOMContentLoaded. |
| Asynchronous external classic script | Downloads alongside parsing and executes when available. | Execution can interrupt other work; dependency order is not guaranteed. |
The table is a qualitative comparison, not a timing test. MDN documents stylesheet media and blocking attributes and the script rules above. Module scripts defer by default; adding defer to an inline classic script does not provide these external-script semantics.
An illustrative script change
Suppose a standalone interface script needs the parsed document, and no earlier inline code depends on it running immediately. Deferral may fit that dependency. The following is illustrative syntax, not a live file on this site or a measured improvement:
<script src="/assets/interface.js" defer></script>
Test the actual interface after changing the loading order. If another script expects this one to have already run, simply adding an attribute can break behavior. Do not change every script to async: independent execution is different from ordered deferred execution.
TTFB, fonts and lazy loading
Time to First Byte measures the interval until the navigation’s first response byte. A stylesheet request discovered after that response can delay paint; its duration is not automatically an addition to that navigation’s TTFB. Keep server-response and browser-rendering evidence separate.
Font loading has another effect: text may initially be hidden or shown with a fallback. MDN’s font-display documentation explains those display periods. swap uses a short block period and then fallback text while the font loads; it does not guarantee identical layout or zero delay.
Lazy loading concerns when a resource is requested. Deferring a nonessential resource and delaying the page’s primary content have different consequences. Decide what the visitor needs to see first rather than using one loading rule for everything.
Investigate a specific dependency
- Identify the content whose appearance is delayed.
- Inspect the requests and execution before that content can paint.
- Check which styles or scripts it actually needs.
- Make one controlled loading or resource change.
- Retest visible content, layout and functional interaction.
Chrome’s render-blocking insight recommends reducing unnecessary first-paint dependencies. It treats critical CSS inlining as an advanced option that can introduce bugs, not a requirement for every site. Removing unused rules can be more appropriate than maintaining a separate inline stylesheet.
Do not add request durations into a fake result
Downloads can overlap, and execution, discovery and resource dependencies affect the sequence. Adding each file’s duration does not establish a visitor’s total delay. An audit’s estimated savings are a hypothesis to test, not a measured business outcome.
Moving necessary CSS later can create an unstyled initial view or layout changes. Keep the styles required for a usable first view available, and investigate nonessential dependencies selectively. A page that paints sooner but becomes unreadable has not completed the reader’s task.
Additional questions
Should every stylesheet be inlined?
No. Critical CSS inlining can reduce a request dependency, but it adds extraction and maintenance work and can introduce bugs. Chrome’s guidance says many sites can reach recommended performance targets without it. Decide from the actual dependency and retest the resulting page.
Does async mean a script cannot delay the page?
No. Async changes fetching and execution timing. The script still executes when available and can interrupt other work. Use it when the script can run independently, and check its actual effect rather than assuming the attribute makes execution free.
Related glossary terms
- JavaScript SEO: distinguish content access from paint timing.
- Server-side rendering: understand where the initial HTML is produced.
- Core Web Vitals: distinguish loading, interaction and stability measurements.
Sources and editorial note
Primary references are linked beside the explanations and were checked on October 12, 2026. AI assisted this revision. Examples are illustrative; no private search property, customer result, browser performance experiment or named human approval is claimed.