Design thinking for better websites. Explore company profiles
Article Redesign measurement

How to measure whether a website redesign worked

Judge a redesign against its original visitor tasks and business outcomes, with a baseline and context for other changes.

A browser page beside a website wireframe, illustrating redesign measurement.

Measure a website redesign against the problems it was meant to solve. Before launch, record how people complete important tasks and what outcomes matter to the business. After launch, compare the new experience with that baseline while allowing for other changes that may affect results.

Define success before changing the site

Choose a small set of task and business measures. A service site might track qualified enquiries and whether visitors can find eligibility information. An online shop might look at product discovery, checkout completion and support questions. Avoid using page views alone as proof that a page is useful.

Add qualitative evidence. Ask people to complete a task on the current site and note confusion, errors and time-consuming steps. Record feedback from staff who handle enquiries. This creates a clearer starting point than a general feeling that the old site looks dated.

Check the measurement setup

Make sure events and forms are recorded consistently before comparing periods. Confirm that the new site counts the same completed action and that test submissions are excluded where practical. If the tracking method changes with the redesign, note the break in measurement rather than treating the numbers as directly comparable.

Protect privacy and collect only data needed for the decision. A useful redesign review can combine aggregate behaviour with direct customer research without building detailed profiles of individuals.

Compare with context, not certainty

Traffic source, seasonality, campaigns, prices and service availability may change alongside the website. A rise or fall in enquiries cannot automatically be attributed to design. Compare like-for-like periods where possible and keep notes about other changes.

Look beyond averages. A new homepage may help first-time visitors while making a returning customer's route harder. Review key journeys separately and test accessibility and mobile use after launch, not only before it. Compare what people say they expected with what the site actually offered at the point they stopped or asked for help.

Turn findings into the next improvement

Schedule an early review for urgent defects, then a later review once the site has enough ordinary use to reveal patterns. Prioritise fixes by impact and evidence. If a form completion rate falls, examine its fields and errors before assuming the page needs a new visual style.

Share what the redesign achieved, what remains uncertain and what will be tested next. A redesign is successful when it helps people complete meaningful tasks and leaves the organisation able to maintain that improvement.

Frequently asked questions

How soon can we judge a redesign?

Check for broken journeys immediately, but allow enough normal use for broader patterns. The right period depends on traffic and the type of decision.

Is more traffic proof the redesign succeeded?

No. Traffic can change for many reasons. Compare the tasks and outcomes the redesign targeted, while noting campaigns and other factors.

What if the results are mixed?

Identify which audiences or journeys improved and which did not. Use that evidence to plan focused changes instead of declaring the whole project a success or failure.