Are homeowners left guessing what happens after a Canterbury build enquiry?
We reviewed canterbury-builders.co.nz across desktop and mobile performance, basic SEO checks and AI/agent readiness, then compared its project and capability presentation with Stu Bell Construction.
The clearest opportunity is to make the enquiry journey easier so that it's quick and easy for a potential customer to find the website and get in touch.
Investigate the 0.573 desktop CLS and 5.6s mobile LCP. Identify shifting elements and the requests delaying the first screen, then fix the highest-impact causes.
Review the Lighthouse accessibility findings on key project and contact pages, then fix verified barriers in navigation, form labels, contrast or keyboard use.
PRIORITY 4
BOTTOM LINE:
Canterbury Builders has real projects and a broad building offer to draw on. A clear build journey can help homeowners understand whether the team fits their project before they enquire. The reports also identify desktop layout movement and a slow mobile first-content measure worth validating and improving.
Want to see how the build journey and the Lighthouse findings fit together?
THE BUILD PROCESS IS NOT PRESENTED AS A CLEAR ROADMAP
The site shows Canterbury Builders’ project types, experience and completed work, but does not appear to give homeowners a clear step-by-step roadmap from first conversation to handover. For a major build or renovation, visitors often need to understand how decisions, pricing and construction will work before they are ready to enquire. A concise process page, grounded in the team’s real approach, could answer those questions earlier and give each project page a useful next step.
LAYOUT MOVEMENT AND MOBILE TIMING ARE WORTH FIXING
DESKTOP CLS IS 0.573; MOBILE LCP IS 5.6 SECONDS
The Canterbury mobile LCP is faster than Stu Bell’s 15.2s result, so it is not a competitive weakness in this comparison. However, 5.6s remains above the recommended 2.5s LCP threshold, while the desktop layout shift score of 0.573 is well above the 0.1 “good” threshold. These are controlled Lighthouse lab results, not evidence that visitors are bouncing. Validate the shifting element and mobile bottleneck, then prioritise fixes that keep content and enquiry actions visible.
NO REAL-USER FIELD DATA
The supplied reports show no CrUX field data, so they cannot confirm real-world Core Web Vitals pass/fail or visitor behaviour. Use the lab metrics above for this comparison, then check analytics and Search Console field data before making user-impact claims.