web-quality-audit
$
npx mdskill add tech-leads-club/agent-skills/web-quality-auditComprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.
SKILL.md
.github/skills/web-quality-auditView on GitHub ↗
--- name: web-quality-audit description: 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. license: MIT metadata: author: web-quality-skills version: '1.0' --- # 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)
More from tech-leads-club/agent-skills
- ai-cold-outreachWhen the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
- ai-pricingWhen the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.
- ai-sdrWhen the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.
- ai-seoWhen the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.
- ai-ugc-adsWhen the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.
- aws-advisorExpert 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.
- best-practicesApply 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". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).
- chrome-devtoolsBrowser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser debugging.
- cloudflare-deployDeploy 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).
- codenaviYour pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for greenfield scaffolding, CI/CD, or infrastructure provisioning.