What Does a UX Audit Cost, and What Should It Find?
By CodexierPublished 5 min read
A UX audit is a structured review of how well a website or app lets people do what they came for. Prices vary widely because the word covers everything from a designer's afternoon with a checklist to weeks of user research. This guide connects price to method, lists the deliverables that justify the fee, shows how to estimate what the fixes are worth before you buy, and is honest about when an audit is the wrong purchase.
Expert review vs user research
The two methods find different things. An expert review is fast and catches known problems: unclear calls to action, forms that ask too much, navigation that hides the important pages, mobile layouts that break. It leans on the reviewer's experience and on your analytics, which show where people drop. User research, whether moderated sessions or unmoderated recordings, reveals the misunderstandings an expert cannot see: the word on a button that means something else to customers, the step people do not realise exists. Most companies get the most value from a review first, then targeted testing of the flows the review flagged. Testing a handful of real users on the flagged flows is the second step.
What drives the price
| Driver | Cheaper | More expensive |
|---|---|---|
| Scope | One flow, such as enquiry or checkout | Whole site or app across roles |
| Devices | Mobile and desktop of the main site | Multiple apps, tablets, assistive technology |
| Evidence | Heuristics plus your analytics | Session recordings, surveys, moderated tests |
| Output | Prioritised list with fixes | Redesigned wireframes and prototypes |
| Follow-up | One readout meeting | Implementation support and re-measurement |
When comparing quotes, ask which of these each one includes. A low price for a whole-site audit usually means a checklist run without analytics access, which produces generic advice. A high price should come with evidence from real usage and wireframes for the biggest fixes. Neither is wrong; they are different products, and the quote should say which.
Deliverables worth paying for
The report is the product, so judge suppliers on what it contains. A useful audit gives you a short list of findings ranked by expected impact and effort, each with a screenshot, the evidence behind it, a concrete proposed change and a way to measure whether the change worked. It should be readable by the person who will implement it and by the person who pays for that.
- A ranked list of at most fifteen to twenty findings; a hundred unranked issues is noise.
- Evidence per finding: analytics numbers, a recording, or the principle violated.
- A proposed fix specific enough to estimate, with quick wins separated from projects.
- The metric each fix should move and its current value, so success can be checked.
- A readout meeting where you can push back and ask what to do first.
Estimating the value of fixes
Before buying, put a rough number on what better UX would be worth. Take the monthly visitors to the flow in question, the share who complete it today, and the value of a completion, whether an order, a booking or a lead that closes at a known rate. A modest improvement in the completion share, multiplied by visitors and value, gives the monthly gain; compare that with the audit fee plus the cost of implementing the fixes. If the number is a small fraction of the fee even under optimistic assumptions, the audit is premature and traffic is the problem. If it is a multiple, the audit is cheap. The UX audit and conversion improvement service is built around exactly this calculation; the price is on our pricing page.
When an audit is not needed
You do not need a UX audit when you already know what is wrong and just need it fixed; spend the money on the fix. You do not need one for a site with very little traffic, because there is nothing to measure and the money should go to reaching people. You do not need one right before a full redesign, where the findings would apply to screens that are about to disappear; audit the new design as a prototype instead. And an audit will not rescue a product whose problem is the offer or the price rather than the interface.
If you have steady traffic, a conversion rate that disappoints, and no clear idea why, an audit is the cheapest way to find out. Book a short call with your analytics open and we will say within fifteen minutes whether an audit, user testing or a plain fix is the right purchase.
Frequently asked questions
How long does a UX audit take?
An expert review of one or two flows takes about a week from access to readout. Adding user testing extends that by the time to recruit and run sessions, typically two to three weeks in total.
Does the audit include implementing the fixes?
Usually not; the audit produces the prioritised list and proposed changes. Implementation is quoted separately, either by us or by your own team. Ask for findings specific enough that any competent developer can estimate them.
Do we need to give the auditor access to our analytics?
Yes, read access to your analytics and, if you have them, session recordings. Without data the audit falls back on general principles, which are useful but cannot tell you where your visitors actually leave.
Traffic is fine but conversions are not?
Fifteen minutes with a designer: open your analytics, show us the flow that disappoints, and we tell you whether an audit will pay for itself and what it would cover.
Book a free 15-minute call