So far we've spoken about website testing in general terms. However when the subject is typically discussed, it’s in the context of A/B and multivariate testing.
Both forms of testing have the same aim–discover the best performing variation of a page or application design–but they operate differently and suit different contexts.
A/B Testing
A/B testing (also known as split testing) is the simplest form of testing. In A/B testing you test 'whole of page' variations. The variations can be minor (such as a change to a headline) or major (an entirely new page layout with brand new content). The key thing is that each design is treated as its own entity for the purposes of testing.
Is ideal for websites with low traffic or where there’s a fast turnaround required. That’s because A/B testing requires less traffic to reach statistical certainty (the point at which you can be confident the winner will remain so when set live).
Is ideal for testing wide-scale changes to page and screen designs.
Is very useful for testing isolated changes.
Is the perfect starting point for most new test regimes as it allows you to quickly establish a high performing base before moving on to more incremental changes.
Multivariate Testing
Multivariate testing differs from A/B testing in that it is more granular. Rather than test multiple pages, multivariate testing focuses on multiple variations of specific page elements and exposing users to different combinations of these elements. This kind of testing goes beyond telling you which version of a page produces the best results, and tells you which elements on the page have the biggest impact, helping you optimise at a far more granular level.
Is perfect for making incremental changes to already high-performing pages
Requires a lot of traffic since mixing and matching different element designs means the real number of variations can be quite high. For instance, testing three elements of a page, each with three variations (including the original design) means 27 variations to be tested
Is tailor-made to testing multiple page changes at scale
Helps you understand the impact of different elements on page performance, both in isolation, and together.