Check: Verify that priority construction templates remain usable on mobile before treating project photography as complete. Evidence required: Field measurements where available, repeatable lab tests for representative service, project, and contact templates, transferred image sizes, rendered image dimensions, and a list of the heaviest assets on each sample page.
Pass condition: Essential content and actions render without avoidable instability or media that overwhelms the page, and Largest Contentful Paint is compared with the 2.5 second reference threshold as diagnostic evidence rather than a visibility guarantee.
Fail condition: Large photos, fonts, scripts, or layout movement interfere with reading or contact actions, or the team cannot identify which assets are responsible for the observed slowdown. Severity: High when the problem appears on templates used for service evaluation, project review, or enquiries.
Owner: Web development or technical SEO, with project marketing supplying source media that can be prepared for its actual display size. Corrective action: Resize and compress media for its rendered use, choose an appropriate modern format when supported, declare dimensions, defer nonessential assets, and remove unnecessary scripts only after checking their business function.
Validation step: Run the same mobile tests again on the same templates and compare transfer size, visual stability, and measured performance before and after the change.
Check: Verify that the preferred version of each priority URL is discoverable through the site and technically eligible for indexing. Evidence required: Crawl exports, indexation inspection, canonical targets, robots directives, XML sitemap entries, response codes, and internal-link paths for core service pages and approved project evidence.
Pass condition: The intended pages are reachable through useful internal links and do not conflict with blocking directives, unrelated canonicals, redirect chains, duplicate paths, or broken responses.
Fail condition: A commercially important page is orphaned, blocked, duplicated without control, redirected through avoidable chains, canonicalized elsewhere without justification, or expected to be found only through search results.
Severity: Critical when the defect prevents access to a page used for service research, project qualification, enquiries, or procurement review. Owner: Technical SEO and web development. Corrective action: Resolve directive conflicts, repair broken links and redirects, reconnect orphaned pages through purposeful navigation or contextual links, and keep the XML sitemap limited to canonical URLs the firm intends search engines to consider.
Validation step: Re-crawl after release, inspect the affected URL, and verify that the preferred address returns the intended response, is internally linked, and remains technically eligible for indexing.
Check: Verify that site security, navigation, forms, and linked business documents work in the journeys a prospect actually follows. Evidence required: HTTPS checks, successful form tests, mobile navigation tests, broken-link reports, and manual access checks for capability statements, project files, safety documents, or other business-critical resources linked from the site.
Pass condition: A visitor can move from service or project research to the intended contact action and open the supporting material without browser warnings, broken controls, dead links, or inaccessible files.
Fail condition: Mixed content, certificate or protocol problems, broken forms, dead document links, or mobile navigation defects interrupt research or prevent an enquiry from reaching its destination.
Severity: High when the issue blocks contact or hides information used for due diligence. Owner: Web development, with marketing or operations confirming that the linked documents are current and appropriate for publication.
Corrective action: Repair security and protocol issues, replace or remove dead resources, test form routing, and simplify navigation when priority pages are hard to reach. Validation step: Repeat the same task flows on common mobile and desktop browsers and record successful navigation, submissions, and document access.