webaudit

A comprehensive website audit combines static file analysis with browser-based rendering checks using Playwright screenshots to evaluate UX, SEO, accessibility, performance, and security. This produces structured FAIL, WARN, and INFO findings to highlight issues across desktop, mobile, and various visual states.

Yes, you can run a web audit on both a live URL and a local codebase. The Skill performs static file analysis for code inspection and applies browser-based rendering checks to live sites during QA checks and visual inspections to capture real user views across different devices and states.

You can check your web app for accessibility and low-contrast focus states using Playwright-based screenshots to inspect real user views. The Skill visually verifies keyboard focus, reduced motion, and error states, reporting them as structured FAIL or WARN findings for quick remediation.

Yes, Playwright is required for visual verification during a web audit. The Skill uses the playwright-core dependency to capture screenshots, inspect real user views across desktop and mobile, and verify visual states like dark mode and error conditions.

The best way to find missing meta tags and broken layouts before launch is running an automated full-spectrum review. This Skill evaluates SEO tags and uses Playwright screenshots to catch broken mobile layouts, producing actionable findings and optional safe auto-fixes for certain issues.

Automated web audits for robustness and security are limited to static file analysis and visual rendering checks. While they can identify common vulnerabilities and structural issues, complex security flaws or dynamic robustness issues may require further manual investigation beyond the generated findings.