express-milo-performance-diagnosis

express-milo-performance-diagnosis is a cursor rule for Cursor from adobecom/da-express-milo. It costs 466 tokens per session, scanned A, original, Apache-2.0.

A set of rules for finding performance problems in Express-Milo pages, especially pages built with Adobe Experience Manager. It explains how slow loading, hidden page content, and delayed page elements can affect the time users see the main content.

In plain words
What is it for?
Use it to investigate low PageSpeed scores, slow main headings, white screens, or pages that remain hidden while their content is being prepared.
Why use it?
It helps identify whether slow pages are caused by stylesheets, page transformation, or loading order. It guides fixes toward speeding up the page instead of hiding the underlying problem.

Cursor rule for Cursor

Written for Cursor: installed under .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/express-milo-performance-diagnosis
Clone the repo
git clone --depth 1 https://github.com/adobecom/da-express-milo

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for express-milo-performance-diagnosis

README.md
[![agentmods](https://agentmods.dev/badge/rules/adobecom/da-express-milo/express-milo-performance-diagnosis.svg)](https://agentmods.dev/rules/adobecom/da-express-milo/express-milo-performance-diagnosis)
Your own site
<a href="https://agentmods.dev/rules/adobecom/da-express-milo/express-milo-performance-diagnosis"><img src="https://agentmods.dev/badge/rules/adobecom/da-express-milo/express-milo-performance-diagnosis.svg" alt="Measured on agentmods" height="20"></a>
Per session 466 This file is loaded in full into every session.
When invoked 466 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.1 $0.00466 $0.00466
Opus 5 $0.00233 $0.00233
Sonnet 5 $0.00093 $0.00093
Haiku 4.5 $0.00047 $0.00047

Measured 6d ago against content hash 29f2a87d7cf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

express-milo-performance-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 6d 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/express-milo-performance-diagnosis.mdc · 61 lines

What it actually says

Express-Milo Performance Diagnosis

APPLY: PageSpeed < 90 queries

Performance Issue Decision Tree

User: "PageSpeed score 75, H1 LCP 5+ seconds"
├─ LCP > 3s + white screen pattern?
│  └─ YES → CSS render-blocking (27KB styles.css via JavaScript)
├─ Font loading issue?
│  └─ NO → Removing typekit has no impact
└─ SOLUTION → Optimize AEM loading phases for LCP elements

User: "Need to bypass body { display: none; }"
└─ NO → Optimize AEM EDS transformation speed, not bypass

Root Cause: CSS Render-Blocking in scripts.js

// ❌ PROBLEM: 27KB CSS blocks body visibility for 5+ seconds
(function loadStyles() {
  const link = document.createElement('link');
  link.setAttribute('rel', 'stylesheet');
  link.setAttribute('href', path); // BLOCKS until download complete
  document.head.appendChild(link);
}());

AEM EDS Transformation Requirements

Raw HTML → Decorated → Loaded (3 phases, users see NONE until loaded)

  • H1 exists in raw HTML but needs final DOM structure CSS
  • body { display: none; } required until data-block-status="loaded"
  • Focus on accelerating transformation speed for LCP elements

Solution Pattern

// ✅ SOLUTION: Follow hero-marquee pattern for LCP optimization
export default async function init(el) {
  // Phase 1: Create LCP structure immediately (synchronous DOM)
  const basicStructure = createLCPStructure(el);
  el.append(basicStructure);
  
  // Phase 2: Defer heavy operations to Promise.all
  const dataPromises = Promise.all([
    fetchCards(),
    fetchRatings() // Don't block LCP with API calls
  ]);
  
  // Phase 3: Enhance with data after LCP
  const data = await dataPromises;
  enhanceWithData(basicStructure, data);
}

Expected: LCP 5s → 1.5s, PageSpeed 75 → 98

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. 6d ago First seen · 61 lines · 466 tokens per session scan A 29f2a87d7cf4

Subscribe to this mod's changes

express-milo-performance-diagnosis is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 466 tokens to every session, about $0.0023 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.