UX Audit Guide: Find What’s Driving Customers Away

When a website no longer converts as well as it did, customers are struggling, or the experience has simply fallen behind the business’s needs, a redesign can create a real opportunity for improvement. A UX audit helps make sure that opportunity is used well, revealing where the current experience breaks down, who it affects and where a redesign will have the biggest impact.

A UX audit done right will bring together data, customer behaviour, accessibility issues and expert insight to show where the biggest opportunities lie. This gives design, development and marketing teams a clear set of priorities, so the redesign is based on real customer needs rather than assumptions.

What is a UX audit?

A UX audit is a review of your website, app or digital service to understand how well it works for the people using it. It looks at how easily customers can find what they need, complete important tasks, and navigate the pages, while identifying anything that could be getting in their way.

An audit can cover everything from navigation and content to forms, search, accessibility, mobile experience, performance and conversions. The goal isn’t just to point out what’s good or bad. It’s to understand what could be improved, why it matters and which changes should be prioritised as part of a redesign.

What a UX audit is not

A UX audit helps you make better decisions about your website, but it’s important to understand what it can and can’t tell you.

• It’s not based on personal taste or what one person thinks looks good.
• It can’t guarantee that every recommended change will increase conversions.
• It’s not a full accessibility audit unless WCAG testing is specifically included.
• It doesn’t replace ongoing user research, testing and measurement.
• It doesn’t always mean rebuilding everything. An audit can show what should stay, what needs improving and where a redesign could have the biggest impact.

A good UX audit reduces the guesswork. Some findings will highlight clear problems that need fixing, while others will identify opportunities worth exploring or testing.

Making that distinction clear helps everyone understand what needs attention now, what could be improved through a redesign and what needs further testing before a decision is made. That helps avoid mistakes when redesigning your website.

Evidence source	What it can tell you	What to keep in mind
Analytics and funnels	Where customers enter, what they do and where they leave	Shows what is happening, but not always why
Usability testing	How real users complete tasks and where they run into problems	A small group can reveal useful issues, but may not represent every customer
Interviews and support data	What customers need, expect and regularly struggle with	What people say they do can be different from what they actually do
Heuristic review	Where the experience goes against established usability best practices	Expert findings may need further testing to confirm them
Accessibility evaluation	Where people with disabilities may face barriers when using the website	Automated tools can find some issues, but they cannot assess accessibility on their own
Performance data	How quickly pages load and how smoothly the website responds	Test results may not reflect the experience of every real customer
Competitor review	How other websites approach similar customer needs and where there may be opportunities	Just because a competitor does something doesn’t mean it’s the best approach

When should you run a UX audit?

A UX audit is particularly useful before a website redesign. It helps you understand what’s already working, what needs to improve and where the biggest opportunities are, so those insights can shape the new website.

It’s also worth considering a UX audit when:

• Conversions or engagement start to drop and it’s not clear why.
• Customers keep reporting the same problems or asking for help with the same tasks.
• Your audience has changed or grown and the website needs to meet different needs.
• Your website has become more complex as new pages, products or features have been added.
• You’ve recently launched or made major changes and want to understand how well they’re working.
• Your business has gone through an acquisition or integration that has changed the customer experience.

You don’t need to wait until something goes wrong. Regular UX reviews can catch smaller issues before they become bigger problems, especially as new content, campaigns, plugins and features are added over time.

How often you need an audit depends on your website. A busy ecommerce or transactional site may benefit from regular testing and measurement, while a smaller, more stable website may only need a review when significant changes are planned.

Step 1: Define the audit’s objective

Start by deciding what you want the UX audit to help you understand or improve. Think about your most important customers, the tasks they need to complete, the devices they use and the results you want to achieve. For an ecommerce website, that might mean looking at how easily mobile customers can find products and complete checkout. For a B2B website, it could mean understanding how easily potential customers can evaluate your services and get in touch.

It’s also useful to agree on what the audit will and won’t cover before you begin. Note any known problems, upcoming changes and technical limitations, as well as which customer data can be used and who needs to see the findings. This keeps the audit focused on the areas that matter most.

