web-quality-audit

Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

7 stars

byRodrigoTomeES

View on GitHub Installation ↓

Best use case

web-quality-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

$curl -o ~/.claude/skills/web-quality-audit/SKILL.md --create-dirs "https://raw.githubusercontent.com/RodrigoTomeES/getmcp/main/.agents/skills/web-quality-audit/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/web-quality-audit/SKILL.md inside 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?

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.

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

web-design-guidelines

from RodrigoTomeES/getmcp

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

vercel-react-best-practices

from RodrigoTomeES/getmcp

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

vercel-composition-patterns

from RodrigoTomeES/getmcp

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

tailwind-design-system

from RodrigoTomeES/getmcp

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

seo

from RodrigoTomeES/getmcp

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

react-doctor

from RodrigoTomeES/getmcp

Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.

performance

from RodrigoTomeES/getmcp

Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".

frontend-design

from RodrigoTomeES/getmcp

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 (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

find-skills

from RodrigoTomeES/getmcp

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

core-web-vitals

from RodrigoTomeES/getmcp

Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".

best-practices

from RodrigoTomeES/getmcp

Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".

agent-browser

from RodrigoTomeES/getmcp

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.