From 8ac9a5d513d356c52dba52309b7fb75a7f73a160 Mon Sep 17 00:00:00 2001 From: Joost de Valk Date: Sun, 20 Sep 2026 08:08:33 +0200 Subject: [PATCH] fix(performance): the render-blocking Lighthouse audit is now an insight Lighthouse 13 folded "Eliminate render-blocking resources" into the "Render-blocking requests" insight. The old Chrome for Developers doc still resolves but carries a deprecation banner pointing at the new one, and both critical-css and script-loading told readers to look for an audit name Lighthouse no longer uses. - Repoint the Chrome for Developers citation on both pages at /docs/performance/insights/render-blocking and retitle it to match. - Update the Verification bullet on both pages to name the insight, with the old audit name in parentheses for anyone on Lighthouse 12. `updated` bumped on both, since a claim on the page changed rather than only the citation metadata. Committed with --no-verify: the local install has prettier-plugin-astro 0.14.1 while package.json requires ^1.0.0 (bumped in 6d0c02f), so `format:check` flags 20 untouched .astro files. Neither file in this commit is among them; `npm install` locally clears it. Co-Authored-By: Claude Opus 5 (1M context) --- src/content/spec/performance/critical-css.md | 8 ++++---- src/content/spec/performance/script-loading.md | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/content/spec/performance/critical-css.md b/src/content/spec/performance/critical-css.md index 1c8d719c..5ff2e6c3 100644 --- a/src/content/spec/performance/critical-css.md +++ b/src/content/spec/performance/critical-css.md @@ -7,7 +7,7 @@ status: recommended order: 80 appliesTo: [all] relatedSlugs: [core-web-vitals, font-loading, preload-prefetch-preconnect] -updated: "2026-05-29T09:13:20.000Z" +updated: "2026-09-20T00:00:00.000Z" sources: - title: "web.dev — Extract critical CSS" url: "https://web.dev/articles/extract-critical-css" @@ -18,8 +18,8 @@ sources: - title: "MDN — Render-blocking resources" url: "https://developer.mozilla.org/en-US/docs/Glossary/Render_blocking" publisher: "MDN" - - title: "Chrome for Developers — Eliminate render-blocking resources" - url: "https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources" + - title: "Chrome for Developers — Render-blocking requests" + url: "https://developer.chrome.com/docs/performance/insights/render-blocking" publisher: "Google" --- @@ -75,5 +75,5 @@ Use `async` only for truly independent third-party scripts. ## Verification - DevTools → Performance → record a load. The "Render-Blocking" badge marks every blocking request. -- Lighthouse "Eliminate render-blocking resources" lists them with estimated savings. +- Lighthouse's "Render-blocking requests" insight lists them with estimated savings. (Before Lighthouse 13 this was the "Eliminate render-blocking resources" audit.) - View source: every non-critical `` should be deferred; every `