TLDR; Two tacos 🌮🌮 because it "probably" works, but the UI and server speed were too terrible for me to bother with.

I'm a CRO nerd 🤓 - I've used a lot of conversion optimization tools: Google Optimize, VWO, Convert.com, Optimizely, and more. I've been around the block, and I wanted to love this tool. I pay a lot of money for testing services, but I quit after an hour. I'd rather pay or use Google Optimize.

🔍 First issue, let's start. Medium gray text on white or light gray backgrounds is an accessibility nightmare. Check your UI's contract ratios (hint, hover over the elements in Chrome's inspect tool). I can't imagine anything pro-level starting like this. Fine, I'll get my reading glasses and battle on.

🐢 The second issue, the site is slow. I see three reviews here on AppSumo, so I'm guessing the app isn't getting hammered right now. No idea why it seems to take so long to load.

For example, I clicked on the logo to load the dashboard. When I got annoyed, I started counting. I hit a count of 15 one-thousand before my EMPTY dashboard loaded. No project started yet, and I'm just trying to find stuff. Some pages load in a few seconds, others take quite some time.

Let's move on.

🤔 Let's create a test. How hard can it be?

I create a PROJECT. Part of that involves creating a LOCATION and a TEST. A LOCATION is part of a SITE, which we don't get to make yet. So, when we make a LOCATION, if we type a domain in, it creates a SITE named after the test location instead of the domain.

😕 Any of you confused yet? I sure as hell am. I'm used to testing tools organizing things by domain. While it may be flexible not to organize website tests by domain first, it's terribly unintuitive. With a sigh, I slog deeper into this mess.

OK, in making the LOCATION, we need a title, a SITE, a URL (which, per the placeholder, apparently, still needs to have the domain typed into it), etc. We can also use RegExp, which avoids needing to type the domain in multiple times, I guess.

There's a "Matching by Data Object (optional)" - There's no help link here, so maybe it's matching by a data attribute on an item? I have no clue. So let's move on.

The Editor URL is optional, and there are some advanced parameters. Again, no links to help docs on the advanced params, so I guess not needed. Yay! After about 4-5 seconds of saving, we're done with our first LOCATION.

There's an option (checkbox) that says "Include Optimize Build Framework?" - No clue what this is, and there's no help link or tooltip. I guess I don't need that then. Moving on.

😣 So, I've made all these things and ignored a random checkbox. I'm at the actual part where I create variations.

Not bad, but my biggest complaint (using the Advanced Editor) is that when you click "Edit CSS" I get a modal labeled "Variation CSS" instead of using my variation name.

Next step, Scripts, none on this test, next step.

[CONTINUED IN THE FIRST COMMENT]