FreeScore your product against our 48-point UX audit checklist48-point UX audit checklist
Fixed scopeTwo weeksPrioritised fix list

Find the friction before it costs you users

A UX audit finds where people get stuck in your product or website, explains why, and ranks every fix by impact against effort. You get a backlog your team can act on, not a report that gets filed.

What is a UX audit?

A UX audit is a structured evaluation of a digital product or website that identifies usability problems, interaction friction, accessibility issues and conversion blockers, and ranks the fixes by impact and effort.

Ours combines three kinds of evidence: a heuristic and task-based review of your core journeys, your analytics and session data where you have them, and a WCAG 2.1 AA accessibility pass. It applies to SaaS products, mobile apps and marketing websites alike.

The output that matters is the ranking. Most audits hand over a long list of observations with no priorities; ours scores every finding so the work sorts itself into quick wins and structural changes. To run a first pass yourself, start with our 48-point UX audit checklist.

What problems can a UX audit reveal?

The symptoms usually show up in your numbers first. An audit connects each one to the specific screens and decisions causing it.

Onboarding drop-off

Sign-ups that never reach a first meaningful action, usually because the first session asks for effort before it shows value.

Features nobody can find

Navigation and labels that make sense to the team that built them and hide important capability from everyone else.

Leaks on high-intent pages

Pricing, sign-up, checkout or demo-request pages where people arrive ready to act and leave without acting.

Forms and error states

Validation that fires too late, messages that blame the user, and dead ends with no way to recover.

Inconsistency that reads as risk

Five button styles and three date formats. In B2B and fintech especially, visual inconsistency erodes trust.

Accessibility gaps

Contrast, keyboard and screen-reader problems that exclude real users and increasingly block enterprise procurement.

When should you conduct a UX audit?

An audit is the cheapest way to replace opinions with evidence. These are the situations where it pays back fastest.

Traffic is fine, conversion isn't

Acquisition is working and the funnel still leaks. You suspect the problem is on the page rather than in the campaign, but nobody can point at the step that loses people.

Support keeps answering the same question

The same few tickets arrive every week. That is a design problem being absorbed by people, and it is measurable.

Everyone has an opinion, nobody has evidence

Design is being decided by whoever argues hardest. An external audit gives the team a shared, ranked list to work from.

You're about to fund a redesign

Before committing to a rebuild, it is worth knowing which problems actually cost money. Often a targeted fix list captures most of the value for far less.

What we evaluate

Every audit covers the same eleven dimensions across the journeys agreed at scoping, so findings are comparable and nothing important is skipped.

  • Navigation: can people find what they came for without guessing?
  • Information architecture: are things grouped and named the way users think?
  • Usability: can core tasks be completed without help?
  • Accessibility: WCAG 2.1 AA contrast, keyboard, focus and screen-reader checks
  • Interaction: do controls behave predictably and give feedback?
  • Content clarity: does the copy explain, or does it assume knowledge?
  • Conversion: where do high-intent visitors drop, and why?
  • Onboarding: how long until a new user reaches first value?
  • Error states: can people recover when something goes wrong?
  • Visual hierarchy: does the most important thing look most important?
  • Consistency: do the same things look and behave the same everywhere?

Our UX audit methodology

Five lenses, applied to the same journeys. Each catches problems the others miss.

  1. Heuristic evaluation

    An expert walk-through of each journey against established usability principles, recording every point of friction with a screenshot and an explanation.

  2. Competitive analysis

    How comparable products solve the same task, so we know which conventions your users already carry and when breaking them costs adoption.

  3. User journey analysis

    The end-to-end path a real user takes, including the moments outside your product, mapped against where analytics show people stalling.

  4. Accessibility review

    A WCAG 2.1 AA pass over the audited journeys. Accessibility and usability problems overlap heavily, so they are ranked together.

  5. Conversion analysis

    Where you have GA4, Hotjar, Clarity or similar, we tie observed friction to actual drop-off, so a finding is backed by a number rather than an assertion.

What you receive

The deliverable is designed to go straight into your backlog.

Audit report

Every finding with a screenshot, the journey it sits in, and a plain explanation of why it hurts.

Issue prioritisation

Each issue scored on user impact, business impact and implementation effort, so the list sorts itself.

Severity classification

Blocking, major and minor, so engineering can see at a glance what cannot wait.

Annotated screens

The problem shown in place, not described in prose that someone has to interpret.

Recommendations

What to do instead, with wireframes or visual direction for the highest-impact fixes.

Quick wins

Changes that are cheap to ship and worth shipping this sprint.

Strategic recommendations

The structural problems that a sprint cannot fix, framed so you can decide whether a redesign is warranted.

Implementation roadmap

A suggested sequence agreed in a live walkthrough with your product and engineering team.

How long does a UX audit take?

