Compressed, from Cloudflare’s edge, applied before the page shows
Included on the sites we build and run
Each with its own installation guide
Chance to beat the control, with four guards met
The script is the only part of werun.Experiments your visitors download. It was written around one requirement: a test must never make the site slower to look at, or show the original page first.
The snippet goes first in the head and never changes. New tests reach the site without anybody touching it again: publishing a test rebuilds the script and clears the cache.
The script and the tests running on your site arrive compressed in one file from Cloudflare's cache at edge.werun.dev, not from your server.
It loads synchronously on purpose. Style changes are in place before the element exists, and an element about to change waits for it, 2 seconds at most. No frame shows the original page swapping to the variation.
The snippet carries the attributes that Cloudflare Rocket Loader, LiteSpeed, SG Optimizer, Autoptimize, WP Rocket, Jetpack Boost and Cookiebot's auto-blocking respect, so they leave it where it is.
A visitor gets a variation and keeps it on every visit. The visit counts the moment they qualify for the test, in the control too, so both sides are measured the same way.
The editors of Elementor, Divi, Bricks and the other builders, the WordPress customizer, the Webflow Editor and Shopify's theme editor never show or count a test, so editing the site and testing it stay out of each other's way.
Opens at full size.Our team builds each variation with werun.dev - Experiments, our Chrome extension, on your site as it is. Open it on a page and it shows the site's licence, whether the snippet is there, what the site is built with and its tests.
Text typed on the page, HTML, links, images (uploaded or by address), style, classes and attributes; hide it, remove it or insert HTML next to it. Browse mode keeps the page working, to open a menu or a tab before picking something inside it.
Each change is anchored on the id the builder gives the element (Elementor's, Bricks', Oxygen's, Breakdance's, Shopify's sections), animation classes are ignored, and the editor warns when a selector finds more than one element.
The editor applies changes with the same engine as the script your visitors get, so what the team sees while editing is what a visitor in that variation will see.
When the variation is a different page rather than a change, the visitor is sent there before the first page shows, and the visit is counted on arrival.
Each save keeps a version of the test: variations, changes, goals, targeting and traffic. The newest 50 stay, and any of them can be restored.
Opens at full size.The primary goal decides the test; the others are there to look at. A conversion only counts for a visitor who saw the test.
Someone clicks the button or the link picked in the editor.
Counted when the form tool confirms the send, not on the click: Elementor Pro, Contact Form 7, Gravity Forms, WPForms, Formidable, Fluent Forms, Ninja Forms, Bricks, Divi, HubSpot, Webflow and Shopify.
The thank-you page, for example: the most reliable goal when a form or a purchase ends on a page of its own.
Anything the site reports with one line of JavaScript, with revenue when there is any.
The order and its total: a snippet for WooCommerce, a Customer events pixel for Shopify, one line on any other site.
Each visitor's variation goes to Google Analytics 4 and Microsoft Clarity as well, so reports and recordings can be split by it.
A change targets an element, and the test decides the pages: the same change can run on one page, a folder or the whole site.
Opens at full size.Include and exclude rules on the address: one page, every page under a folder, the whole site, one language version, or a regular expression.
Device, new or returning visitor, browser language, country, campaign parameters such as utm_source, and where the visitor came from. Every condition has to be met.
The share of matching visitors that takes part, the weight of each variation (up to 7 besides the control) and the dates it runs.
A test warns when another running one changes the same page or the same elements, and a site can make its tests mutually exclusive.
Bayesian statistics, read in our CRM: for every goal, how likely each variation is to beat the page as it is, by how much, and what choosing it could cost.
Opens at full size.A winner needs a 95% chance of beating the control and four guards met: at least 7 days, the planned sample, 50 conversions per variation and the traffic split the test was set to.
The plan says how many visitors the test needs to detect the uplift you care about, and how many days are left at the current pace.
When the traffic split drifts from what was configured, the results say so first. It is usually a redirect, a cache or a bot, and worth knowing before reading anything else.
Changing what visitors see in a running test starts a new revision, with its metrics from zero and the earlier ones still there to read.
Every visitor gets the winning variation while the change is made on the site for good.
Every site gets an installation guide for what it is built with, and goals ready to add for its platform.
With Elementor, Divi, WPBakery, Bricks, Oxygen, Beaver Builder, Breakdance or Gutenberg.
In the site's custom head code, on a paid site plan.
In the theme's layout, right after the head opens.
In the layout every page shares.
werun.Experiments lives in our CRM, where your projects, invoices and support already are.
Each test on your site with its status, hypothesis, visitors, verdict and the primary goal’s table. Read-only, for the contacts you choose.
Tell us what you want to try. Our assistant in the CRM turns it into a draft (variations, goals, targeting, traffic and sample size) and our team picks the elements on the page.
The script runs on every domain of the site, but only the ones that count add up, so a staging copy can be tested without touching the numbers.
A site setting stops every test on the site at once, for the day something has to go back to how it was.
Opens at full size.werun.Experiments costs you nothing: it is included on the sites we build and run. These are the tools a site would use instead, with what each one charges for visual A/B testing on one site.
| Tool you would use | What it charges | With werun.Experiments | Done here by |
|---|---|---|---|
| VWO | Quote onlyPriced on monthly active users, on a quote. Its free Starter plan has been discontinued; a 30-day trial is what is left. | Included | Visual editor, Split URL, targeting and results |
| Optimizely Web Experimentation | Quote onlyEvery plan is packaged individually, on a quote, and billed on monthly active users. | Included | Visual editor, Split URL, targeting and results |
| AB Tasty | Quote onlyJoined VWO in January 2026 and is sold from the same quote-only pricing page. | Included | Visual editor, Split URL, targeting and results |
| Kameleoon | Quote onlyIts visual editor is in the Enterprise plan, priced on a quote by traffic. | Included | Visual editor, Split URL, targeting and results |
| Convert Experiences | $3,588 / yearGrowth plan, paid yearly ($299 a month), for up to 100,000 tested users a month. | Included | Visual editor, Split URL, targeting and results |
| Crazy Egg | $1,188 / yearPlus plan, billed yearly ($99 a month): A/B tests with a visual editor beside heatmaps and recordings, for up to 150,000 tracked pageviews a month. | Included | Visual editor, Split URL, targeting and results |
Read on Oct 25, 2026 on each vendor's own pricing page. A price is the cheapest plan that includes visual A/B testing, for one site and one year, billed yearly, in the vendor's currency, at its smallest traffic tier. "Quote only" is a vendor that publishes no price. A tool does more than its row says: the row is only the job it shares with werun.Experiments.
These are the other tools’ prices, not ours: list prices for the smallest plan with a visual editor. They are alternatives, so the figure is the cheapest of them, not a sum. Google Optimize, the free option many sites used, closed on September 30, 2023.
werun.Experiments tests what a page shows. When a test belongs in your product’s code, we plan it there.
The plugin, the blocks, the theme, the A/B tests and the feedback extension go on the sites we build and run, and we charge nothing for any of them.
The plugin on every WordPress site we run: security, email delivery, an activity log and a branded sign-in, one switch per module.
The Gutenberg block library we write for the sites we build: heroes, pricing tables, FAQs, jobs from your ATS and a query builder for any post type.
The base theme we build sites on: structure only, and one settings screen that writes the brand into theme.json.
Clients click any element of their site and leave a comment. It becomes a task in the CRM project, with a screenshot and the page details.
