VWO Logo
Like this post?
Read our in-depth guide to Conversion Rate Optimization
Share this post
3 Min Read

Architecture update: leaner, meaner and faster A/B tests

placeholder
Paras Chopra
Founder and Chairman of Wingify.

In our mission to be the best A/B testing platform on earth, we have recently updated VWO architecture. This blog post updates what has changed and why.

Prelude: phasing out of optional page tagging code

In addition to tag-less testing which required no code changes, VWO had optional code for people who liked to tag their pages with code (like other free testing tools). As we all know it, tagging is frustrating, cumbersome and error-prone. So, we have dropped it all together from VWO. No user used this feature and it only created confusion.

Meaner: multiple tests on a SINGLE page possible now

Until now you could run only one test per page. While this is the way it should actually be, some advanced users ran a site wide test (for example, on footer or sidebar) and then they wanted to test a specific page also. With old architecture, one could run only one test per page so VWO only ran the most recent test on that specific page. The old architecture also meant that if one of the site pages is a test goal, you couldn’t run a different test on that page. This was especially frustrating to users who ran multiple A/B tests across their funnels.

But ALL this has changed. You can now run multiple tests on a single page or run tests on a page which is a conversion goal for a different test. A note of warning: we actually discourage multiple tests on a single page because it jeopardizes statistical significance of those tests. It is best to avoid such a condition.

Faster: asynchronous content loading

Now onwards, the content of test variations will be loaded asynchronously without stalling browser. This means while VWO is fetching variation content, browser can keep loading your rest of the page. This feature will make the tests noticeably faster, especially if you had lots of content in your variations.

Leaner: 10% smaller JavaScript code

We used Google’s excellent Closure Compiler to shorten the code by 10%. The current size of shortened, gzipped code stands at about 26.5 KB. Most of this code is JQuery, which VWO uses quite heavily (because it so awesome!).

Smaller JavaScript file means less data to download for your visitors and hence faster tests.

Overall Thoughts

We are committed to faster loading tests for your visitors. Every millisecond of delay frustrates visitors and we perfectly understand the importance of page load time for your business. Rest assured our engineers are fanatics about optimization (in all senses of the word). Do let us know your feedback on the updates and if you have any ideas/suggestions on making the test loading even faster.

More from VWO

Measuring an Inbound Campaign through the Conversion Funnel

If you thought measuring the success of your inbound campaign is a tedious job, well…

Read More
Smriti Chopra

Smriti Chopra

6 Min Read

How To Optimize Conversion Rate On Website Templates

The huge number of website templates available today has made it easier than ever to…

Read More
Sujan Patel

Sujan Patel

7 Min Read

This One Mistake is Costing Your eCommerce Store Sales and Revenue

I’m going to take a swipe at one of the most widely recommended ‘best practice’…

Read More
Siddharth Deswal

Siddharth Deswal

5 Min Read
>
Shanaz from VWO

Hi, I am Shanaz from the VWO Research Desk.

Join our community of 10,000+ Marketing, Product & UX Folks today & never miss the latest from the world of experience optimization.

A value for this field is required.

Thank you!

Check your inbox for the confirmation mail