UX audit checklist: find friction before redesigning

The short answer

Audit the highest-value journeys first. Review entry context, information architecture, navigation, content hierarchy, interaction states, forms, mobile behaviour, accessibility basics, trust, performance and measurement. Separate observed evidence from hypotheses, then prioritise findings by user/business impact, confidence and implementation effort.

Start with the task, not the screen

Before reviewing UI details, define the following. A beautiful screen can still be the wrong solution to the wrong task.

• Who is the user?
• What are they trying to accomplish?
• What does success look like?
• What information do they need?
• What does the business need from the journey?
• Which devices/channels matter?
• What evidence is available?

1. Entry and orientation

Check whether a visitor arriving on an important page can quickly understand where they are, what the product/service/page is about, who it is for, what they can do next, and whether the page matches the promise that brought them there.

Campaign-message mismatch is a UX problem even when the page itself is polished.

2. Information architecture and navigation

The goal is not minimum clicks. It is clear choices.

• Labels use customer language rather than internal organisation terms
• Important categories/services are discoverable
• Navigation depth is proportionate
• Breadcrumbs are useful where hierarchy matters
• Search exists where users reasonably need it
• Related content is connected
• Mobile navigation does not hide critical choices

3. Content hierarchy

Scan the page without reading every sentence. Can you identify the primary message, major sections, proof, important constraints and the next action?

Headings should describe the information beneath them rather than use vague slogans everywhere.

4. Interaction states and feedback

Every interactive element has more than one state. A cart icon that gives no feedback after adding an item is a small example of a larger principle: the interface should confirm what just happened.

• Default
• Hover/focus
• Selected
• Loading
• Success
• Error
• Disabled
• Empty
• Unavailable/sold-out where relevant

5. Forms

For OTP or multi-step forms, each state needs explicit feedback.

• Only necessary fields are requested
• Labels remain understandable
• Validation appears at the right time
• Errors explain how to recover
• Required/optional states are clear
• Keyboard/mobile input types are appropriate
• Submission/loading is visible
• Success is unambiguous
• Analytics measures genuine completion rather than only the submit click

6. Mobile behaviour

Do not treat mobile as a scaled-down desktop screenshot. A sticky CTA that covers product information is not an optimisation.

• Tap targets
• Sticky elements
• Content order
• Navigation
• Modals
• Filters/sort
• Tables
• Long forms
• Image/media behaviour
• Keyboard overlap
• Horizontal overflow
• CTA visibility without obstruction

7. Ecommerce decision support

For commerce journeys, check whether customers can understand product differences, variants, availability, price/discount, size/dimensions, delivery, returns, trust and cart status.

Review both product and collection pages. Discovery friction often begins before the PDP.

8. Trust and reassurance

Trust is contextual. Avoid adding badges that do not mean anything to the user.

• Clear contact/company information
• Policies
• Credible project/client evidence
• Secure/payment expectations
• Transparent pricing or scoping where appropriate
• Real testimonials/reviews when substantiated
• Author/expert identity for advice content

9. Accessibility basics

A UX audit should at minimum notice obvious barriers. A heuristic audit is not the same as a formal accessibility conformance audit.

• Insufficient contrast
• Missing keyboard focus
• Unlabeled controls
• Poor heading hierarchy
• Images without meaningful alternatives where needed
• Interactions that depend only on colour
• Motion without appropriate consideration
• Forms with inaccessible errors

10. Performance as experience

Slow interaction, layout movement and heavy scripts affect usability. Performance findings should be validated with appropriate technical evidence rather than judged only by feel.

• Important content appears promptly
• Media is appropriately handled
• Third-party scripts/apps justify their cost
• Interaction does not feel blocked
• Layout remains stable enough to use confidently

11. Measurement and evidence

No single source explains the entire journey.

• GA4 journey/event data
• Search Console landing/query context
• Support questions
• CRM outcomes
• Session recordings/heatmaps where appropriate
• Usability observations
• Customer feedback
• Technical crawl/performance evidence

Turn findings into priorities

For each finding, record: Problem — what is happening? Evidence — what supports it? Impact — who/what is affected? Confidence — observation or hypothesis? Recommendation — what should change? Effort — approximate implementation complexity? Validation — how will we know?

This is more useful than a deck containing 100 screenshots labelled “improve UI.”

Redesign or optimise?

Recommend a redesign when the underlying architecture, product model, brand or system no longer supports the task. Recommend focused optimisation when the core structure works and friction can be isolated.

The audit should help make that decision rather than assume the answer.