css-render-blocking-diagnosis

A troubleshooting guide for finding CSS that delays a web page from appearing. CSS is the code that controls a page's visual layout and styling, and render-blocking CSS makes the browser wait before showing content.

In plain words
What is it for?
It is for diagnosing slow first rendering, delayed largest visible content, and poor PageSpeed results caused by CSS loading patterns.
Why use it?
It helps identify why a page may show a blank screen or load slowly even after JavaScript improvements. The guide focuses on loading order, hidden page content, and oversized stylesheets.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/adobecom/da-express-milo/css-render-blocking-diagnosis
Clone the repo
git clone --depth 1 https://github.com/adobecom/da-express-milo

Made for: Cursor.

Per session 1,102 This file is loaded in full into every session.
When invoked 1,102 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01102 $0.01102
Opus 5 $0.00551 $0.00551
Sonnet 5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

Measured 2d ago against content hash d768ad20abec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

css-render-blocking-diagnosis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/css-render-blocking-diagnosis.mdc · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CSS Render-Blocking Diagnosis & Resolution

APPLY: EVERY PERFORMANCE QUERY - PRIMARY DIAGNOSTIC RULE

Critical Learning from 98 PageSpeed Achievement

This rule documents the breakthrough that achieved 98-91 PageSpeed scores by solving CSS render-blocking bottlenecks.

Primary Diagnostic Protocol

Step 1: CSS Blocking Symptom Recognition

IMMEDIATE RED FLAGS requiring CSS investigation:

  • LCP > 3 seconds with white screen pattern
  • Body/content delayed despite JavaScript optimizations
  • Performance scores stuck at 80-85 despite component work
  • Render delay >70% in LCP performance breakdown
  • "Body doesn't show until late" user complaints

Step 2: CSS Loading Sequence Audit

Check these patterns in loading order:

# 1. Confirm body hiding pattern (correct)
grep -r "body.*display.*none" head.html

# 2. Find CSS loading mechanism (potential issue)
grep -r "createElement.*link" scripts.js
grep -r "stylesheet" scripts.js

# 3. Check CSS file sizes (>20KB = likely blocking)
ls -la */styles/styles.css

Step 3: Root Cause Confirmation

Render-blocking CSS anti-pattern:

// ❌ PROBLEM: Large CSS via JavaScript = render blocking
(function loadStyles() {
  const paths = [`${miloLibs}/styles/styles.css`]; // 27KB file
  paths.forEach((path) => {
    const link = document.createElement('link');
    link.setAttribute('rel', 'stylesheet');
    link.setAttribute('href', path); // BLOCKS body visibility
    document.head.appendChild(link);
  });
}());

The Solution Implementation

Phase E: Optimize Block Loading Speed

// ✅ SOLUTION: Focus on LCP element structure creation speed
// Following AEM Three-Phase Loading principles
export default async function init(el) {
  // Phase 1: Create LCP structure synchronously (REQUIRED for performance)
  const lcpContent = createBasicStructure(el);
  el.append(lcpContent);
  
  // Phase 2: CSS loading optimized for AEM transformation phases
  // body { display: none; } stays until data-block-status="loaded"
  
  return lcpContent; // Return immediately for LCP measurement
}

Read the full file on GitHub · 139 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 139 lines · 1,102 tokens per session scan A d768ad20abec

Subscribe to this mod's changes

css-render-blocking-diagnosis is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,102 tokens to every session, about $0.0055 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.