web-quality-audit

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.

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.

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. Make each title descriptive and concise; display truncation varies by device and result type.
• Meta descriptions. Write useful, page-specific summaries; search engines may choose a different snippet.
• Heading hierarchy. The primary heading is descriptive and the structure is logical; do not fail valid HTML solely for using more than one <h1>.
• Descriptive link text. Not "click here" or "read more".

Technical SEO:

• Mobile-friendly. Responsive design. Tap targets ≥ 48px.
• HTTPS. Secure connection required.
• Page experience signals. Use field Core Web Vitals as evidence, without promising a ranking change.
• Structured data. JSON-LD for rich snippets (Article, Product, FAQ, etc.).

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.

Use the Lighthouse Agentic Browsing results as technical signals for how well assistants can understand and interact with the rendered page.

• Accessible interaction surface. Semantic HTML, labels, names, roles, and states must expose meaningful controls in the accessibility tree.
• WebMCP integrations are valid when present. Review registered tools, schemas, and form coverage; do not add WebMCP solely to raise an audit score.
• llms.txt is optional. A valid file may help compatible tools discover curated content, but a Lighthouse pass does not prove that search or AI products will ingest, rank, or cite it.
• Keep this category separate from SEO claims. Agentic browsability is not evidence of search ranking or AI visibility.

• Core Web Vitals passing
• No accessibility errors (axe/Lighthouse)
• No console errors
• HTTPS working
• Meta tags present

• Check Search Console for issues
• Review Core Web Vitals trends
• Update dependencies
• Test with screen reader

• Full Lighthouse audit
• Performance profiling
• Accessibility audit with real users
• SEO keyword review