Two weeks from kickoff to walkthrough. Kickoff is normally within 48 hours of signature, and we can compress to one week when there is a genuine deadline.

  1. Scoping (days 1 to 2)

    We agree which journeys are in scope and which metric matters most. You get a written scope with a fixed price before work starts.

  2. Review (days 3 to 7)

    Heuristic evaluation, task walkthroughs, analytics review and the accessibility pass across the agreed journeys.

  3. Prioritisation (days 8 to 10)

    Every issue scored and ranked. This is the step most audits skip, and the one that makes the output usable.

  4. Handover (days 11 to 14)

    Written report, annotated recommendations and a live walkthrough where your team argues with the findings and agrees what goes into the next sprint.

How much does a UX audit cost?

A UX audit is quoted as a fixed fee against a written scope, agreed before any work starts, so there is no hourly drift. The fee depends on how much of the product is in scope, not on a day rate.

What moves the price: the number of journeys audited; how many platforms are involved (web, iOS, Android); whether analytics and session data are available; how deep the accessibility review needs to go; whether you want recommendations as written guidance or as wireframes for the top fixes; and whether the audit includes a round of usability testing with real users.

Because it is fixed-scope, an audit is the lowest-risk way to work with us for the first time, and the fee is credited against a subsequent design engagement if you continue. For broader context on design pricing, see our guide to UI/UX design pricing in India.

UX audit vs UX research vs usability testing

Three ways to find out what is wrong. They answer different questions, and the cheapest one is often enough.

UX auditUX researchUsability testing
What it isExpert evaluation of your product against usability principles and your own dataEmpirical study of actual users: interviews, observation, journey mappingWatching people attempt specific tasks on your product or a prototype
Tells youWhat is likely wrong, and what to fix firstWhat is actually happening, and whyWhether particular tasks succeed, and where they fail
Best whenYou need a prioritised fix list fast, or before deciding on a redesignThe team is not the user, or a big decision rests on an untested assumptionYou want to validate a flow or a redesign before building it
Typical lengthAbout two weeksTwo to four weeks, depending on recruitmentOne to two weeks for a focused round
OutputRanked issue register, annotated screens, roadmapPrioritised findings with evidence and recordingsTask success, observed problems, timestamped recordings

Frequently asked questions

What is a UX audit?

A UX audit is a structured evaluation of a digital product or website that identifies usability problems, interaction friction, accessibility issues and conversion blockers, and ranks the fixes by impact and effort. Ours combines a heuristic and task-based review, analytics and session evidence, and an accessibility check.

Is a UX audit the same as a design audit?

Mostly, yes. "Design audit" is sometimes used for a purely visual review of consistency and brand. A UX audit goes further: it evaluates whether people can complete tasks, where they drop off and why, and it includes accessibility. Ours covers visual consistency as one of eleven dimensions.

How much does a UX audit cost?

A UX audit is quoted as a fixed fee against an agreed written scope, so there is no hourly drift. The price depends on the number of journeys, the platforms involved, whether analytics are available, the depth of accessibility review and whether you want wireframes for the top fixes. The fee is credited against a subsequent design engagement if you continue.

What do I actually receive at the end?

A prioritised issue register, with every finding scored on user impact, business impact and implementation effort, plus annotated recommendations with visual direction for the highest-impact fixes and a live walkthrough with your team. It is designed to go straight into your backlog.

How long does a UX audit take?

Two weeks from kickoff to walkthrough is standard: two days scoping, five days reviewing, three days prioritising, and the rest writing up and presenting. We can compress to one week when there is a real deadline, though the prioritisation stage is the one worth protecting.

How is a paid audit different from a free one an agency offers?

A free audit is a sales document; its purpose is to find enough problems to justify a proposal. A paid, fixed-scope audit is a deliverable in its own right, deep enough to be useful whether or not you hire us for the fixes.

Do you need access to our analytics?

It makes the audit substantially better but is not required. With GA4, Hotjar, Clarity or similar we can tie observed friction to actual drop-off numbers. Without it we still run heuristic and task-based evaluation; we just cannot quantify the cost of each issue as precisely.

Will you also fix the problems you find?

If you want us to. Many clients run the audit as a standalone diagnostic and hand the list to their own team, and the report is written to support that. Others continue into a design engagement, in which case the audit fee is credited.

Can you audit a product that hasn't launched?

Yes, though the method changes. Without live users or analytics we rely on heuristic evaluation, comparison against category conventions and task walkthroughs with people matching your target profile. Pre-launch fixes are cheaper because nothing is locked in yet.

Should we start with a UX audit or UX research?

If budget only allows one, start with the audit: it is faster and often sufficient. Choose research when the team is not the user, or when an expensive decision rests on an assumption nobody has tested. See our UX research service.

Request a UX audit

Tell us what isn't working. In a 30-minute call we agree which journeys are worth auditing, and you get a fixed written scope before any work starts.

Last updated 4 October 2026