Split testing
Done right

The easiest tool for split testing your landing pages.
Start server-side experiments in a few clicks.

Get started for free

No credit card required

Client-side

Tests are rendered using JavaScript during the loading of the page.

VS

Server-side

Occurs on the web server and not in the user’s browser.

Bad UX

Your users are likely to get exposed to the “flicker effect”, which means they will see the original page for an instant before the variation appears. And you don’t want that to happen.

Great UX

With server-side testing the variation is determined before the resource is served to the browser, hence there will be no “flicker effect”.

Slow page load

With client-side testing the page load time will suffer and your end user will have to wait in front of a blank page until the content loads.

Fast page load

Rendering happens in the server, which means performance and page load time are blazing FAST.

Just “Cosmetic” Tests

You can only test surface-level things such as layouts, colors and copy. You won’t be able to test any deeper, like an ecommerce checkout flow or a different algorithm in your SPA.

Tests that have an impact

You can test the full stack. A new algorithm, a database query, a new architecture, a complete re-brand. Tests that will have a real impact on your revenue.

More work to implement

Once the winner is determined, it still has to be built and implemented, which means longer time to hit production mode and bring benefits.

Ready from the get go

Once the winner is determined, all the variations have already been implemented and are impacting your conversion rates from the get-go.

Server-side

Occurs on the web server and not in the user’s browser.

Great UX

With server-side testing the variation is determined before the resource is served to the browser, hence there will be no “flicker effect”.

Fast page load

Rendering happens in the server, which means performance and page load time are blazing FAST.

Tests that have an impact

You can test the full stack. A new algorithm, a database query, a new architecture, a complete re-brand. Tests that will have a real impact on your revenue.

Ready from the get go

Once the winner is determined, all the variations have already been implemented and are impacting your conversion rates from the get-go.

VS

Client-side

Tests are rendered using JavaScript during the loading of the page.

Bad UX

Your users are likely to get exposed to the “flicker effect”, which means they will see the original page for an instant before the variation appears. And you don’t want that to happen.

Slow page load

With client-side testing the page load time will suffer and your end user will have to wait in front of a blank page until the content loads.

Just “Cosmetic” Tests

You can only test surface-level things such as layouts, colors and copy. You won’t be able to test any deeper, like an ecommerce checkout flow or a different algorithm in your SPA.

More work to implement

Once the winner is determined, it still has to be built and implemented, which means longer time to hit production mode and bring benefits.

We’ve built Splitstack for non-techies.

Server-side testing used to be complicated. Not anymore.
With Splitstack you can launch experiments on your landing pages in minutes, without the need for a developer.

🎉 Cookie-free solution 🎉

Launch experiments in a matter of clicks 🚀

It doesn’t have to be complicated.
Just enter the URLs you want to test and decide how the traffic should be split between them. We’ll take care of the rest.

Run your tests without hurting the experience of your users.

Our proxy-server methodology allows you to run tests at high-performance and super fast rendering, which means that your users won’t suffer from any of the downsides that occur with client-side tools.

Start running tests that have a real impact on your bottom line.

With Splitstack you can finally start testing the full-stack even without the need of a developer. Not just fancy button colors. Now you can apply structural changes to your landing pages and see the impact on your conversions from the get-go.

It’s that simple

1. Enter your URLs

Start with your control URL and add up to 5 variations.

2. Set the traffic split

Decide how much traffic we should send to each landing page.

3. Place the pixel

Implement the pixel to track your conversions. You can use GTM or any other tag manager solution.

4. You’re good to go!

Start sending traffic to your landing pages and monitor your conversions in real-time.

Plans

Billed Yearly Save 20%

Starter

Free

No Credit Card Required, No Trial Period.3 Experiments3.000 clicks2 URLs max per experimentFull analyticsCustom domains (CNAMEs)Set the traffic % betwen URLsGroup ExperimentsCustom slug
Most popular

Professional

$15

Per Month, billed annually.Unlimited ExperimentsUnlimited Clicks5 URLs per experimentFull analyticsCustom domains (CNAMEs)Set the traffic % between URLsGroup ExperimentsCustom slug
Try it for free

No credit card required

A 1 second delay in page load time can result in a 7% reduction in conversions.

And you still want to use client-side tools for your experiments? 🤔

Get started for free

No credit card required