A UX audit checklist before you rebuild.

A redesign is often the most expensive way to avoid naming the real problem. Before you rebuild the whole thing, run a focused UX audit. You may find that the issue is not "the website looks old." It may be one unclear promise, one buried action, one form that asks too much, or one mobile step that quietly breaks trust.

This checklist is not a substitute for a full audit, but it is enough to stop you walking into a rebuild blind.

Start with the journey

Pick one primary journey. Not the whole product. Not every page. One route a user takes to create value: land on the site, understand the offer, enquire; open the app, choose a plan, pay; create an account, complete setup, reach the first useful moment.

Then walk it slowly and write down where the user has to guess.

• Entry: does the first screen make the next step obvious?
• Context: does the user know where they are and what just happened?
• Decision: is the choice easy, or are too many options competing?
• Action: is there one clear primary action?
• Recovery: what happens when the user cannot complete the happy path?

Check the promise

Most conversion problems start before the button. The user arrives with a question: "Is this for me, and should I trust it?" If the page answers that question slowly, vaguely or with too much decoration, the interface is already leaking.

Look at the first meaningful screen and ask:

• Can a new visitor explain what this does in one sentence?
• Is the primary benefit concrete, or just a broad claim?
• Does the page say who it is for?
• Is the proof close to the decision point?
• Is the CTA written as an action, not a slogan?

Check friction in the action

Forms, booking flows, checkout flows and sign-up steps are where polite designs become expensive. Every field asks for effort. Every unclear label asks for trust. Every unexpected step asks for patience.

Audit the action step with a simple rule: if the product needs the information, ask clearly; if it does not need it yet, remove it.

• Fields: can any field be delayed until after the first commitment?
• Labels: are they specific enough without placeholder text?
• Validation: does the user learn what went wrong and how to fix it?
• Progress: can the user tell how much is left?
• Confirmation: is there a clear "you are done" state?

Check mobile as the real version

Do not audit the desktop first and call mobile "responsive" at the end. For many products, mobile is the experience. It has less space, less patience and more physical friction.

Run the same journey on a phone width and look for the practical failures:

• Text that wraps into awkward fragments.
• Buttons too low, too small or too close together.
• Sticky elements covering important content.
• Forms that fight the keyboard.
• Cards that look neat on desktop but become a long, shapeless scroll.

Check accessibility basics

Accessibility is not a separate moral appendix after conversion work. It is part of whether the interface can be used clearly. Start with the basics because they catch a surprising amount of product friction.

• Can you tab through the journey in a sensible order?
• Is focus visible when using a keyboard?
• Does body text have enough contrast against the background?
• Are icon-only controls labelled or obvious from context?
• Do errors describe the fix, not just the failure?

Rank issues by severity

A useful audit does not hand over a pile of opinions. It ranks fixes so the team knows what to do first.

1. P1 - critical. Blocks the main journey, hides the action, breaks trust, or causes users to abandon.
2. P2 - important. Adds friction or uncertainty, but the user can still complete the task.
3. P3 - polish. Worth improving after the core journey is clear.

What a good audit gives you

A good audit should leave you with a fix list, not a feeling. At minimum, you want:

• the journey being audited;
• screenshots or references showing where each issue lives;
• severity for each finding;
• the reason it matters;
• a specific recommended fix;
• quick wins separated from bigger redesign work.

When to bring in a senior eye

Run this pass yourself first. It will catch obvious friction and sharpen your thinking. Bring in a senior UX audit when the stakes are higher: paid traffic is going to the page, users are dropping in a flow, a redesign is about to start, or the team disagrees about what is actually wrong.

The goal is simple: fix what is costing users first. Then redesign from evidence, not anxiety.