In this Article
- Quick answer: Do you need a website UX audit before a redesign?
- Website UX audit: what it is and what it checks
- A strong UX audit turns findings into priorities
- Three paths after a UX review
- Choose an audit first when the cause is unclear
- Include UX diagnosis in redesign discovery when major change is certain
- Targeted improvements may be enough
- UX audit vs. usability testing, CRO, and accessibility audits
- Questions to ask before commissioning a UX audit
- Use the audit to reduce uncertainty
- UX audit FAQs
Your website feels off.
Leads have slowed. Visitors miss important information. Navigation has become harder to manage after years of adding pages. Or the site still reflects the company you were three years ago.
A redesign can feel like the obvious fix. It can also become an expensive way to solve a problem you haven’t defined yet.
A website UX audit helps you examine how people use the current site before you decide how much needs to change. Your team can use it to find friction, identify likely causes, and set priorities for improvement.
Some redesigns benefit from a standalone UX audit. Other projects can include the same diagnostic work inside the redesign process. In some cases, the findings may point toward targeted improvements instead of a full rebuild.
Quick answer: Do you need a website UX audit before a redesign?
Consider a UX audit before redesigning when your team knows the website has problems but cannot explain their cause or scope.
If a major business, brand, platform, or structural change already requires a new website, include UX research and evaluation in the redesign discovery process.
If the problems center on a few pages or customer journeys, targeted improvements may solve them without rebuilding the full site.
The decision depends on how much you still need to learn before choosing the solution.
Website UX audit: what it is and what it checks
A website UX audit is a structured review of how well a website helps users understand information, navigate the experience, and complete important tasks.
The exact methods depend on the site and the questions your team needs to answer.
A UX team might review:
- navigation and information architecture;
- key customer journeys;
- website analytics and behavioral patterns;
- content and messaging clarity;
- forms and conversion paths;
- mobile and cross-device experience;
- accessibility issues;
- interface consistency;
- heuristic usability principles;
- usability testing or other user research.
A heuristic evaluation is one common part of the process. Nielsen Norman Group describes heuristic evaluation as having evaluators examine an interface and judge how well it follows recognized usability principles.
That method can help experts identify potential usability problems. Research with users answers a different question: how people respond to the experience while trying to complete realistic tasks.
A strong UX audit turns findings into priorities
You do not need a 70-page document listing everything someone dislikes about your website.
You need enough evidence to decide what to do next.
A useful audit should help your team answer questions such as:
- Where do users struggle?
- Which journeys create the most friction?
- Which issues affect important business or user goals?
- Are the problems isolated or spread across the experience?
- Which findings deserve attention first?
- Which issues need more research before you change anything?
That context separates useful UX analysis from subjective design feedback.
Take navigation as an example. Someone might flag a hidden menu as a usability problem. That observation alone does not tell you whether changing it will improve the experience. The answer depends on the users, device, available alternatives, and tasks people need to complete.
A heuristic review gives you expert evidence to consider. It does not remove the need to understand the specific context in which people use the site.
Three paths after a UX review
The result of a UX audit should influence the scope of the work that follows.
Your situation | Sensible next step | Reason |
|---|---|---|
You see clear symptoms, but the cause remains uncertain | Run a UX audit before defining redesign scope | You need evidence about the problem before committing to the solution |
Business, brand, platform, or structural changes already require a new site | Include UX diagnosis within redesign discovery | You know the website needs major change, but research should still guide what you build |
Problems cluster around a few pages, flows, or interactions | Prioritize targeted improvements | The current site may still support the business without a full rebuild |
This framework keeps the conversation focused on the problem you need to solve rather than the size of the project.
Choose an audit first when the cause is unclear
A separate website UX audit makes the most sense when your team sees problems but has competing explanations for them.
You might be in this position if:
- conversion or engagement has dropped without a clear reason;
- customers struggle to find important information;
- sales and marketing disagree about what the website needs;
- years of incremental updates have made the experience harder to manage;
- leadership wants a redesign because the site feels old;
- you need to decide which improvements deserve budget first.
Starting with diagnosis gives your team a stronger basis for defining scope.
For example, low conversion might point to confusing navigation, weak messaging, unclear proof, form friction, or a mismatch between the visitor and the offer. Changing the visual design before you understand the cause may leave the original problem in place.
If conversion is the main concern, a broader conversion rate optimization approach may also make sense. CRO focuses more closely on behavioral data, testing, and the parts of the journey that influence desired actions.
Include UX diagnosis in redesign discovery when major change is certain
A standalone audit adds less value when the organization already knows that the current website can no longer support the business.
A company may have:
- entered new markets;
- changed its positioning or service mix;
- outgrown its CMS or technical platform;
- accumulated a site architecture that no longer fits its content;
- introduced new accessibility or governance requirements;
- changed the audiences the website needs to serve.
These projects still need UX analysis.
The difference is where the work happens.
A strong website strategy process can include analytics review, journey mapping, information architecture analysis, audience research, content planning, and other forms of diagnosis before the team moves into design.
The same principle applies to a broader website design project. Research and UX thinking should shape what gets designed rather than entering the process after the main structural decisions have already been made.
You can skip the separate engagement without skipping the thinking. Our guide to the B2B website redesign process shows where that diagnosis fits.
Targeted improvements may be enough
A UX audit can also narrow the scope.
Your team may find that most of the experience works well while a few areas create disproportionate friction.
Perhaps users struggle with one form. The navigation labels need work. A key service page fails to answer buyer questions. Important proof appears too late in the journey.
Those problems may call for focused improvements instead of a full website redesign.
The reverse can happen too. A few visible problems may trace back to deeper issues across the information architecture, messaging, content structure, and customer journey.
A useful audit helps your team see which situation you have before you set the budget and scope.
UX audit vs. usability testing, CRO, and accessibility audits
These disciplines overlap, but they answer different questions.
Approach | Main question |
|---|---|
UX audit | Where does the current experience create friction, and what deserves attention? |
Usability testing | How do representative users behave when they try to complete key tasks? |
Conversion rate optimization (CRO) | Which parts of the journey may be limiting desired actions, and which improvements should the team test? |
Accessibility audit | Where does the site create barriers for people with disabilities or fail relevant accessibility requirements? |
Usability testing gives you evidence from people using the interface. Nielsen Norman Group’s usability testing guidance describes a common format in which a researcher asks participants to perform realistic tasks, observes their behavior, and listens to their feedback.
Accessibility evaluation requires its own methods and expertise. W3C’s Web Accessibility Initiative explains that automated tools can help identify accessibility problems, but no tool can determine conformance on its own. Knowledgeable human evaluation remains necessary.
A project may use several of these methods. The right mix depends on the decision you need to make.
Questions to ask before commissioning a UX audit
Ask what the audit will help your team decide before you pay for one.
A few questions can expose whether the scope fits your needs:
- Which business or user problems will the audit investigate?
- Which pages, journeys, and audiences will the team review?
- Which evidence will the team use?
- Does the scope include user research, expert review, or both?
- How will the team rank findings?
- Will recommendations separate small improvements from structural changes?
- How will the findings influence redesign scope?
- What happens after the audit?
The answers should give you a clear picture of the process and the decision you will be able to make at the end.
Use the audit to reduce uncertainty
A website UX audit earns its value when it helps you make a better decision about what comes next.
If you know the website underperforms but cannot explain why, an audit can help you define the problem before committing to a redesign.
If the business already needs a new website, include UX diagnosis in the redesign process before your team starts making design decisions.
If the problems turn out to be concentrated, fix the areas that create the friction.
The goal is to understand the current experience well enough to invest in the right level of change.
For teams that need that diagnosis before setting redesign scope, 500 Designs’ UX Audit & Usability Testing service combines UX evaluation, analytics, usability testing, and prioritized recommendations to help define the next step.
UX audit FAQs
What is a UX audit?
A UX audit is a structured review of how well a website helps people understand information, find their way and complete important tasks. It combines expert review, such as a heuristic evaluation, with evidence from analytics, key journeys and, where needed, usability testing, then ranks what to fix first.
What does a website UX audit include?
Usually navigation and information architecture, key customer journeys, analytics, content and messaging clarity, forms and conversion paths, the mobile experience, accessibility issues, interface consistency and a heuristic review. The mix depends on the questions your team needs answered.
Do you need a UX audit before a website redesign?
Run one first when you can see problems but can’t yet explain their cause or scope. If a new site is already certain, include the UX diagnosis in redesign discovery. If the problems sit in a few pages or journeys, targeted fixes may be enough. See signs you need a new website if you’re still deciding.
How is a UX audit different from usability testing?
A UX audit looks across the whole experience to find friction and set priorities. Usability testing watches representative users try realistic tasks. Many audits include a round of usability testing to confirm the most important findings.
Who runs UX audits for B2B websites?
500 Designs, a B2B brand and website agency in Irvine, California, runs UX audits and usability testing as a standalone engagement or as part of website strategy and redesign work.





