Do styling A/B tests work on lead capture pages?

Worse here than elsewhere. Styling tests win 10% of the time on lead capture pages, against 15% across all page types. The category is not the problem; this page is.

It is not the best use of a test slot on this page either. CTA copy tests win 21% on lead capture pages on 38 tests tests.

Small sample. Few of these tests cleared the bar. The 95% interval on that win rate runs 6% to 19%, so read the figure as directional.

The numbers

	lead capture pages	all page types
Tests analysed	50+	1,000+
Beat control	10%	15%
No measurable difference	68%	—
Lost to control	22%	—
Median lift when it won	not reported	—

Median traffic per variant was 1642 visitors.

What else is worth testing on lead capture pages

change type	win rate on lead capture pages	tests
CTA copy	21%	38 tests
Split URL	12%	100+
Headline	11%	50+
Styling (this page)	10%	50+

Only change types with at least 30 tests on lead capture pages appear here.

What counts as a styling test

Visual treatment shifts — spacing, weight, borders, colour, shadows — with the same content in the same order. Move the content and it is a layout test. Rewrite it and it is a copy test.

Control and variant wireframe for a styling A/B test — Control on the left, variant on the right. For how this differs from adjacent categories, see the styling benchmark.

Styling tests that won on lead capture pages

On mobile, reorders two child divs within a container and adjusts top padding, without changing any text
Hides the control button group and shows a styled card-like variant button group (with hover/click effects), swapping between desktop and mobile versions responsively.
Adds pulsing scale and glowing text-shadow animation to the price display, and forces the step info text to stay black and fully opaque
Hides one process section and displays a date-tiles section as a grid, with no wording changes

Styling tests that did not

Adds collapsible accordion behavior and section styling, initially showing only the first item expanded with read more/less toggles and rotating plus icons
Adds collapsible accordion behavior with show/hide sections, toggle icons, and read-more/less labels without changing wording
Hides the old statistics section and shows the achievement badges element; no wording changes

These are individual tests, not rules. Each ran on one site, with one audience, against one page we are not showing you. They are picked to be illustrative rather than sampled at random, and a change that won here can lose on your page for reasons none of this captures. Read them as prompts for what to test, not as findings to copy.

Who ran these tests

This is every Mida account that ran a readable test — in-house marketers, founders, product teams, and agencies working on client sites. Nothing here is filtered by who ran the experiment or how experienced they are.

Low win rates are normal in experimentation, including at the top end. Microsoft's experimentation team, reporting on its own platform, found that only about one third of ideas improve the metric they were designed to improve — and that roughly another third actively hurt it. That is a dedicated experimentation organisation with research, prioritisation and review behind every test.

A mixed population like this one runs below that. The gap is roughly what disciplined practice buys you: ideas grounded in research rather than opinion, one variable at a time, and tests built so the result can actually be read.

So treat these as a general base rate, not a target. If you would rather not close that gap the slow way, find a CRO agency in the United States, the United Kingdom, the Netherlands or Australia — or browse every region.

A win is a variant that beat its control on that test's primary goal with a statistically significant result. Tests that never got enough traffic to say anything either way are excluded. The methodology has the full detail, including what these numbers cannot tell you.