A business owner compares printed website pages around a worktable

The website, without jargon

Your website should help customers. It should not test your technical knowledge.

You do not need to know code. You need to verify whether someone understands, finds the right button and contacts you easily.

Test two real journeys: requesting a service and doing it on a phone. Each hesitation gives you a more useful repair order than a list of technical terms.

See the four starting points

Two useful questions

What is genuinely blocking your website?

Observe a behaviour, then fix its cause.
  1. 01Visitors do not contact youThe website gets visits, but enquiries remain rare or hard to explain.See the check
  2. 02The website blocks people on phonesThe website looks acceptable on a computer but becomes slow or awkward on a phone.See the check
  3. 03Essential website pagesEvery page should answer a real customer question, not merely fill a menu.See the check
  4. 04Trust and contactThey contact it when the offer feels real, the risk is understandable and the next step is reasonable.See the check

Without becoming technical

Inspect the journey before discussing a redesign

A website can look good and still make contact difficult. Three actions give an initial answer.
  1. 01

    Choose one action

    Call, request a quote or book: test one goal.

  2. 02

    Try it on a phone

    Complete the journey with one hand, like a rushed customer.

  3. 03

    Record hesitation

    Every return, zoom or hunt for a button is a concrete issue.

02:00

Would an outside view help?

The assessment repeats these checks without asking you to speak technically.
Assess it in 2 min