Testing with just five users uncovers about 85% of usability problems, according to Jakob Nielsen’s research. An audit applies the same efficiency to a live product, quickly finding the biggest problems in data you already own.

A UX audit is a structured review of a website or app that identifies where users struggle, measures the cost of each problem, and ranks the fixes. It combines analytics, expert review against usability heuristics, and accessibility checks. The output is a prioritized list your design and engineering teams can act on.

This guide covers when to audit and which data to pull. It then sets out a step-by-step method, a 50-point UX audit checklist and a scoring model, with a report template at the end.

What is a UX audit, and when should you run one?

What is a UX audit in practice? A two-to-four-week review that combines your analytics with an expert walk-through of key user flows, scored against usability heuristics. Run one before a redesign, after a drop in conversion, or once a year on any product that earns revenue.

Good triggers for an audit:

• Conversion or sign-up rates fall for two months in a row
• Support tickets about “how do I” questions climb
• A redesign is planned and the team needs a baseline
• A new market or audience is about to launch

Audits work best on live products with real usage data. A prototype with no traffic suits usability testing better, because there is nothing to measure yet and every finding would rest on guesses about how people might behave.

Which data sources does a UX audit use?

An audit draws on six data sources, from quantitative analytics to qualitative feedback. Analytics shows where users drop off. Recordings and support tickets show why. Expert review explains the cause in design terms. Accessibility checks catch problems that analytics never shows.

Start with analytics, because it tells you where to look. Pick the three flows that carry the most revenue or drop-off. Focus there.

What are the steps in a UX audit?

Here is how to conduct a UX audit: set a goal, gather data and walk the key flows against a checklist. Then score each finding and report fixes in priority order. Plan about two weeks for three flows with one senior designer.

1. Agree on goals. Pick the business metric the audit should move, such as checkout completion.
2. Collect data. Export funnel data for the last 90 days, plus recent support tickets.
3. Map the flows. Write out each step of the three priority flows.
4. Review each step. Walk through every flow on desktop and mobile with the checklist below.
5. Score findings. Rate each problem for severity and reach.
6. Report and plan. Group fixes into quick wins and larger projects with owners.

The step most teams rush is the first. An audit with no target metric produces a long list of opinions. One tied to checkout completion produces a short list of fixes that move revenue.

Step 4 leans on expert judgment. Our guide to heuristic evaluation covers Nielsen’s 10 heuristics with examples.

Want a second pair of eyes on your key flows?

WebOsmotic reviews your three highest-value flows and hands back a scored, ranked fix list within two weeks.

Request a UX Audit

What goes on a 50-point UX audit checklist?

A 50-point UX audit checklist groups checks into seven areas, from navigation to trust signals. Mark each item pass, partial or fail for every flow you review. Note where each fail occurs. Revenue flows come first.

Navigation and structure

1. Users can tell where they are on every page.
2. Main navigation labels use the words customers use.
3. Search is visible on content-heavy sites.
4. Search handles typos and synonyms.
5. Breadcrumbs or back paths exist on deep pages.
6. The logo returns users to the home page.
7. No key task sits more than three clicks from the start.

Content and messaging

1. Each page states its purpose in the first screen.
2. Headings describe the content below them.
3. Body text avoids internal jargon.
4. Prices and fees appear before checkout.
5. Error and empty states explain what to do next.
6. Help content is reachable from the task it supports.
7. Calls to action say what happens on click.

Forms and input

1. Forms ask only for information the task needs.
2. Labels sit outside the fields and stay visible.
3. Inline validation explains each error in plain words.
4. Required fields are marked clearly.
5. Inputs use the right mobile keyboard type.
6. Users can review entries before submitting.
7. A failed submission keeps the data already entered.

Layout and visual design

1. Visual hierarchy points to the main action.
2. Tap targets are large enough on mobile.
3. Spacing groups related items together.
4. Similar elements look and behave the same everywhere.
5. Important content is visible without horizontal scrolling.
6. Images support the task and carry descriptive alt text.
7. Dark patterns, such as pre-checked add-ons, are absent.

Accessibility

1. Text meets the WCAG contrast ratio of 4.5:1.
2. Every function works with a keyboard alone.
3. Focus is always visible.
4. Form fields have programmatic labels.
5. Headings follow a logical order.
6. Video has captions.
7. Targets meet the WCAG 2.2 minimum of 24 by 24 CSS pixels.
8. Screen readers announce errors and status changes.

Performance

1. Largest Contentful Paint is 2.5 seconds or less.
2. Interaction to Next Paint is 200 milliseconds or less.
3. Layout shift stays under a score of 0.1.
4. Pages stay usable on a slow mobile connection.
5. Loading states appear for waits over one second.
6. Images are sized for the screen that shows them.

Trust and conversion

1. Contact details are easy to find.
2. Security and privacy messages appear where data is asked for.
3. Reviews or case studies sit near decision points.
4. Return, refund or cancellation terms are clear.
5. Guest checkout or a low-commitment first step exists.
6. Confirmation pages say what happens next.
7. Transactional emails match the on-screen flow.
8. Users can reach a human when the interface fails.

The accessibility thresholds come from the W3C’s WCAG 2.2 standard. Performance targets follow Google’s Core Web Vitals. Both matter beyond usability, since accessibility gaps raise ADA lawsuit risk and slow pages lose search visibility.

How do you score and prioritize audit findings?

Score each finding for severity and for reach, then multiply the two. Severity runs from 1 for cosmetic to 4 for blocking. Reach climbs from 1 for a rare edge case to 4 when every user on a key flow hits it. A score of 12 or more goes into the next sprint.

Add a rough effort estimate to each finding. High-scoring items that are cheap to fix become quick wins that ship within weeks, while expensive ones become projects with their own scope and budget.

Track the target metric after each release, because the audit pays off only when the fixes move the number agreed in step 1.

What should a UX audit report include?

A UX audit report should include the goal and the flows reviewed, then each finding with its evidence, score and recommended fix. Keep the summary to one page for leadership. Put the detail in an appendix the design and engineering teams can work through.

Next steps usually split three ways. Quick wins go straight to engineering, and content issues go to marketing. Bigger fixes go to design for testing with users first.

Teams that need help with the redesign work can bring in our UX design services, which take audit findings through research and testing. The guide to user research in UI/UX design covers the research methods that follow an audit.

Have an audit report but no time to act on it?

Our designers turn audit findings into tested screens, starting with the quick wins that move your target metric first.

Talk to Our UX Team

Frequently asked questions

How long does a UX audit take?

Expect 2 weeks for three key flows, or 4 to 6 weeks for a product with many user types and several apps. Writing the report itself usually takes 2 to 3 days of that time, and a walk-through with the product team adds one more meeting.

What is the difference between a UX audit and usability testing?

An audit is an expert review backed by analytics and accessibility checks. Usability testing watches real users try tasks. The two complement each other: an audit finds likely problems cheaply, and testing with 5 users confirms the most important ones before a redesign.

How much does a UX audit cost?

Cost depends on scope and who runs it. In-house, a 2-week audit uses about 80 hours of a senior designer’s time plus analyst support. Agencies price by flow count and depth. Ask for a fixed scope.

Can I use this UX audit checklist for a mobile app?

Yes. The 50 checks apply to apps too, with extra checks for platform conventions such as back navigation on Android and for app store screenshots. Native apps need their own performance targets, so measure launch time and screen load time in place of Core Web Vitals.

How often should a company run a UX audit?

Run a full review once a year on any product that earns revenue, plus a focused audit before each redesign. Fast-growing products benefit from a light quarterly check on the top 3 flows, using the same checklist so results compare over time.