site-speed-optimization

Auditing HTML for site speed issues involves counting and measuring DOM elements like scripts, inline CSS, and images against defined thresholds. This process identifies render-blocking resources and weight-related problems, returning PASS, WARN, or FAIL findings.

A static HTML page may load slowly due to excessive external scripts, overly large inline CSS, or unoptimized image formats. These HTML-level factors increase page weight and delay rendering, directly hurting SEO and overall performance.

Yes, when auditing a static HTML page, the check warns if pages are not using Next.js Image optimization patterns. It explicitly avoids duplicating Core Web Vitals render-blocking and font-loading checks to focus on HTML-level contributors.

The best way to check image alt text for SEO and accessibility is to validate image alt coverage within the HTML DOM. This identifies missing alt attributes and flags potentially inefficient image formats that slow down page loads.

To reduce CSS weight and script count, you must detect excessive external scripts and overly large inline CSS blocks within the HTML. Applying defined PASS/WARN/FAIL thresholds to these elements provides concrete suggestions to fix render-blocking delays.

An HTML-level performance audit is limited to static DOM attributes and elements, avoiding overlap with Core Web Vitals render-blocking and font-loading checks. It focuses strictly on script count, CSS weight, and image alt coverage.