Sometimes clunky, but always useful and valuable
September 03, 2018

Sometimes clunky, but always useful and valuable

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Visual Website Optimizer

Our growth department works with clients using VWO to address potential areas in which their e-commerce sites could attract and keep more customers. It's the primary tool that we use to turn conversion rate optimization proposals into concrete data that we can then use to inform clients and make actionable recommendations.
  • Organization and management of multiple A/B tests paused or running at once is very well laid out and intuitive.
  • Heatmaps have provided a huge amount of actionable data in focused testing areas.
  • A/B test overview data is very easy to make inferences from because of its simple and visually outstanding presentation.
  • The Chrome extension tends to have issues loading Heatmaps. It's not uncommon to go to a Heatmaps page and have to refresh the page at least once in order for the extension to load correctly.
  • The visual editor for making variations for A/B tests feels clunky and often doesn't appear in the final version (previewing the variation as a page on its own) as it does in the editor. At times the undo button has caused erratic behavior such as duplicating or "redoing" several of the same action at once rather than stepping backward.
  • Overall, if there were any way to decrease the amount of time that the Chrome extension takes to load, I could see workflow across several areas being greatly improved.
  • I can't speak to hard numbers but as our primary analysis tool it's at the center of our conversion rate optimization business and is therefore indispensable in terms of our revenue.
I would say the primary determinant of Visual Website Optimizer's usefulness is the amount of data coming from the website(s) you're analyzing. In the case of sites less focused on conversions or those with less traffic, data can be volatile and/or confounding (your hypothesis might be strong but the data isn't actionable). I would recommend its use for any conversion-focused sites that have a relatively predictable and steady flow of traffic.