Your next customer is probably holding a phone.

What to check before calling a website mobile-friendly: content, navigation, forms and speed.

Share

Design the decision, not just the screen.

A responsive grid is useful, but it is not the whole mobile experience. A visitor should be able to understand your offer, find relevant proof and take the next step without hunting through a desktop layout that has been squeezed into one column.

Start by deciding what the first screen must communicate. A clear service, a meaningful difference and an obvious next step usually matter more than a long opening animation.

Give content room to breathe.

Use a readable body size and a comfortable line length. Break long passages into sections with descriptive headings. Keep important details in text rather than embedding them in an image. A phone should not force a visitor to pinch-zoom to read your core message.

  • Check text at narrow widths and with larger system text settings.
  • Keep primary actions easy to tap.
  • Make menus usable with a keyboard and assistive technology.
  • Keep sticky controls from covering page content.

Reduce friction in the enquiry.

Ask for the information that helps you respond. Use appropriate input types for email and telephone fields. Label every field clearly, keep validation understandable and explain what happens after submission.

If a form opens an email client or WhatsApp instead of saving an enquiry, say so. A polished success message should never imply that a message was received when it was not.

Treat speed as a content decision.

Large imagery, third-party widgets, fonts and video all have a cost. Compress images, supply appropriate sizes and defer assets that are not immediately needed. Avoid loading a full video just to decorate the first screen.

Test representative service and contact pages as well as the homepage. A fast landing page does little good if the enquiry route is slow or broken.

Test the complete journey.

Try the website on a narrow phone, a larger phone, a tablet and a desktop. Open the menu, follow a service link, read the proof, complete the form and verify where the enquiry arrives. Check focus visibility, reduced motion and error states.

The useful question is not whether the page fits. It is whether a person can complete their task comfortably.

Run the test as three real customer tasks

Give someone the link you actually send in campaigns. Ask them to identify who the service is for, find any information they need to decide whether it fits, and complete the next step. For a service business that might mean opening the local page, checking availability and submitting a brief. For a store it could mean finding a size, checking shipping and reaching payment. Observe where they pause and where they need help. Repeat once on a modest connection so you can see how a late image, font or player affects the task. Keep a record of the phone, entry page and task outcome.

Write down what counts as fixed

For every issue, record the page, the device or width, what happened and the expected behaviour. A report that says “the form needs improvement” is hard to test. A report that says “at 360 pixels, the sticky chat button overlaps the form submit button after a validation error” gives a developer a clear reproduction. Check the fix on the same phone and then on a larger one. For performance, compare the same page with a similar network profile and supplement lab scores with real visitor data when available. Prioritise failures on the path to enquiry or checkout before polishing details elsewhere.