Webnetism
  • Design
    • Web design
    • User experience (UX) design
    • Branding
    • Graphic Design
  • Development
    • Web applications
    • Desktop & mobile applications
    • Intranet development
    • CMS:42
    • Ecommerce websites
  • Hosting
    • Colocation hosting
    • Shared hosting
    • Disaster recovery
    • Domain Names
    • Email services
    • Dedicated hosting
    • Cloud backup
  • Marketing
    • Email marketing
    • SEO
    • PPC
  • Projects
  • About us
    • Team
    • Careers
  • Blog
  • Contact

Importance of A/B Testing on your website

Written on 24 May 2016

How much testing do you do on your website?

At some point you’ve probably come across or carried out A/B testing. Maybe that’s from testing a subject line in an email newsletter or a social media post. But how much testing do you do on your website?

What is A/B testing?

In web design A/B testing is taking two different versions of a page and running them simultaneously to see which version works better. For example, you might want to test whether “Buy now” delivers more sales than “Add to Card”. Typically, A is the existing design (called the control) and B is the challenger. Once you start the test half your visitors are sent to variant A whilst the other half are sent to variant B. You can then select the winner based on the metric you’re looking to change, e.g. sales, conversion rate, time spent on page, bounce rate etc.

Split testing example 

What to test on your website?

Because you’re sending each user to a different version of the webpage the possibilities of what to test are almost infinite. The key to a successful test is to focus on one change that is likely to have the most impact, for example:

  • The look or call to action on a button
  • The headline
  • Different images
  • Website copy
  • Number of fields on a form
  • Different pricing/offers 

The Do’s and Don’ts

Don’ts

  1. Don’t let your opinion interfere with the outcome of a test. You might not necessarily like changing the button from your aesthetically pleasing beige to bright red, but the aim of carrying out a test is to improve that key metric that you’re looking to move.
  2. Don’t test pages independently. It’s really important that you keep an A/B test as fair as possible. It might be easy to make a quick change from one week to another in your CMS, but don’t! Other factors (which may be out of your control) can influence weekly visits to your site.
  3. Don’t set results in stone. Consumer behaviour often changes over time and you might find that new red button is now better off being a green button.

Do’s

  1. Do test more than one variant at a time. For example, you might want to test your beige button against variant B, a red button and against variant C, a green button.
  2. Do test across your whole website, if you’re testing something that’s used in lots of places (like an add to cart button) make sure you change them all and not just one.
  3. Do analyse results across different devices. You might find that a different variant is more suitable; this is where responsive web design is crucial.

If you don’t currently carry out regular A/B testing on your website, get in touch and we can discuss your requirements.


Join the newsletter and stay up to date with us. You can unsubscribe at any time.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Find out more about how your email address is used in our privacy policy
Webnetism / Continental Ltd, Herrick Way, Cheltenham GL51 6TQ
t: +44(0)1452 855 558e: sales@webnetism.comcareers@webnetism.com
  • Email Guides
  • Webmail
  • Remote Support
  • Careers
  • Terms and Conditions
  • Privacy Policy
  • Cookie Policy
© copyright 2025 Webnetism
Contact Get in touch

Our use of cookies

We use necessary cookies to make our site work. We'd also like to set analytics cookies that help us make improvements by measuring how you use the site. These will be set only if you accept. For more detailed information about the cookies we use, see our Cookies page.

We'd like to set Analytics cookies to help us improve our website by collecting and reporting information on how you use it. The cookies collect information in a way that does not directly identify anyone. For more information on how these cookies work please see our 'Cookies page'.