A mobile website review should start with the tasks a customer needs to complete. A site can fit a phone screen and still make a service hard to understand, a form difficult to use or a phone number hard to tap.
Choose the tasks to test
List three to five actions that matter to the business, such as finding a service, checking an important detail, calling the company or sending an enquiry. Begin from the page a visitor is most likely to reach from search or a shared link. Record the steps and note where the task becomes unclear.
Test on real phones
Use at least one smaller screen and one larger phone if available. Check that text can be read without zooming, buttons have enough room to tap, menus open and close, and important information does not disappear behind sticky elements. Complete each form with the phone keyboard. Confirm that field labels, required-field messages and error instructions remain visible.
Check speed and layout stability
Use PageSpeed Insights or browser performance tools to find possible delays, then confirm the effect while completing the customer task. Look for large images, third-party scripts or late-loading content that shifts buttons and text. A score is a diagnostic signal, not proof that a page works well for a customer.
Prioritise fixes by their effect
Fix barriers that prevent a visitor from understanding, navigating, contacting or purchasing first. Next address repeated friction and visual issues that make a task harder. Keep a short before-and-after record so the same journeys can be retested after changes.
Decide what kind of help is needed
If the problem is limited to a few pages or controls, a focused interface repair or tune-up may be enough. A larger redesign is more appropriate when the navigation, content structure or technology prevents many important tasks. Ask a consultant to show the observed problem, proposed fix and acceptance test for each priority.
A useful mobile consultation ends with a ranked list of issues, clear owners and a way to confirm that the changes work. Start with visitor tasks, then choose the smallest scope that removes the barriers.