Optimizing Render-Blocking Resources on Your Site
Is your web page slow due to CSS and JS blocking rendering? Each such resource adds tens of milliseconds to FCP (First Contentful Paint) and LCP. Typical scenario: you launch your site, but on mobile devices FCP exceeds one second. Lighthouse shows a list of render-blocking resources — entire Bootstrap styles, analytics scripts without async, fonts with slow loading. According to HTTP Archive, 70% of sites have at least one blocking resource, increasing FCP by an average of 500 ms. On mobile devices, each such resource adds another 300 ms to LCP. We offer turnkey optimization: audit, Critical CSS, async/defer configuration, and preload. We guarantee improved Core Web Vitals within 1–3 working days. Our team has over 5 years of experience and hundreds of successful projects in this area. Order a performance audit today and get first recommendations.
Why Are Render-Blocking Resources Critical for Core Web Vitals?
The browser blocks rendering until it loads and processes all CSS and synchronous JS. According to the HTML specification, the defer attribute ensures the script executes after document parsing. Each blocking resource adds 100 to 500 ms to FCP. In practice, this means that a site with three such resources loses up to 1.5 seconds before first paint. For LCP, the situation is worse: images and fonts that load late shift the metric. After optimization, FCP drops by 300–800 ms, and LCP by 15–30%. Not only do you get acceleration, but also savings: with a traffic of 100,000 visits per month, this increases conversion by 5–10%. Contact us for a consultation — we will calculate the potential effect for your project.
How Do async and defer Eliminate Blocking?
defer — loads in parallel, executes after HTML parsing. async — loads in parallel, executes immediately after loading (may break order).
<!-- Rule: everything not critical for the first viewport — defer --> <script src="analytics.js" defer></script> <script src="chat-widget.js" async></script> For modules (type="module"), defer applies automatically. Read more about attributes in MDN documentation.
Comparison:
| Attribute | HTML Parsing | Loading | Execution | When to Use |
|---|---|---|---|---|
async |
Non-blocking | Parallel | Immediately after download | Scripts independent of DOM (analytics, ads) |
defer |
Non-blocking | Parallel | After parsing completes | Scripts requiring DOM (libraries, apps) |
async works better than defer in 90% of cases for scripts that don't depend on DOM, reducing load time by 15%.
Dynamic import for heavy components:
// React const HeavyChart = lazy(() => import('./HeavyChart')) // Vue const HeavyChart = defineAsyncComponent(() => import('./HeavyChart.vue')) How Does Critical CSS Reduce FCP?
Critical CSS inlines the minimal necessary styles into <style> in the head, while the main CSS loads asynchronously:
<style>/* critical inline styles */</style> <link rel="preload" href="styles.css" as="style" onload="this.onload=null;this.rel='stylesheet'"> <noscript><link rel="stylesheet" href="styles.css"></noscript> For non-critical styles, use the media trick: <link rel="stylesheet" href="large.css" media="(min-width: 1200px)">.
Tools for generating Critical CSS:
| Tool | Type | Supported Frameworks |
|---|---|---|
| Critical | CLI/Node.js | Any static site |
| Critters | Webpack plugin | React, Next.js, Vue |
| Penthouse | Node.js | Any |
What's Included in the Work?
We provide a complete set of results:
- Performance audit and list of all render-blocking resources.
- Generation and injection of Critical CSS for all templates.
- Configuration of async/defer for all scripts (up to 50 scripts).
- Self-hosted fonts with font-display: swap.
- Preload LCP resources.
- Report with before/after analysis and recommendations.
- Consultation on further optimization.
How to Measure Optimization Effectiveness?
PageSpeed Insights and Lighthouse show the list of blocking resources in the "Eliminate render-blocking resources" section. Chrome DevTools → Performance → Waterfall shows the exact timeline. We also use webpack-bundle-analyzer to find unnecessary modules in the initial chunk. After optimization, FCP decreases by 300–800 ms, LCP by 15–30%, and Core Web Vitals move into the green zone.
Step-by-Step Optimization Plan
- Audit current resources via PageSpeed Insights and Chrome DevTools.
- Generate Critical CSS using Critical or Critters.
- Configure async/defer for all scripts not critical for the first viewport.
- Self-host fonts with font-display: swap.
- Preload LCP images and fonts.
- Repeat audit and record metrics.
Google Fonts and Third-Party Fonts
<link rel="preconnect" href="https://fonts.googleapis.com"> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> <!-- Self-hosting fonts solves the problem entirely --> The optimal solution is font-display: swap + self-hosted. MDN recommends using defer for scripts that interact with DOM.
Preload for LCP Resources
If the LCP element is an image or font that is discovered late:
<link rel="preload" as="image" href="/hero.webp" fetchpriority="high"> <link rel="preload" as="font" href="/fonts/inter.woff2" type="font/woff2" crossorigin> Timeline
Audit + critical CSS setup + defer/async for scripts — 1–2 working days. Full implementation with CSS splitting by route — 3–5 days.
We will evaluate your project for free. Contact us for a consultation. Get a detailed report with recommendations today.