Step 2: Identify users and priority journeys

Next, identify the main groups of people using your website and what they are trying to achieve. Existing customer research, analytics, support conversations and feedback can all help. Focus on people’s needs, goals, knowledge and circumstances rather than creating personas based on details that don’t affect how they use the website.

Then decide which customer journeys the audit should focus on. These might include finding a service, comparing products, completing checkout, submitting an enquiry or managing an account. Remember to consider how people arrive from search engines, emails and advertising too. The customer journey often starts before someone reaches your homepage and continues after they complete an action.

Step 3: Establish a measurement baseline

Before using analytics to make decisions, check that the right things are being measured. Review important events, conversion funnels, campaign tracking and consent settings. It can also help to compare behaviour across mobile and desktop, different markets, and new and returning customers. Look for patterns in where people complete tasks, leave the website, encounter errors or ask for help.

Individual metrics rarely tell the whole story. A customer who visits one page and leaves may have found exactly what they needed, while someone spending a long time on the website may actually be struggling. Use analytics to spot patterns, then combine those findings with other evidence to understand what might be causing them.

Step 4: Review customer feedback and operational evidence

Customer feedback can reveal problems that analytics alone cannot explain. Look through support tickets, live chats, complaints, reviews, sales notes and website feedback for questions or problems that appear regularly. Customer-facing teams can be especially useful because they often know which parts of the website cause confusion or lead people to ask for help.

Consider how serious each problem is as well as how often it happens. A problem that affects fewer people may still be a high priority if it prevents someone from making a payment, completing an important task or accessing the website. Make sure any personal or sensitive customer information is removed from the audit findings.

Step 5: Evaluate information architecture and content

Look at how information is organised and whether the navigation, categories and labels make sense to customers. People should be able to understand where a link will take them and find the information they need without having to understand your internal terminology. Search should also cope with common words, alternative terms and simple spelling mistakes.

Content should be clear, useful and easy to scan. Important information shouldn’t be buried in long paragraphs, and calls to action should appear at the right point in the journey. Pay particular attention to the small pieces of content around forms, errors, prices, consent and confirmation messages, as these can have a big impact on whether customers feel confident about what to do next.

Step 6: Include accessibility properly

Accessibility should be considered throughout the audit rather than treated as an afterthought. Automated tools can help identify some problems, but they cannot tell you whether a website is fully accessible on their own. Human testing and, where possible, research with disabled people provide a much clearer understanding of the experience.

Check areas such as keyboard navigation, focus states, headings, labels, colour contrast, zoom, page reflow, error messages and screen-reader output. Be clear about the level of accessibility testing included in the audit too. A general UX accessibility review is not the same as a full WCAG conformance audit.

Step 7: Assess performance and technical issues

A slow or unreliable website can quickly make a good experience frustrating. Look at how quickly important pages load, how responsive they feel and whether content moves around unexpectedly. Check for broken links, form problems, browser and mobile issues, login problems, payment failures and errors caused by third-party services.

Try to explain technical problems in terms of what they mean for the customer. Instead of simply reporting a technical error or performance score, explain the effect it has. For example, a slow script might mean a product filter appears to do nothing when someone taps it. This makes it much easier for teams to understand why a fix matters and how urgently it should be addressed.

Step 8: Run usability testing

Usability testing shows you what happens when real people try to complete important tasks on your website. Choose participants who reflect the customers you want to understand and give them realistic tasks without telling them exactly how to complete them. Watch what they do, where they hesitate and where they need help.

You don’t need a huge number of participants to uncover useful problems, but a small test group shouldn’t be treated as representative of every customer. Usability testing works best as an ongoing process. Test ideas, make improvements and test again as the website or redesign develops.

Step 9: Review competitors without copying them

Look at how competitors and other good websites handle the same tasks and customer needs. This can help you understand familiar patterns, see different approaches and spot opportunities to improve your own experience. Just remember that something isn’t automatically good UX because a competitor is doing it.

The goal isn’t to make your website look or work exactly like everyone else’s. It’s to understand what customers are likely to expect and where you could make their experience clearer, quicker or easier. A redesign should still feel distinctive to your brand while making it simple for customers to achieve what they came to do.

