A useful website audit connects technical findings to the tasks customers need to complete. Start with the pages that explain your services, attract enquiries or take orders, then record the URL, the observed issue, its effect on users and a repeatable acceptance check.
This is a practical inspection guide, not a statistical study or a report of measured customer results. The priorities below should be assessed against your own website, analytics and business requirements.
1. Check the complete mobile journey
Open the homepage, a service or product page and the enquiry or checkout journey at common phone widths. Important information should remain available without horizontal page scrolling. Check headings, navigation, image crops and any fixed contact controls.
- Open and close the mobile menu using touch and a keyboard.
- Check that buttons have clear labels and can be selected without hitting nearby controls.
- Read the main service explanation and complete the enquiry form on a phone.
- Check that a fixed header does not cover headings reached through section links.
2. Separate performance measurements from assumptions
Use a browser performance trace or Lighthouse to investigate slow pages, and compare with real-user Core Web Vitals data when it is available. A lab score is a diagnostic result, not a direct ranking score or a promised conversion result.
- Identify the main visible image and check its dimensions, format and loading priority.
- Check that images reserve space before loading and that fonts do not create disruptive shifts.
- Review scripts and embeds that block interaction or load before they are needed.
- Record the device, network conditions, page and date so a later test can be compared fairly.
3. Verify search discovery and page purpose
Each important page needs a clear purpose, a descriptive title, useful visible content and crawlable links. Check the actual HTTP response and rendered page rather than relying only on a plugin status indicator.
- Confirm important pages return 200 and removed pages return an appropriate status or relevant redirect.
- Check unique titles, descriptions, a clear main heading and an accurate canonical URL.
- Compare the sitemap with the pages that should be indexed; exclude draft or duplicate URLs.
- Validate structured data against visible facts and avoid unsupported reviews, prices or results.
- Use Search Console to inspect indexing and Google-selected canonicals after publication.
4. Test enquiry and checkout paths
A visible contact form is only one part of a working enquiry journey. Test required fields, clear error messages, recovery after a failed request and the confirmation shown after success. Use a controlled test inbox and an agreed test window before sending real submissions.
- Confirm the correct service or product is included in the enquiry.
- Check phone, email and WhatsApp destinations against official business details.
- Verify that repeated clicks do not create duplicate submissions.
- For ecommerce, test supported payment methods and order notifications in the payment provider test environment.
5. Measure useful outcomes
Analytics should answer business questions: which pages lead to enquiries, where users leave a journey and whether a successful form submission is recorded once. Treat a button click and a completed enquiry as different events.
- Confirm the intended analytics property and tag configuration.
- Keep development and preview activity out of production reporting.
- Check that events contain useful context without sending form messages or personal details.
- Document any gaps before interpreting changes in traffic or enquiry counts.
6. Review maintenance and access responsibilities
Check HTTPS, supported software versions, account ownership and the availability of tested backups. An automated security scan can identify issues to investigate, but it does not establish that a website is secure.
- List who controls the domain, hosting, CMS and third-party accounts.
- Confirm update, backup and restoration responsibilities.
- Check that administrative access is limited to the people who need it.
- Prioritise fixes by user impact, exposure, evidence and implementation effort.
Turn findings into a delivery plan
For each finding, keep the affected URL, reproduction steps, evidence, proposed change, owner and acceptance check in one record. Separate confirmed defects from improvement ideas. Re-test changed journeys and document any remaining limitations.
Digitronix provides technical SEO audits and implementation and website maintenance. Share your website and requirements so the pages, access, deliverables and quotation can be agreed before work begins.
Further reading
See the Google SEO Starter Guide and Core Web Vitals guidance for the underlying search and performance guidance.
