A mobile website audit focused on customer tasks
A mobile audit should test the tasks customers actually need: understanding the offer, reading evidence and taking the next action.
AI-assisted practical guide · Editorial approach
The useful starting point
A mobile audit should test the tasks customers actually need: understanding the offer, reading evidence and taking the next action. Check layout, loading, keyboard behaviour and errors along that journey. A responsive screenshot alone cannot prove the interaction works.
Understand the decision
Choose representative pages with long headings, dense tables, forms and large images. Test narrow screens and a real interaction sequence. Watch for sticky elements that cover controls, menus that lose focus and images that crop out useful detail. Avoid relying on one device width; content length and browser behaviour can expose different failures.
A practical approach
Choose one visitor task and walk through it on a phone. Read the page without using knowledge of the business: can you explain the offer, its limits and the next action? Then test the complete action with synthetic details in a test environment. Include missing fields, invalid inputs, slow responses, interruptions and retries. A click is a sign of interest; it becomes an enquiry only when the receiving system confirms durable acceptance.
- Select complete tasks rather than random pages.
- Test narrow screens and long real content.
- Inspect sticky bars and keyboard focus.
- Exercise errors and slow responses.
Illustrative example
A restaurant site could be checked from menu discovery to a reservation request. The auditor would inspect opening information, readable dishes and whether the form fits above any sticky bar. A homepage that looks attractive would not excuse an unusable final step.
A mistake to avoid
Do not call a site mobile-ready solely because columns stack. Readability, performance and receiving-system feedback are part of the experience.
What to review
Record task failures, horizontal overflow, obscured actions and layout movement; resolve issues by their impact on the visitor's intended action.
Turn the guide into a working brief
Create a short acceptance checklist covering content ownership, keyboard access, error messages, receipt behaviour and the receiving team. Give every unresolved item an owner. Keep the next action proportional to the visitor’s readiness: a practical guide or price explanation may suit someone who is not ready for a sales call. Inspect a few conversations alongside analytics so that a technical event is not mistaken for a useful commercial outcome.
Common questions
What should I prepare before asking for help?
Start with this checklist: Select complete tasks rather than random pages. Test narrow screens and long real content. Inspect sticky bars and keyboard focus. Exercise errors and slow responses. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Record task failures, horizontal overflow, obscured actions and layout movement; resolve issues by their impact on the visitor's intended action. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- W3C WAI: Forms Tutorial
Reference for accessible labels, instructions and feedback. Original business examples are illustrative, not research findings or verified client results.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.Related guides
What should a service page include to generate useful enquiries?
A service page should explain the problem it solves, who it suits, what is included, what needs confirmation and the next action.
Read the guide →How many fields should an enquiry form have?
Use the fields the receiving team needs to take the next useful step.
Read the guide →Contact page design for customers who are not ready for a call
A contact page should offer a clear, low-pressure way to describe a need and understand the next step.
Read the guide →