Turn findings into action

Once the audit is complete, bring those findings together and decide what needs attention first. For each issue, explain who it affects, what they were trying to do, what went wrong and what you recommend changing. Include supporting evidence such as analytics, research, screenshots or testing, while making sure personal customer information is protected.

Not every issue will have the same impact or urgency. The following factors can help you decide what to prioritise:

Priority factor	What to consider
Severity	Does the problem stop customers completing a task, make it difficult or simply cause a small inconvenience?
Reach	How many customers and important journeys are affected?
Business impact	Could the problem affect conversions, costs, customer trust or business risk?
Accessibility	Does the problem prevent or make it harder for some people to use the website?
Confidence	How strong is the evidence that this is a real problem?
Effort	How much design, development, content or operational work will be needed to fix it?
Dependencies	Does anything else need to happen before the improvement can be made?

A simple scoring system can help teams compare priorities, but it shouldn’t be the only factor in deciding what gets fixed. Serious accessibility, security or data issues may need immediate attention even if they don’t have an obvious impact on conversions.

What should a UX audit deliver?

A good UX audit should give your team a clear understanding of what needs to improve and what to do next. Depending on the scope of the audit, this could include:

• A clear summary of the audit’s goals, audiences and areas reviewed
• A summary of the main evidence and insights gathered
• Key customer journeys and conversion funnels
• UX issues ranked by importance, with evidence to explain each finding
• Accessibility and performance issues that need attention
• Recommended improvements, ideas to test and areas that need further research
• A prioritised roadmap showing what should happen first and who needs to be involved
• Measures that can be used to understand whether the changes are working
• A presentation or working session to help the teams responsible for the website understand the findings

Most importantly, the audit needs to be useful after the report has been delivered. Recommendations should become part of the redesign or development plan, with clear priorities and enough information for teams to take action. A long presentation is of little value if nobody knows what to do with it afterwards.

Validate improvements after the audit

Some problems have an obvious solution. If a checkout button is broken, for example, it needs to be fixed. Other recommendations may need to be explored through prototypes, usability testing or experiments before committing to a final design.

Once improvements have been made, check that they have actually solved the original problem. Review accessibility and performance again, make sure analytics are tracking correctly and look at how customer behaviour changes after launch.

It’s also important to look for unexpected effects. Making a form shorter might increase the number of enquiries but reduce their quality. Changing the navigation might make the website easier for new customers while making familiar tasks harder for existing ones. UX improvement is an ongoing process of making changes, measuring the results and continuing to learn.

Common UX audit mistakes

A UX audit is most useful when it stays focused on real customer needs and leads to practical improvements. Some common mistakes can make the findings less useful:

• Trying to audit every page instead of focusing on the most important customers and journeys
• Using analytics to guess why customers behave in a certain way
• Treating heatmaps as an explanation of customer behaviour rather than a useful signal
• Copying competitors without knowing whether their approach actually works
• Making recommendations based on opinions rather than evidence
• Prioritising small visual changes over problems that stop customers completing important tasks
• Making recommendations without considering who will implement them or how much work is involved
• Making changes without checking whether they solved the original problem

Use the audit to improve more than the website

Fhoke is a London-based UK web design agency that has worked with brands around the world. We’ve been around since 2008, while our founders have worked in agencies since 2000. In that time, we’ve seen that UX problems aren’t always caused by the design itself. They can also come from unclear responsibilities, inconsistent page templates or content blocks, limited customer research or a website that has become difficult to manage over time.

As an award-winning WordPress agency, we can use audit findings to improve the foundations of a website, including its templates, blocks, content structure and publishing experience. As a web design agency, we bring together research, UX, accessibility and visual design to make sure those insights become practical improvements as part of a redesign.

A good UX audit gives you a clearer understanding of your website before deciding what comes next. By combining data with real customer behaviour, accessibility testing and expert review, you can see what’s working, what needs to change and where the biggest opportunities lie. Those findings can then shape a more informed redesign, focused on making customer journeys clearer, building trust and delivering better results. And not to mention a way better-looking website at the end.