Check: project imagery is delivered efficiently without removing useful visual evidence. Evidence required: page templates, representative gallery pages, rendered image dimensions, file formats, loading behavior, and field or lab performance data where available.
Pass condition: images are appropriately sized for their display context, noncritical gallery assets do not block the initial experience, and important project photos remain clear enough for homeowners to evaluate the work.
Fail condition: oversized originals are served broadly, galleries delay interaction, or image handling causes obvious layout instability. Severity: high when affected pages are core replacement or quote pages.
Owner: web engineering or the site-performance owner. Corrective action: generate responsive image sizes, use efficient supported formats such as WebP or AVIF, reserve layout space, and defer noncritical gallery assets.
Validation: retest representative templates in PageSpeed Insights and browser developer tools, then confirm that conversion elements remain usable.
Check: mobile usability supports the way homeowners actually browse. Evidence required: mobile rendering, tap targets, form completion, navigation, viewport behavior, and Search Console usability signals where available.
The source previously stated that 60-70% of homeowners begin replacement research on mobile devices, but it provides no supporting source URL, so keep that range as historical context rather than a verified benchmark.
Pass condition: a homeowner can understand the service, review project evidence, compare relevant options, and request contact on a small screen without zooming or fighting the interface. Fail condition: key controls are hard to tap, text is difficult to read, content overflows, or forms cannot be completed reliably.
Severity: critical on pages that receive meaningful mobile traffic. Owner: web engineering with marketing review of the contact path. Corrective action: fix responsive layouts, simplify form fields, improve tap targets, and remove mobile-only blockers. Validation: complete the quote path on representative phones and compare field performance before and after the change.
Check: structured data reflects visible, accurate business and service information. Evidence required: rendered page content, JSON-LD, entity details, business information, and structured-data validation output.
Pass condition: markup describes content users can see, uses appropriate eligible types, and matches the actual business and service information. Fail condition: markup invents offers, ratings, service areas, products, or other facts, or exists mainly because someone expects a ranking boost.
Severity: medium unless incorrect markup creates a material misrepresentation. Owner: technical SEO or engineering with business-data review. Corrective action: remove unsupported properties, align markup with visible content, and keep entity details consistent with the site.
Validation: test syntax, compare marked facts against the page, and monitor Search Console for relevant errors or warnings.
Check: Core Web Vitals issues are diagnosed at the template and element level. Evidence required: field data where available, lab traces, the elements responsible for slow loading or layout shifts, and the affected templates.
Pass condition: the team knows which elements create the problem and has addressed the causes that materially affect important pages. Fail condition: the site relies only on a summary score without identifying the element, template, or resource creating the issue.
Severity: high when poor performance affects core service or lead-generation pages. Owner: engineering. Corrective action: prioritize the largest visible content appropriately, reserve dimensions for dynamic assets, reduce blocking resources, and retest. Validation: compare field and lab evidence after deployment rather than assuming a plugin setting solved the issue.