A remodeling website can look polished while still hiding expensive technical friction in project galleries, service templates, old campaign URLs, lead forms, and third-party scripts. Audit representative pages first, keep the baseline evidence, and only close a check after the same test passes on the live implementation.
Project image delivery
Evidence required: Build a page-level inventory for representative kitchen, bathroom, addition, whole-home, and portfolio URLs. For each important image, record file size, format, intrinsic dimensions, rendered dimensions, loading behavior, and whether the asset is reused at unsuitable sizes.
Include a mobile performance capture from the same pages. Older galleries may still contain source files around 5MB, so inspect actual assets instead of assuming the media library is optimized. Pass condition: Important images are delivered at dimensions appropriate to their rendered use, use efficient formats where the site stack supports them, remain visually credible for evaluating workmanship, and do not create avoidable loading, responsiveness, or layout problems in the tested journey.
Fail condition: Oversized originals, unnecessary transfer weight, missing dimensions, duplicate downloads, or gallery behavior creates a repeatable technical or usability problem on an important page.
Severity: High when image delivery degrades a core service, portfolio, or contact journey; otherwise Medium. Owner: Web developer or site owner responsible for media delivery. Corrective action: Resize source assets, convert formats when appropriate, configure responsive delivery, preserve meaningful alternative text for informative images, remove redundant downloads, and retest every gallery component affected by the change.
Validation step: Repeat the same page and device tests, compare the live results with the baseline, and manually review image quality, gallery controls, zoom behavior, and the transition into the contact path.
Structured data accuracy
Evidence required: Inventory the structured data present on service, company, project, and genuine location pages. Compare each important property with the rendered content, the entity actually represented, and current documentation for the schema type being used.
Pass condition: Markup is syntactically valid, describes content a visitor can verify on the page, uses an appropriate type, and does not invent services, locations, reviews, project details, or business attributes.
Fail condition: Markup contains validation errors, contradicts visible information, represents a service or location the business cannot substantiate, or exists only because someone assumed schema itself guarantees rankings or AI inclusion.
Severity: Medium, raised to High when the markup materially misrepresents the business or an important service. Owner: SEO lead with developer support. Corrective action: Remove unsupported properties, align each retained property with visible content, use only appropriate supported types, and document the business or page evidence for fields that could be misunderstood later.
Validation step: Run an appropriate structured-data validator, inspect the rendered page, compare the final output with the visible content, and confirm that no implementation note is being treated as a ranking guarantee.
Broken project and service destinations
Evidence required: Crawl internal links and collect broken or misdirected destinations from navigation, service pages, project galleries, blog posts, old campaigns, and lead-path components.
Review Search Console data where available and identify any current links that return a 404 response. Pass condition: Important internal links resolve to the intended live destination, deliberately removed pages have a sensible disposition, and a homeowner can move through current service, project, and contact journeys without reaching a dead end.
Fail condition: A live page links to a missing project or service destination, a redirect sends readers to unrelated content, or a deleted URL breaks a current navigation or conversion path. Severity: High for primary navigation, core services, portfolio evidence, and contact paths; Medium for isolated references with little user impact.
Owner: Web developer or content manager. Corrective action: Restore content that should still exist, change the source link when a better live destination exists, or add a relevant redirect only when there is a genuine replacement.
Do not redirect unrelated removed pages to a generic page simply to suppress an error. Validation step: Re-crawl the affected paths and manually follow the corrected journey from each important source page to the final destination.
Deferred media loading
Evidence required: Inspect how below-the-fold project images, before-and-after components, videos, and embedded assets load on representative mobile and desktop pages. Record the baseline request pattern and manually note any delayed interaction, blank component, or layout shift.
Pass condition: Offscreen media is deferred where appropriate without postponing content that is immediately needed, hiding important project context, blocking accessibility, or breaking gallery interaction.
Fail condition: The page downloads unnecessary offscreen media immediately, or the deferral implementation causes missing content, unstable layout, broken controls, or a worse lead journey. Severity: Medium, raised to High when the behavior affects a primary service, portfolio, or contact path.
Owner: Front-end developer. Corrective action: Configure native or application-level deferred loading for suitable assets, exempt media needed immediately, preserve dimensions, and test sliders, comparison modules, and embedded media with real project content.
Validation step: Repeat the original page tests, compare request behavior with the baseline, and manually complete the entire gallery and contact journey on devices represented in the company's analytics.