A website fitting inside a phone screen is only the beginning. People still need to read it, open the menu, compare services and finish whatever they came to do. A booking button hidden beneath a banner or a form that loses its contents can make a visually attractive page frustrating.
For a Cheltenham business, a useful mobile review follows real customer tasks. You do not need a device laboratory to spot important problems, although a developer should verify fixes across an agreed range of browsers and screen sizes.
Start with three ordinary visits
Choose a service page, a page containing examples or products, and the contact route. Open each directly on your phone instead of always entering through the homepage.
Try these tasks without relying on what you already know:
- Find out whether the business provides the service you need.
- Find a relevant example or useful detail about that service.
- Contact the business or start a booking.
Note where you hesitate, mis-tap or need to zoom. Ask someone unfamiliar with the site to try the same tasks if possible. Explain the goal, then let them attempt it without coaching; otherwise your instructions can conceal the confusing parts.
Look for layout problems in the content
Long headings, addresses, product names and embedded tools often reveal weaknesses that a neat demonstration page misses. Turn the phone sideways, increase the text size and try a page with more content than usual.
The basic idea of responsive design is that layout adapts to the available screen and how people interact with it. Google's web.dev guidance covers fitting content to the viewport and avoiding restrictions that stop visitors zooming. Responsive web design basics.
Ask a developer to investigate horizontal overflow instead of simply hiding everything outside the screen. Hiding the overflow may remove the visible symptom while leaving a button or piece of information inaccessible.
Check menus and persistent controls
Open every level of the navigation. Can you close it easily? Is it obvious which items are links and which expand another group? Does it cover the page in a way that makes the next action difficult to understand?
Headers, cookie controls, chat bubbles and sticky buttons all compete for a small screen. View them together, particularly with the keyboard open. A control that works alone can become unusable once another panel appears.
Touch testing matters, but also use a keyboard on a larger device. Ensure you can reach the menu, links and form fields and see where the focus is. A mobile review should not introduce a design that excludes other ways of using the site.
Complete the form, including a mistake
Forms deserve a separate pass because reading a page is much easier than entering information on a small screen. Try an ordinary message, then leave a required field empty and correct it.
Check that the form preserves what you have already entered. Make sure the error explains what needs changing, and that the completion message is easy to recognise. W3C's form guidance recommends feedback that clearly communicates both errors and successful completion. W3C guidance on form notifications.
For bookings, follow the journey through any external provider. A usable website cannot compensate for a booking calendar that becomes unreadable after the customer taps through. The booking system planning guide covers that wider journey.
Example: a restaurant menu on a small screen
Suppose an independent Cheltenham restaurant publishes its menu as a large image. This is a hypothetical example.
The image may scale down until the text becomes tiny. A practical improvement would make the essential menu information available as readable page content, keep any downloadable version as an additional option, and put opening details and booking access nearby.
Testing should include changing text size and opening the booking tool, not just taking a screenshot of the new menu. The success criterion is that someone can decide whether to visit and take the next step.
Record defects so a developer can reproduce them
A report that says "mobile is broken" leaves too much to interpretation. Include the page address, device, browser, action taken and expected result. A screenshot can illustrate the position of a problem, while a short description explains the task it prevented.
Prioritise blocked actions, hidden information and unreadable content before decorative inconsistencies. If the layout behaves but the page takes too long to respond, use the slow website troubleshooting guide to investigate that separately.
I build and improve websites for Cheltenham businesses, with scope based on the work the site needs. Send James a page that is difficult to use and describe the customer action you want to make easier. That provides a clear starting point for a focused repair or a wider redesign.