Practical business website guidance · Updated 1 November 2026

Does your website work well on a phone?

Check menus, service information, readable content and contact routes on a phone. A practical small-business checklist alongside automated observations.

A page fitting inside a phone screen is only the beginning. Customers still need to find the right service, read the evidence and make contact. Test a complete relevant journey instead of relying on a homepage screenshot or one automated score.

Start with a real customer task

Choose a common enquiry: finding an interior painter, checking a service area or asking about a specific repair. Open the website on a phone and try to complete the information-gathering steps without relying on what you already know about the business.

Notice where you hesitate. Is the service name clear? Can you tell whether the business serves the area? Do you know whether to call, send photographs or use a form? Record the actual page and difficulty so a change can address a concrete issue.

Open and close the menu

Check that the menu control is recognisable and responds. Follow a link to a relevant service and confirm that you can return or reach another page. A visible menu icon does not prove that the menu opens or that its links work.

Look for controls hidden behind banners, sticky headers or other overlays. If the menu expands, the content should remain readable and the next action should not become trapped off-screen. Test what happens after navigating, not only the first tap.

Read the service without sideways scrolling

Check the opening explanation, headings, paragraphs, lists and tables. The visitor should not need to zoom to understand ordinary text. Long URLs, large tables, fixed-width images and embedded tools can create overflow even if the homepage looks comfortable.

Inspect more than one page type. A service page, guide and quote form may use different layouts. Break a complex comparison into a readable format or provide controlled table scrolling rather than shrinking the whole page to make it fit.

Make buttons and links practical

The main contact action should be easy to identify and use without competing with several unrelated choices. Check tap targets, spacing and contrast. A tiny text link beside another tiny link can be difficult to select accurately even when an automated test does not flag the whole journey.

Tap-to-call should show the intended number. A WhatsApp link should open the correct business route. An email link should use the intended address. Opening a route is a different test from confirming that a conversation or message reaches the business.

Check the evidence and pictures

Project images should load at a useful size, retain their proportions and have captions that make sense. Avoid placing a large text block over the important part of a work photograph. Keep illustrative concepts and edited previews visibly labelled on a phone as well as on desktop.

A gallery needs usable controls and an obvious way to close an enlarged image. Important service facts should also appear as readable page text; a tiny screenshot of a price table or review is not an effective substitute.

Test forms on your own authorised site

Try the actual fields and validation. Labels should remain understandable, errors should explain what needs correcting and optional information should be marked accurately. Check that the keyboard and sticky elements do not prevent reaching the send button.

Send a clearly labelled test enquiry on your own site and verify receipt in the intended inbox. Do not complete tests on other businesses’ forms. A form being present, or a success message appearing, does not establish delivery or that the reply-to details are correct.

Check banners and persistent controls

Consent notices, chat widgets and bottom contact bars compete for a small screen. Keep choices readable without covering the service or blocking navigation. The page should remain usable after accepting or declining optional analytics.

Check that a fixed contact bar does not hide the last form field or footer link. Avoid adding a new sticky CTA to solve a problem already caused by too many persistent elements. Inspect the screen at the point where the customer needs to act.

Automated checks are useful samples

The Gold Oak checker can return selected mobile observations with the stated capture limits. A result may be unavailable or limited if the page or assets cannot be assessed reliably. That is not automatically a pass or a fault.

An emulated homepage capture is different from every real device, page and interaction. Use it to choose what to inspect manually. Read what the results mean and keep loading measurements separate from full usability.

Keep a short change list

Record the task, page, device, problem and proposed fix. Start with issues that stop a customer finding the service or making contact. After changes, repeat the same journey and check related pages that use the same component.

For enquiries that remain weak despite a working phone journey, read the enquiry diagnosis guide. For loading symptoms, use the speed guide. The appropriate next step may be a focused improvement rather than a complete rebuild.