What should a UX audit reveal?
A UX audit is not a verdict on whether a website is “beautiful”. It checks whether a real person can understand the offer, find information, complete an action and know what happens next. You can run one before a redesign—or without replacing the whole site.
This checklist follows four stages: understanding, navigation, completion and trust. For each finding, record the page, the user task that breaks and the smallest change that could test your hypothesis.
12 checks to run
1. The first-screen message
Can a new visitor understand who the business helps, what it helps with and what to do next without reading a full page?
2. The primary action
Is there one clear CTA on the key page, using the real action—such as booking a call or sending a question—rather than a vague “Submit”?
3. Navigation and structure
Can someone reach services, pricing, FAQs and contact details without guessing where they are?
4. Finding answers
Choose three questions customers actually ask. Count the steps needed to find an answer and check whether it appears where a visitor would expect it.
5. Mobile use
Test on a real phone: menu, type size, tap targets, horizontal scrolling, forms and click-to-call links. Responsive does not automatically mean usable.
6. The contact form
Ask only for information needed at the first step. Check persistent labels, suitable field types, preserved input and specific error messages.
7. The post-submission path
Send a real enquiry. Is receipt confirmed? Does it reach the right person? Is the next step clear—only if that is the process the business actually follows?
8. Basic accessibility
Use the site with a keyboard and check focus, heading structure, contrast, alternative text and clear field names. W3C’s WCAG 2.2 provides testable technical criteria; it does not replace user testing.
9. Speed and stability
Check real-user data, not only a lab score. Google describes page experience as a combination of performance, security, mobile usability and clarity—not one score.
10. Trust and risk reduction
Is it clear who is behind the business, what the process looks like and where a visitor can get answers? Do not add logos, certifications or results without a real basis.
11. Languages and direction
For a multilingual site, test every version separately: wording, RTL, menus, forms, links, titles and contact paths. Partial translation is a UX problem, not only a language problem.
12. Measurement
Connect each action to a goal: CTA views, form starts, errors, submissions, calls or bookings. Traffic alone does not show where the journey breaks.
Turn the audit into a work plan
- Choose two or three important journeys and test them end to end.
- Separate content, interface, technical and measurement problems.
- Rank findings by impact on the task, frequency and risk—not by how visible they are to a designer.
- Test a small measurable change before deciding on a full redesign.
Compare the findings with EzraTech’s checklist for enquiry-generating websites, brief questions before development and guide to when a redesign is justified.
The takeaway
A useful UX audit does not produce an endless list of opinions. It shows where a person gets stuck, the likely reason and what can be changed and tested. Fix a local problem locally. Consider a redesign only when several important journeys fail together.