Introduction
What is Web Guard?
Web Guard is an all-in-one web quality guard that enforces Performance, Accessibility, SEO, Schema, Security, and UX standards in CI/CD pipelines and local development. It combines Lighthouse, axe-core, and HTML analysis into a single CLI — failing the build when any pillar drops below your configured thresholds.
Instead of juggling multiple tools, Web Guard gives you a single command that audits your site across six quality pillars. Each pillar reports violations with severity levels and actionable fix hints.
The Problem
Web quality spans multiple dimensions that are hard to check consistently. Teams often miss regressions because each concern requires a different tool:
- Performance degrades after a deploy but nobody runs Lighthouse
- Accessibility violations slip in because axe-core isn't in the CI pipeline
- SEO metadata is missing or malformed on new pages
- JSON-LD structured data has invalid or missing required fields
- Security headers are absent because nobody checks response headers
- UX issues like tiny touch targets or images without dimensions cause layout shifts
Web Guard catches all of these in a single command, before they reach production.
The 6 Pillars
| Pillar | Engine | What it checks |
|---|---|---|
| Performance | Lighthouse | Score, LCP, CLS, INP, TTFB, FCP |
| A11y | axe-core | WCAG violations by impact level |
| SEO | HTML parsing | Title, meta, headings, canonical, robots, sitemap |
| Schema | JSON-LD | Structured data presence, valid JSON, required fields |
| Security | HTTP headers | CSP, HSTS, X-Frame-Options, Referrer-Policy, Permissions-Policy |
| UX | Puppeteer | Viewport, image dimensions, touch targets, font-display |
Use Cases
- CI/CD pipelines — fail builds when any quality pillar degrades
- Pre-deploy checks — audit staging before promoting to production
- Quality dashboards — export JSON for monitoring tools
- Local development — catch regressions before committing
- SEO audits — validate metadata, headings, and structured data
- Security hardening — ensure all response headers are present
Web Guard requires Chrome/Chromium installed on the machine. In CI environments, use browser-actions/setup-chrome@v1 or similar.