Guide
What is a UX audit?
A plain guide to UX audits: what one is, what it looks at, how it runs step by step, and how to tell if your product needs one.
5.0 from 33 Upwork reviews · Top Rated · 100% Job Success
The short answer
A UX audit is a review of a product or website, screen by screen, to find where people get confused, slow down or give up. The result is a list of problems, each shown on a screenshot, ranked by how much it hurts users and how much work it takes to fix.
An audit looks at what already exists. It does not change the product. It tells you what to fix first, so the next design or development work goes where it matters.
What a UX audit is not
It is not a usability test. In a usability test you watch real users try tasks. In an audit, an experienced designer reviews the product against known usability principles. Audits are faster and cost less. Tests show you real behaviour. They answer different questions, and many teams do an audit first and test later.
It is not an automated report. Tools can check speed, broken links and some accessibility rules. They cannot tell you that a button label is confusing or that the main action is in the wrong place. That needs a person.
It is not a redesign. An audit gives you the plan. Fixing the problems is a separate step.
What a UX audit checks
An audit usually follows the journeys that matter most to the business: sign-up, onboarding, the main task people come to do, and checkout or upgrade. On every screen in those journeys, the questions are the same.
- Purpose: is it clear what this screen is for and what to do next?
- Copy: are labels and messages plain and specific, or full of words only the team understands?
- Layout: is the main action where people look first? Is anything competing with it?
- Navigation: can people tell where they are and how to get back?
- Feedback: after a click, does the product show what happened?
- Errors: do error messages explain what went wrong and how to fix it?
- Empty states: what does a new user see before there is any data?
- Mobile: does the screen still work on a phone?
- Accessibility basics: is text readable, is colour contrast enough, are touch targets big enough?
Many of these questions come from Jakob Nielsen's 10 usability heuristics, published in 1994 and still the most widely used checklist in the field. They include visibility of system status, consistency and standards, error prevention, and recognition rather than recall.
How a UX audit runs, step by step
- Agree the scope. Decide which journeys and screens are in the review, and what worries you most: a sign-up that loses people, a dashboard nobody uses, a site with visits but no enquiries.
- Get access. The auditor needs the product or site, a test account if there is a login, and ideally any analytics, support tickets or user feedback you already have. The extras are not required, but they point to problems faster.
- Review every screen as a new user. The auditor goes through each journey step by step and notes what is unclear, what takes too many steps, and where the layout, the copy or the feedback lets people down.
- Rank the findings. Every issue is rated by impact on users and by effort to fix. Quick wins come first.
- Write it up. Each finding goes on an annotated screenshot, in plain words, with a suggested fix.
- Walk through it together. A call to go through the findings and answer questions, so the team agrees on what to do.
What you get at the end
- Every issue on an annotated screenshot, so anyone can see where it is.
- Findings ranked by impact and effort.
- Quick wins your developers can ship within days.
- Suggestions for bigger changes.
- A walkthrough call.
If an audit you are offered is missing any of these, ask why.
When a product needs a UX audit
- Traffic or sign-ups look fine, but people leave before they pay or activate.
- Something feels off, but nobody can say exactly what.
- You are planning a redesign and want to know what is actually broken first.
- The team argues about design changes without a shared view of the problems.
If you already know exactly what is wrong, you can skip the audit and go straight to design.
Can you audit your own product?
You can, and the checklist above is a good start. The hard part is distance. Teams know their product too well to see it as a new user does, and they tend to explain problems away. An outside reviewer has no history with the product, which is most of the value.
How long a UX audit takes and what it costs
Both depend on how many screens are in scope. One key flow is a small job. A whole product with several user roles is a large one. With me, the timeline and one fixed price are agreed in writing before work starts. The UX audit cost guide shows my real price ranges by size, from $500.
Getting a UX audit
I run UX audits for SaaS products, apps and websites. Read the UX audit services page for what is included and how to start. When you are ready for the fixes, I can design them as a SaaS dashboard redesign, mobile app design or website design.
FAQ
Questions about UX audits.
What is a UX audit?
A screen-by-screen review of a product or website that finds where users get stuck and ranks what to fix first, by impact and effort.
What is the difference between a UX audit and usability testing?
An audit is an expert review against usability principles. Usability testing watches real users try tasks. Audits are faster and cost less; tests show real behaviour.
Is a UX audit the same as a heuristic evaluation?
A heuristic evaluation is one method an audit uses: checking screens against rules like Nielsen's 10 heuristics. A full audit also looks at the business journeys, copy, mobile layout and any data you share.
How long does a UX audit take?
A small audit of one flow, like sign-up, takes 3 to 5 working days. Sign-up plus the main screens takes 1 to 2 weeks, and a whole product 2 to 3 weeks. The exact timeline is agreed in writing before we start. It also depends on how fast I get access and feedback.
How much does a UX audit cost?
With me it starts from $500. See the UX audit cost guide for ranges by size.
Do I need analytics for a UX audit?
No. Analytics, support tickets and feedback help find problems faster, but the review works without them.
What happens after the audit?
Your team can fix the issues using the ranked list, or I can design the fixes as a separate project.
Want a fixed price for your product?
Book a free 30 minute call. You leave with 3 written fixes, even if we don’t work together.