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".
What this skill does
# 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 in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".