SEO & usability
How to run a 10-minute website audit that is actually useful
A simple audit framework focused on mobile usability, trust, and enquiry paths.
Published by NMark Designs · · 3 min read
Minutes 0–2: choose a visitor task
An audit without a goal easily becomes a list of personal preferences. Pick one real task: finding a service, checking an offer or making an enquiry. Start on the page that visitor lands on, not necessarily the homepage.
Write down what you expect to learn and the next step you need. If the offer is unclear, quote the confusing sentence and propose a precise alternative instead of writing ‘improve the copy’.
Minutes 2–4: follow the mobile journey
On a phone, open the menu, find a service and reach contact. Check whether text fits the screen and sticky elements cover buttons. Then use a desktop keyboard to move through the main controls.
A screenshot is useful evidence of a layout problem. Include the viewport width and steps to reproduce it. ‘Does not work on mobile’ alone does not give someone enough information to fix it.
- Do links deliver what their labels promise?
- Can you see focus without using a mouse?
- Can you close the menu and return to the content?
Minutes 4–6: check speed, not a perfect score
Run PageSpeed Insights for the selected URL. Distinguish field data from real users and a laboratory test. Missing field data does not mean the site is fast or slow: it means the report lacks a sufficient sample.
Core Web Vitals track main-content loading (LCP), interaction responsiveness (INP) and layout stability (CLS). One lab score does not represent every visitor’s experience. Record an obvious issue, such as an oversized hero image, and retest after changing it.
Minutes 6–8: test contact end to end
A visible button is not the same as working contact. Check phone numbers, field labels and error messages. Send a test message only with the owner’s agreement, then confirm it actually arrived.
Do not enter sensitive information for a test. If the form provides no clear confirmation or the owner never receives the message, fixing that takes priority over polishing button shadows.
Minutes 8–10: turn findings into an order of work
Keep the three most important findings. For each, record: URL → problem → evidence → proposed change → verification. Fix task blockers first, understanding second and visual details last.
Example note: ‘Contact page at 375 px: the menu covers the button. Reduce its height or allow scrolling. Verify by opening the menu and reaching contact without overlap.’ That is an actionable, testable task.
- Now: broken contact or inaccessible content.
- Next: unclear offers, navigation and readability.
- Later: cosmetic improvements that do not block the task.
What this quick review cannot confirm
Indexing, canonicals, redirects, security and full accessibility need separate investigation. Use Search Console with the owner’s access to inspect indexing; simply viewing a page cannot confirm its Google index status.
The same caution applies to AI search results. Google says AI Overviews and AI Mode have no special additional technical requirements. Useful text, crawlability and accurate information remain the foundation; no audit guarantees a citation or ranking.
Sources & further reading
Send your website and get 3 practical improvements
If you want a fast, actionable next step, send your URL and we will point out what can improve mobile usability, trust, and enquiries first.
