Example Website Lead Leak Check for a NZ Service Business

This anonymised example shows how a small service-business website can look acceptable while still making enquiries harder than they need to be.

The check starts with the customer path, not with design taste.

Mobile friction is usually the first leak

Many service sites technically respond to mobile screens but still force visitors to pinch, hunt, or scroll through weak hierarchy before they can act.

CTA clarity matters more than button volume

A page can have several buttons and still make the next step unclear. Useful CTAs explain what happens next and sit close to the moment of intent.

Forms carry commercial risk

Required fields can be heavier than the job needs.
Validation can fail unclearly on mobile.
Notifications can be unreliable.
Analytics can miss the successful submission.

Proof gaps create hesitation

Small trust gaps add up: dated copy, thin service detail, missing location cues, and no clear examples of the work all make a visitor less confident.

Fastest fixes

Make the contact path obvious on mobile.
Reduce form effort and confirm the submit path works.
Rewrite the service-page CTA around the visitor's next step.
Add real proof only where permission exists.