Audit the production site's technical foundation on representative templates rather than assuming every page behaves the same.
Checkpoint: modern media delivery. Evidence required: inspect thumbnails, poster images, background loops, and exported video formats on high-traffic templates. Pass when assets use formats and compression appropriate to the browser and delivery method without visibly degrading the work.
Fail when unnecessarily large media is shipped by default or duplicate versions load without need. Severity: high on media-heavy landing pages. Owner: front-end or web production. Corrective action: evaluate WebP for imagery and codecs such as AV1 or VP9 where they fit the playback stack. Validation: retest the same pages after deployment and confirm the intended asset is served.
Checkpoint: content delivery. Evidence required: document where large static and media assets are served from and compare load behavior for representative users. Pass when delivery is reliable for the audiences the studio actually serves.
Fail when remote users repeatedly receive avoidable latency from the asset pipeline. Severity: medium to high depending on observed impact. Owner: infrastructure or web owner. Corrective action: configure caching or a CDN where measurements justify it. Validation: repeat the same regional tests and verify that media URLs, cache behavior, and playback still work.
Checkpoint: Core Web Vitals and interaction quality. Evidence required: field data where available, supplemented by repeatable lab tests on important templates. Pass when the page has no material performance defect blocking viewing, navigation, or inquiry actions.
Fail when a specific element or script consistently creates a poor experience. Severity: high when the affected page is commercially important. Owner: front-end engineering. Corrective action: prioritize the measured bottleneck rather than chasing a generic score.
The source previously used an LCP target under 2.5 seconds; treat that value as a recorded performance threshold for this checklist, not as a guarantee of rankings. Validation: compare the same metric and user path after implementation.
Checkpoint: broken links and redirect chains. Evidence required: crawl the site and inspect portfolio, service, archive, and contact links. Pass when priority URLs resolve to the intended destination without unnecessary hops.
Fail when internal links hit broken pages, chains, or irrelevant destinations. Severity: medium, rising to high for core inquiry paths. Owner: SEO or content operations. Corrective action: update internal destinations and consolidate avoidable chains. Validation: recrawl the affected URLs and manually test key navigation paths.