How is web-quality-audit different from single-area audits?

It covers Performance, Accessibility, SEO, and Best Practices in one pass, using Lighthouse-based checks, and orchestrates specialized skills for depth instead of focusing on a single area.

What does the output include?

A structured report with severity-based findings, prioritized action items, and concrete code examples to implement fixes.

Can this be used in CI/CD pipelines?

Yes. It’s designed to be integrated into QA workflows to provide end-to-end web quality checks and drive automated or semi-automated remediation.

web-quality-audit

npx machina-cli add skill tech-leads-club/agent-skills/web-quality-audit --openclaw

Files (1)

SKILL.md

6.8 KB

Web quality audit

Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.

How it works

Analyze the provided code/project for quality issues
Categorize findings by severity (Critical, High, Medium, Low)
Provide specific, actionable recommendations
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:

## 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

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:

Source

git clone https://github.com/tech-leads-club/agent-skills/blob/main/packages/skills-catalog/skills/(quality)/web-quality-audit/SKILL.md

View on GitHub

Overview

Provides a comprehensive quality review using Google Lighthouse, covering Performance, Accessibility, SEO, and Best Practices across 150+ checks. It’s designed for multi-area audits and orchestrates depth through specialized skills rather than focusing on a single area.

How This Skill Works

The audit analyzes the provided site or project, classifies findings by severity (Critical, High, Medium, Low), and returns actionable recommendations with code examples for fixes. It compiles results into a prioritized plan that operators can implement and verify with follow-up checks.

When to Use It

When asked to audit my site across multiple areas (performance, accessibility, SEO, and best practices).
When you want a Lighthouse-based quality review covering 150+ checks.
When checking page quality before release or deployment.
When you need an orchestration of specialized skills for depth rather than a single-area audit.
When preparing a stakeholder-ready report on overall web quality.

Quick Start

Step 1: Provide the target URL or project and initiate a Lighthouse-based quality audit.
Step 2: Review findings, categorize by severity, and assemble a prioritized list of fixes with examples.
Step 3: Deliver the report, annotate fixes with code snippets, and schedule a follow-up audit to verify improvements.

Best Practices

Run the Lighthouse-based audit and categorize findings by severity (Critical, High, Medium, Low).
Provide actionable fixes with concrete code examples for quick wins and long-term improvements.
Prioritize performance improvements: image compression, code splitting, and critical CSS.
Incorporate accessibility checks: meaningful alt text, color contrast, keyboard navigation, and skip links.
Verify SEO basics: valid robots.txt, XML sitemap, canonical URLs, and unique meta tags.

Example Use Cases

Audit a product landing page to reduce LCP below 2.5s and minimize CLS by stabilizing hero images.
Identify and fix missing alt text and keyboard traps on a blog post page to improve accessibility.
Resolve duplicate meta descriptions and implement canonical URLs across a multi-page site.
Run a full site audit to generate a prioritized fix list for an e-commerce platform with 150+ checks.
Provide code samples (HTML/JS/CSS) for common fixes and guide the team through implementing them.

Frequently Asked Questions

Add this skill to your agents