web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once. Orchestrates specialized skills for depth. Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices for focused work.
Best use case
web-quality-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once. Orchestrates specialized skills for depth. Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices for focused work.
Teams using web-quality-audit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/web-quality-audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How web-quality-audit Compares
| Feature / Agent | web-quality-audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once. Orchestrates specialized skills for depth. Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices for focused work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Web quality audit Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks. ## How it works 1. Analyze the provided code/project for quality issues 2. Categorize findings by severity (Critical, High, Medium, Low) 3. Provide specific, actionable recommendations 4. Include code examples for fixes ## Audit categories ### Performance (40% of typical issues) **Core Web Vitals** — Must pass for good page experience: - **LCP (Largest Contentful Paint) < 2.5s.** The largest visible element must render quickly. Optimize images, fonts, and server response time. - **INP (Interaction to Next Paint) < 200ms.** User interactions must feel instant. Reduce JavaScript execution time and break up long tasks. - **CLS (Cumulative Layout Shift) < 0.1.** Content must not jump around. Set explicit dimensions on images, embeds, and ads. **Resource Optimization:** - **Compress images.** Use WebP/AVIF with fallbacks. Serve correctly sized images via `srcset`. - **Minimize JavaScript.** Remove unused code. Use code splitting. Defer non-critical scripts. - **Optimize CSS.** Extract critical CSS. Remove unused styles. Avoid `@import`. - **Efficient fonts.** Use `font-display: swap`. Preload critical fonts. Subset to needed characters. **Loading Strategy:** - **Preconnect to origins.** Add `<link rel="preconnect">` for third-party domains. - **Preload critical assets.** LCP images, fonts, and above-fold CSS. - **Lazy load below-fold content.** Images, iframes, and heavy components. - **Cache effectively.** Long cache TTLs for static assets. Immutable caching for hashed files. ### Accessibility (30% of typical issues) **Perceivable:** - **Text alternatives.** Every `<img>` has meaningful `alt` text. Decorative images use `alt=""`. - **Color contrast.** Minimum 4.5:1 for normal text, 3:1 for large text (WCAG AA). - **Don't rely on color alone.** Use icons, patterns, or text alongside color indicators. - **Captions and transcripts.** Video has captions. Audio has transcripts. **Operable:** - **Keyboard accessible.** All functionality available via keyboard. No keyboard traps. - **Focus visible.** Clear focus indicators on all interactive elements. - **Skip links.** Provide "Skip to main content" for keyboard users. - **Sufficient time.** Users can extend time limits. No auto-advancing content without controls. **Understandable:** - **Page language.** Set `lang` attribute on `<html>`. - **Consistent navigation.** Same navigation structure across pages. - **Error identification.** Form errors clearly described and associated with fields. - **Labels and instructions.** All form inputs have associated labels. **Robust:** - **Valid HTML.** No duplicate IDs. Properly nested elements. - **ARIA used correctly.** Prefer native elements. ARIA roles match behavior. - **Name, role, value.** Interactive elements have accessible names and correct roles. ### SEO (15% of typical issues) **Crawlability:** - **Valid robots.txt.** Doesn't block important resources. - **XML sitemap.** Lists all important pages. Submitted to Search Console. - **Canonical URLs.** Prevent duplicate content issues. - **No noindex on important pages.** Check meta robots and headers. **On-Page SEO:** - **Unique title tags.** 50-60 characters. Primary keyword included. - **Meta descriptions.** 150-160 characters. Compelling and unique. - **Heading hierarchy.** Single `<h1>`. Logical heading structure. - **Descriptive link text.** Not "click here" or "read more". **Technical SEO:** - **Mobile-friendly.** Responsive design. Tap targets ≥ 48px. - **HTTPS.** Secure connection required. - **Fast loading.** Performance directly impacts ranking. - **Structured data.** JSON-LD for rich snippets (Article, Product, FAQ, etc.). ### Best practices (15% of typical issues) **Security:** - **HTTPS everywhere.** No mixed content. HSTS enabled. - **No vulnerable libraries.** Keep dependencies updated. - **CSP headers.** Content Security Policy to prevent XSS. - **No exposed source maps.** In production builds. **Modern Standards:** - **No deprecated APIs.** Replace `document.write`, synchronous XHR, etc. - **Valid doctype.** Use `<!DOCTYPE html>`. - **Charset declared.** `<meta charset="UTF-8">` as first element in `<head>`. - **No browser errors.** Clean console. No CORS issues. **UX Patterns:** - **No intrusive interstitials.** Especially on mobile. - **Clear permission requests.** Only ask when needed, with context. - **No misleading buttons.** Buttons do what they say. ## Severity levels | Level | Description | Action | | ------------ | --------------------------------------------- | ------------------- | | **Critical** | Security vulnerabilities, complete failures | Fix immediately | | **High** | Core Web Vitals failures, major a11y barriers | Fix before launch | | **Medium** | Performance opportunities, SEO improvements | Fix within sprint | | **Low** | Minor optimizations, code quality | Fix when convenient | ## Audit output format When performing an audit, structure findings as: ```markdown ## Audit results ### Critical issues (X found) - **[Category]** Issue description. File: `path/to/file.js:123` - **Impact:** Why this matters - **Fix:** Specific code change or recommendation ### High priority (X found) ... ### Summary - Performance: X issues (Y critical) - Accessibility: X issues (Y critical) - SEO: X issues - Best Practices: X issues ### Recommended priority 1. First fix this because... 2. Then address... 3. Finally optimize... ``` ## Quick checklist ### Before every deploy - [ ] Core Web Vitals passing - [ ] No accessibility errors (axe/Lighthouse) - [ ] No console errors - [ ] HTTPS working - [ ] Meta tags present ### Weekly review - [ ] Check Search Console for issues - [ ] Review Core Web Vitals trends - [ ] Update dependencies - [ ] Test with screen reader ### Monthly deep dive - [ ] Full Lighthouse audit - [ ] Performance profiling - [ ] Accessibility audit with real users - [ ] SEO keyword review ## References For detailed guidelines on specific areas: - [Performance Optimization](../performance/SKILL.md) - [Core Web Vitals](../core-web-vitals/SKILL.md) - [Accessibility](../accessibility/SKILL.md) - [SEO](../seo/SKILL.md) - [Best Practices](../best-practices/SKILL.md)
Related Skills
the-fool
Use when challenging ideas, plans, decisions, or proposals. Invoke to play devil's advocate, run a pre-mortem, red team, stress test assumptions, audit evidence quality, or find blind spots before committing. Do NOT use for building plans, making decisions, or generating solutions — this skill only challenges and critiques.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Use when the user provides Figma URLs or node IDs and asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection. Do NOT use for general Figma data fetching, variable exploration, or MCP troubleshooting (use figma instead).
skill-architect
Expert guide for designing and building high-quality skills from scratch through structured conversation. Use when someone wants to create a new skill, build a skill, design a skill, or asks for help making Agents do something consistently. Also use when someone says "turn this into a skill", "I want to automate this workflow", "how do I teach my Agent to do X", or mentions creating SKILL.md files. Covers standalone skills and MCP-enhanced workflows. Do NOT use for creating subagents (use subagent-creator) or technical design documents (use create-technical-design-doc).
subagent-creator
Guide for creating AI subagents with isolated context for complex multi-step workflows. Use when users want to create a subagent, specialized agent, verifier, debugger, or orchestrator that requires isolated context and deep specialization. Works with any agent that supports subagent delegation. Triggers on "create subagent", "new agent", "specialized assistant", "create verifier". Do NOT use for Cursor-specific subagents (use cursor-subagent-creator instead).
domain-identification-grouping
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
aws-advisor
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
frontend-blueprint
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look better", "frontend", "interface", "redesign", or when the user provides mockups, screenshots, or design references. Do NOT use for backend logic, API design, database schemas, or non-visual code tasks.
cursor-subagent-creator
Creates Cursor-specific AI subagents with isolated context for complex multi-step workflows. Use when creating subagents for Cursor editor specifically, following Cursor's patterns and directories (.cursor/agents/). Triggers on "cursor subagent", "cursor agent". Do NOT use for generic subagent creation outside Cursor (use subagent-creator instead).
decomposition-planning-roadmap
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).
cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare. Do NOT use for deploying to Vercel, Netlify, or Render (use their respective skills).
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys. Do NOT use for deploying to Vercel, Cloudflare, or Render (use their respective skills).
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit).