G23 — Chapter 7 - Technical SEO

Criterion G23 : Critical CSS inline — guide + checklist

PART 1 - Fundamentals Chapter 7 - Technical SEO Keyword : critical css inline

This criterion is subtle… until it blocks SEO performance.

The criterion **G23 — Critical CSS inline** is part of our SEO checklist (335 criteria). Here, you have a **practical** method to check and fix it — with a concrete example.

What exactly this criterion covers

This criterion is subtle… until it blocks SEO performance.

**G23 — Critical CSS inline** (Chapter 7 - Technical SEO): CSS above-the-fold inline in <head>, rest async

Why it matters (SEO + UX)

Why it matters: it is a technical quality factor (crawl, rendering, indexing). When poorly applied, we often observe: ambiguity (wrong associated query), duplication between pages, or loss of performance on impressions.

On high-volume generated sites, this criterion also serves as a **safeguard**: a stable rule prevents 1,000 errors at once.

How to check (step by step)

Approach: tool-assisted test (validator / performance). Recommended tool: **WebPageTest**.

  1. Open the page in Chrome → DevTools → Performance/Network tab.
  2. Run Lighthouse and note the main weakness.
  3. Check if the issue repeats on templates.

Tip: first isolate 10 “representative” URLs (top pages + generated pages) before scaling the fix.

How to fix properly

Strategy: make a “clean” fix (no patch), then measure.

  • Fix the biggest cost source (images, JS, fonts, cache).
  • Retest, then apply to the template (not page by page).
  • Add a safeguard: weight budget (KB) and CI check if possible.

Then: re-crawl 50–200 URLs, then monitor Search Console for 7–14 days (impressions/CTR/indexing).

Concrete example (illustrative)

Example (illustrative):

  • **Context**: training page for aesthetic clinic in Casablanca
  • **Before**: Lighthouse: 46/100 (heavy JS, unoptimized images).
  • **After**: Lighthouse: 80/100 (lazy-load, compression, cache).
  • **Note**: Goal: stabilize LCP.

Checklist to tick

  • [ ] Measure before/after
  • [ ] Respects: fold inline in <head>
  • [ ] Improvement on template
  • [ ] No CWV regression
  • [ ] Cache and compression OK
FAQ

Frequently asked questions — G23

What is the most common mistake on “Critical CSS inline”?

Fixing an isolated page without fixing the template/import: the error returns on the next generation.

Which tool is fastest for large-scale checking?

For this type of criterion, a crawl (e.g. Screaming Frog) + targeted verification in WebPageTest is generally the fastest combo.

How to prevent this from recurring on 10K generated pages?

Freeze an auto-generation rule (title/structure/schema/URLs) + add automatic control (crawl or test) before production import.

Ready to go from theory to action?

Validate this criterion with an audit, then deepen the method in the Academy.

Audit with the tool → Learn in the Academy →