A mobile website checklist for service businesses

Website design

The short answer

Test whether a customer can understand the service, check fit and contact you on a real phone. Include the menu, readable enlarged text, tap targets, loading behavior, forms, errors and the final confirmation. A page shrinking to phone width is only the start. The important test is whether people can complete the task without covered controls, lost answers or uncertainty about whether their request was received.

Use this checklist on your homepage, a key service page and the contact or quote route. Include any external booking or payment step a visitor must use; the journey does not stop at the edge of your own website.

Use a real task and realistic phone conditions

Choose one ordinary task, such as requesting an assessment within your service area. Start from the actual link a customer would use. Test on a real phone, ideally on mobile data as well as Wi-Fi. Use more than one browser or device where available; a desktop device preview helps locate issues but cannot reproduce every keyboard or touch interaction.

Record the phone, browser, page and failed step. Ask someone unfamiliar with the site to try without coaching. If they cannot identify the next action, note what they expected. Repeat the same task after a correction so you can tell whether that specific obstacle has gone.

Check service clarity and navigation before decoration

  • Can you identify the actual service without scrolling through a long introduction?
  • Are coverage, opening information or eligibility details available where relevant?
  • Does the menu open, close and lead to the intended page?
  • Are links named for their destination rather than several identical vague labels?
  • Can you return from a service detail to the inquiry route?
  • Are telephone numbers correct and usable, with another contact route where appropriate?

Menus should also work with keyboard and assistive navigation. Avoid relying on hovering, dragging or an unexplained icon for an essential action. Check that opening a menu does not leave the rest of the page in an unusable state after it closes.

Enlarge text and look for clipping or sideways reading

Increase text size and use browser zoom where supported. Headings, labels and buttons should remain available rather than clipping inside fixed-height boxes. W3C's resize-text guidance describes resizing text up to 200% without loss of content or functionality, with stated exceptions.

Also check a narrow layout. W3C's reflow guidance uses a width equivalent to 320 CSS pixels for vertically scrolling content. Ordinary paragraphs should not require back-and-forth horizontal scrolling. A genuine data table may need its own scrolling region, but visitors still need readable labels and a way to reach the whole table.

Try taps, overlays and the on-screen keyboard

Tap the menu, close button, telephone link and primary action without carefully aiming. Controls should be distinct and comfortably spaced. WCAG 2.2's minimum target-size guidance describes 24 by 24 CSS pixels with defined exceptions and spacing alternatives. Larger controls may be more comfortable than merely satisfying that minimum.

Open cookie notices, chat controls or fixed contact bars if present. Check that they do not cover the content, form errors or submit button. Rotate the phone, open the keyboard and return from an external link. A layout that works only before the keyboard appears is not a complete mobile form test.

Check loading, responsiveness and visual stability

Observe whether the main information arrives promptly, controls react and the page stays still while loading. A late image or banner that moves the button as someone taps is a usability issue even if the page eventually looks correct.

Google's Web Vitals guidance distinguishes loading, responsiveness and visual stability. Use performance tools to investigate those areas, not as a substitute for completing the task. A lab score is not the experience of every customer, and field data may be unavailable for low-traffic pages. Prioritize a demonstrated delay or obstruction rather than replacing the entire site to chase a score.

Complete the form, including mistakes and confirmation

Check that fields have visible labels, helpful keyboards and appropriate autofill. Try a legitimate name, a longer message and an optional field left blank. Required details should support the next decision. Let people say they do not know a technical measurement rather than force a guessed answer.

  1. Leave one required field blank and submit.
  2. Find the error and correct it.
  3. Confirm other valid answers remain.
  4. Submit a clearly labeled test request.
  5. Read the completion message without searching below an overlay.
  6. Verify the saved request and staff notification.

Use the delivery checks if the staff side is missing. An attractive mobile success state is not evidence that a message reached the team.

Turn observations into a repair list

Illustrative checklist result: a service page explains coverage clearly, but its sticky call bar hides the form button when text is enlarged. Its upload field is required even when customers have no photograph. The menu and ordinary content work well.

The first work is to remove the obstruction and reconsider the required upload. Keep the useful navigation and content. Retest enlarged text, the keyboard, missing input and staff receipt. A different hero image can wait while an essential action is blocked.

Assign an owner and retest result to each issue. Our website design and redesign work can address these customer tasks. This checklist is a practical starting point; a fuller accessibility assessment covers more than the checks here.

A few follow-up questions

Does a responsive theme guarantee a usable mobile site?

No. Content, overlays, third-party tools and form behavior can still fail. Test the installed site and its actual customer journey, not just the theme demonstration.

Can we test everything in a desktop browser preview?

Use previews for quick layout checks, then test real phones for touch, text settings, keyboard behavior and external-app handoffs. Record which devices you actually checked.

Should we remove all tables on mobile?

No. A real comparison table can remain useful when its headers and caption are clear and the table can be reached and scrolled. Do not let it make the entire page overflow horizontally.

Sources and further reading

Show us the phone task that gets stuck

Share your website address, device and the step that is difficult. We can discuss focused mobile fixes or a redesign where the task calls for one.

Discuss your mobile website See what our website design service includes
Website by TelosOps