Use this section to verify whether the website can be crawled, rendered, navigated, and trusted without obvious technical friction. Each item needs an evidence record and a named owner before it can be marked complete.
Optimize Large Format Image Files. Evidence required: a representative set of portfolio and service-page images plus a performance report showing how those assets load on mobile. Pass condition: project images are delivered in appropriately compressed modern formats where supported, dimensions are suitable for their display context, and offscreen media does not block initial use of the page.
Severity: high when large media materially delays important content. Owner: developer or site manager. Corrective action: resize, compress, convert, and configure image loading without degrading the project proof customers need.
Validation: rerun the same performance test and manually inspect priority pages. Tools: TinyPNG, WP Rocket, Screaming Frog
Implement LocalBusiness Schema Markup. Evidence required: the rendered structured data on pages where business information is represented. Pass condition: markup describes information that is actually visible and accurate on the page, uses an appropriate supported type, and contains no fabricated locations, services, ratings, or credentials.
Severity: medium because structured data can improve machine readability but should not be treated as a guaranteed ranking factor. Owner: developer or SEO lead. Corrective action: align the markup with the real business entity and on-page content.
Validation: test the rendered markup and compare every important field with the visible page. Tools: TechnicalSEO Schema Generator, Google Rich Results Test
Fix Mobile Navigation and Clickable Elements. Evidence required: manual testing on representative mobile viewports and Search Console data where relevant. Pass condition: menus open reliably, key service information is reachable, buttons do not overlap, and the quote path can be used without accidental taps.
Severity: high on pages that generate inquiries. Owner: designer or developer. Corrective action: repair responsive layout, spacing, menu behavior, and tap targets. Validation: repeat the same journey from landing page to inquiry completion. Tools: Google Search Console, Mobile-Friendly Test
Enable HTTPS and Secure Data Protocols. Evidence required: browser inspection and a crawl confirming that canonical pages and form destinations use secure URLs without avoidable mixed-content warnings.
Pass condition: visitors can browse and submit quote information without a browser security warning caused by the site configuration. Severity: critical when insecure resources or redirects affect customer-facing forms.
Owner: developer or hosting administrator. Corrective action: configure the certificate, redirects, internal links, and embedded resources correctly. Validation: crawl again and manually test inquiry pages. Tools: SSL Certificate, Really Simple SSL