performance-budget
Measure what an AEM Edge Delivery Services page requests before its Largest Contentful Paint element is ready, and compare it with the 100 KB budget. Produces a byte table per request from a Lighthouse run, names the requests that are in the wrong loading phase (eager, lazy, delayed), and sets up a GitHub Action that fails a pull request over the budget. Use when the user asks for a performance budget, a byte breakdown of the critical path, what is using up the LCP budget, or a budget check in CI. To diagnose LCP, CLS or INP in general, use cwv-optimizer.
- Version
- 1.0.0
- License
- Apache-2.0
Pinned to revision ae83a5beb6a7, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/performance-budget/SKILL.md
- skills/performance-budget/CHANGELOG.md
- skills/performance-budget/assets/performance-budget.yml
- skills/performance-budget/package.json
- skills/performance-budget/references/performance-budget-rules.md
- skills/performance-budget/scripts/bytes-before-lcp.jq
Every link opens the file at its source, pinned to the revision this page describes.