A portfolio-heavy cabinet maker site should be technically reviewable before more content is added. These checks focus on whether important pages can be discovered, loaded, interpreted, and reached from relevant project examples.
Check: Portfolio image delivery
Evidence required: A sample of major service pages and project galleries, original image dimensions, delivered image dimensions, file format, file weight, and a mobile PageSpeed Insights review.
Pass/fail condition: Pass when images are sized close to their displayed dimensions, modern formats such as WebP or AVIF are used where the stack supports them, the largest visual is not unnecessarily oversized, and the page remains usable while images load.
Fail when full-size originals are routinely sent to small display slots or essential portfolio content becomes difficult to use on mobile. Severity: High for image-heavy landing pages. Owner: Web developer or site administrator.
Corrective action: Resize source assets for their actual placements, generate responsive variants, compress carefully enough to preserve finish and joinery detail, and lazy-load below-the-fold media where appropriate.
Validation step: Retest the same page template on mobile, compare delivered dimensions with rendered dimensions, and visually inspect representative wood grain, edge detail, and finish texture. Tools: ShortPixel, Squoosh, PageSpeed Insights.
Check: Structured data accuracy
Evidence required: The visible business name, address or service-area configuration, contact details, page purpose, any existing JSON-LD, and a record of which schema types are currently implemented.
Pass/fail condition: Pass when markup uses applicable schema types, matches the visible page, and does not label a custom project, service, or business as something it is not. Fail when markup contains unsupported claims, stale business information, fabricated reviews, or a Product representation for content that is not actually a product offering.
Severity: Medium because incorrect markup can create ambiguity even when it does not produce a rich result. Owner: SEO lead with developer review. Corrective action: Remove unsupported properties, align LocalBusiness or other applicable markup with the visible content, and keep structured data descriptive rather than promotional.
Validation step: Test the deployed markup with Google Rich Results Test where relevant and inspect the rendered source. Treat Schema.org vocabulary as a reference for meaning, not as a promise of search visibility. Tools: Schema.org, Google Rich Results Test.
Check: Mobile usability and Core Web Vitals diagnostics
Evidence required: Mobile PageSpeed Insights results, Search Console page experience or Core Web Vitals reporting when available, and manual tests of navigation, galleries, forms, and contact actions on a phone-sized viewport.
Pass/fail condition: Pass when key pages can be navigated and used without blocked controls, unreadable text, unstable gallery interactions, or avoidable performance problems. Fail when important calls to action, image galleries, or forms are difficult to use on common mobile layouts.
Severity: High for pages that receive meaningful mobile traffic. Owner: Web developer. Corrective action: Fix layout shifts, oversized assets, blocking scripts, inaccessible controls, and mobile interaction defects in the affected template rather than chasing a score in isolation.
Validation step: Repeat the field-oriented and lab diagnostics and complete the same user journey manually after deployment. Tools: PageSpeed Insights, Search Console.
Check: Internal link paths from projects to services
Evidence required: Crawl data, a list of indexable project pages, their internal links, and the destination used for the primary cabinetry service context.
Pass/fail condition: Pass when relevant project pages include descriptive links to the service or category page that genuinely explains the work shown, and important service pages are reachable through normal site navigation.
Fail when galleries are isolated, links rely on vague anchors, or project pages point to unrelated destinations. Severity: Medium to high depending on how much of the site is isolated. Owner: SEO lead or content manager.
Corrective action: Add contextual links from real project descriptions to the cabinet maker SEO hub only where that destination is relevant, and repair broken or orphaned navigation paths. Validation step: Re-crawl the site and manually confirm that a reader can move from a representative project to the relevant service context without using search. Tools: Screaming Frog, Ahrefs.