# Web Quality Audit

Run an evidence-led web quality audit covering performance, accessibility, SEO, best...

- Repository: https://github.com/addyosmani/web-quality-skills (3022 stars)
- Category: Design
- License: MIT
- Last updated: 2026-08-24
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add addyosmani/web-quality-skills --skill web-quality-audit -g -a claude-code -y`
Codex: `npx skills add addyosmani/web-quality-skills --skill web-quality-audit -g -a codex -y`
Cursor: `npx skills add addyosmani/web-quality-skills --skill web-quality-audit -g -a cursor -y`
Gemini CLI: `npx skills add addyosmani/web-quality-skills --skill web-quality-audit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add addyosmani/web-quality-skills`

## Description

Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Web quality audit

Comprehensive quality review that combines live browser evidence with source inspection. Covers Performance, Accessibility, SEO, Best Practices, and Agentic Browsing without treating an aggregate score as proof of quality.

> **Lighthouse 13+.** The Performance category now uses shared **Performance Insights** across Lighthouse and the DevTools Performance panel ([announcement](https://developer.chrome.com/blog/moving-lighthouse-to-insights)). Follow current insight names and evidence. Do not require removed audit IDs or automatically recreate their recommendations; some were retired because they were noisy, inactionable, or easy to over-recommend.

## How it works

1. Establish the audit target: representative URLs, important states and journeys, public versus authenticated access, and mobile/desktop scope.
2. If a page can run, read [the measurement workflow](../performance/references/MEASUREMENT.md) and collect a minimal live baseline before searching the codebase broadly.
3. Use runtime failures to localize source inspection. Keep measured findings separate from hypotheses found only in code.
4. Categorize by user impact and confidence, then make or recommend specific fixes.
5. Re-run equivalent automated checks and the affected manual flows. Report what is verified and what still needs field or human validation.

## Tool routing

Use the best capability already available; do not block the audit on optional setup.

The rest: https://github.com/addyosmani/web-quality-skills/blob/HEAD/skills/web-quality-audit/SKILL.md