Skip to content
ResearchUX lexicon

What is A/B testing in UX?

A/B testing in UX means showing two versions of a design to different groups of users and measuring which one gets the better result.

also calledsplit testing · bucket testing · split-run testing

Think of it as a fair fight between two ideas. Version A is what you have today, version B is the change you suspect is better, and your users cast the votes with their clicks, sign-ups or purchases. You stop arguing about opinions and start reading numbers.

In short
  • Two versions, random groups, one clear goal.
  • Change one thing at a time so you know what caused the result.
  • It tells you what won, not why. Pair it with user research.
  • You need enough traffic and a runtime you decided in advance.
01

How an A/B test actually works

You pick one thing to change, say the wording on a button or the order of two form fields. Then you split your real traffic at random. Half the visitors see the original, the other half see the variation, and a testing tool records what each group does.

The word that matters here is random. If version B only reaches people on Monday mornings, you are not testing a button, you are testing Mondays. Good tools handle the split for you, but it is worth knowing why they do it.

When enough people have gone through both versions, you compare the results on one pre-agreed goal, for example the share of visitors who finished checkout. If the gap is bigger than chance can reasonably explain, you have a winner.

02

Change one thing at a time

This is the rule people break most. If you rewrite the headline, swap the hero image and recolour the button all in version B and it wins, you have no idea which change did the work. Maybe the headline helped and the new image quietly hurt.

One change per test is slower, but it gives you something you can reuse. You learn that a clearer button label helps your audience, and that sticks for every page you build afterwards.

03

What A/B testing is good at, and what it is not

It is great at settling small, concrete questions on a product that already has traffic: which call to action, which price layout, which onboarding step. It is not great at telling you why people behave the way they do.

If version B wins you know that it won, not the reason. That is where interviews and usability tests come in. Use A/B tests to measure and qualitative research to understand.

It also needs enough visitors. A site with a few dozen visits a day can wait months for a trustworthy result, and in that case talking to five users will teach you more, faster.

04

Mistakes that quietly ruin results

  • Stopping the test the moment one version pulls ahead. Early leads often fade, so decide the sample size or runtime before you start.
  • Testing too many variations at once, which needs far more traffic.
  • Picking the winning metric after you have seen the data.
  • Running a test during an unusual week, such as a big sale, and treating the result as normal.
  • Ignoring a tiny improvement that costs a lot to build. A win is only useful if it is worth shipping.
Common questions

A/B testing: your questions, answered

What does A/B testing mean in UX design?

It is a method where you show two versions of a page or feature to different groups of real users at the same time. You then compare a single metric, like sign-ups or clicks, to see which version performs better.

How long should an A/B test run?

Long enough to reach the sample size you calculated before starting, and usually for at least one or two full weeks so that weekday and weekend behaviour are both covered. Stopping early because one version looks ahead is a common way to get a false winner.

How many visitors do I need for an A/B test?

It depends on how big a change you expect and how often people already complete your goal. Smaller expected differences need more visitors. A sample size calculator will give you a number, and if it says you need more traffic than you have, test bigger changes or use qualitative research instead.

What is the difference between A/B testing and multivariate testing?

A/B testing compares two versions that differ in one thing. Multivariate testing changes several elements at once and measures every combination, which can show how elements interact but needs a lot more traffic.

Can designers run A/B tests without a developer?

Often yes. Many testing tools let you change text, colours and layout with a visual editor and handle the traffic split for you. Bigger structural changes usually still need a developer.

People also ask

More quick answers

Is A/B testing qualitative or quantitative?

Quantitative. It counts what people do rather than asking them why, which is why it works best next to interviews or usability tests.

What is statistical significance in A/B testing?

It is a way of checking whether the difference between your two versions is bigger than random luck would likely produce. A result that is not significant should not be trusted as a real win.

What can you A/B test on a website?

Headlines, button labels, images, form length, pricing layouts, navigation labels and onboarding steps are all common choices. Start with the pages that get the most traffic.

What is a control in A/B testing?

The control is the current version you are comparing against. The variation, or variant, is the change you want to try.

Which tools are used for A/B testing?

Teams commonly use dedicated experimentation platforms or the testing features built into analytics and marketing tools. The best choice depends on your traffic and budget.

Keep reading
Free and open source

Found this useful? A GitHub star helps other designers find it.

Star on GitHub