It's great to see multiple products in the market trying to solve this problem and I admire your ability to do so without a large team or any funding. It's unclear how the market will grow in the future but we're thrilled to see Optimizely grow +397% amongst the top 10,000 websites in the last year to over 2,500 happy customers.
I'm glad to see you are focusing on improving your response time. Unfortunately hitting live servers serving dynamic content in 5 locations is never going to be able to beat 100,000 edge-cached nodes in 75 countries serving static content when it comes to response time and reliability.
According to the link you provided it looks like Pingdom reports VWO response times as:
VWO Slowest Average: 352ms
VWO Overall Average: 207ms
VWO Fastest Average: 45ms
According to Pingdom, Optimizely response times are:
Optimizely Slowest Average: 95ms
Optimizely Average: 65ms
Optimizely Fastest Average: 19ms
Here is a head-to-head comparison of Optimizely vs. VWO including response time and feature differentiation: http://i.imgur.com/BRTxC.png
To clarify some of the points you might have misunderstood:
You are right we don't currently offer ancillary features like heatmaps and usability testing. We've been focused on offering the best possible experience for A/B and multivariate testing.
Did Optimizely make that graphic? The support comparison is deceptive. You are comparing the basic plan of VWO to the platinum plan of Optimizely. And comparing lines of code is meaningless. In fact for the reasons outlined above by paras, a 21 line implementation which does not block the site load is more beneficial to most users.
@paras: Your response times do not look good. Why are you using a homegrown pseudo CDN instead of a real one like akamai or limelight ? Also why not make your API docs public ?
The reasons for having a homegrown CDN is mentioned in the article. The major reason though is that our URL matching (determining whether to run a test or not on a particular URL) is complex, and CDNs cannot handle that.
Reason API doc is not public is because API is on demand right now, but anyone can use it. They just have to request for a key from us.
I'm glad to see you are focusing on improving your response time. Unfortunately hitting live servers serving dynamic content in 5 locations is never going to be able to beat 100,000 edge-cached nodes in 75 countries serving static content when it comes to response time and reliability.
According to the link you provided it looks like Pingdom reports VWO response times as:
VWO Slowest Average: 352ms
VWO Overall Average: 207ms
VWO Fastest Average: 45ms
According to Pingdom, Optimizely response times are:
Optimizely Slowest Average: 95ms
Optimizely Average: 65ms
Optimizely Fastest Average: 19ms
Here is a head-to-head comparison of Optimizely vs. VWO including response time and feature differentiation: http://i.imgur.com/BRTxC.png
To clarify some of the points you might have misunderstood:
- Here is a demo showing the Optimizely visual mobile editor: http://www.youtube.com/watch?v=HucXw_egPRs
- Documentation of Optimizely one-click integrations: http://support.optimizely.com/customer/portal/articles/58188...
- The Optimizely API is publicly available at: https://www.optimizely.com/docs/api
You are right we don't currently offer ancillary features like heatmaps and usability testing. We've been focused on offering the best possible experience for A/B and multivariate testing.