Performance Audit Websites
Use this skill to keep premium sites fast enough that visual ambition does not punish users. Measure first and optimize the dominant constraint; do not apply framework folklore as proof.
Own measured diagnosis and implementation. Route pre-build numeric budgets, acceptance thresholds, and visual-richness policy to $performance-budget-lab.
Workflow
- Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
- Read Performance Audit Websites Guide before claiming the site is ready. For React or Next.js implementation work, also read React and Next.js performance.
- Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
- Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
- Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
Separate field data, controlled lab data, source inspection, and inference. A Lighthouse score from one machine is not a field-performance guarantee; an optimized source pattern is not a measured user improvement.
Scoped execution
Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
1---2name: performance-audit-websites3description: Diagnose measured runtime and Core Web Vitals.4---56# Performance Audit Websites78Use this skill to keep premium sites fast enough that visual ambition does not punish users. Measure first and optimize the dominant constraint; do not apply framework folklore as proof.910Own measured diagnosis and implementation. Route pre-build numeric budgets, acceptance thresholds, and visual-richness policy to `$performance-budget-lab`.1112## Workflow13141. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.152. Read [Performance Audit Websites Guide](references/performance-audit-websites-guide.md) before claiming the site is ready. For React or Next.js implementation work, also read [React and Next.js performance](references/react-next-performance.md).163. Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.174. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.185. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.1920Separate field data, controlled lab data, source inspection, and inference. A Lighthouse score from one machine is not a field-performance guarantee; an optimized source pattern is not a measured user improvement.2122## Scoped execution2324Apply the [shared web contract](../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
