Do styling A/B tests work on product pages?

About the same as anywhere else. Styling tests win 14% of the time on product pages, against 15% across all page types. This page neither helps nor hurts the change type.

It is not the best use of a test slot on this page though. Headline tests win 18% on product pages on 100+ tests.

The numbers

	product pages	all page types
Tests analysed	250+	1,000+
Beat control	14%	15%
No measurable difference	70%	—
Lost to control	17%	—
Median lift when it won	+15%	—

Median traffic per variant was 3576 visitors.

What else is worth testing on product pages

change type	win rate on product pages	tests
Headline	18%	100+
Styling (this page)	14%	250+
Body copy	9%	100+
Split URL	9%	100+
Social proof	8%	50+
Price framing	8%	38 tests
Layout	6%	50+
CTA copy	6%	48 tests

Only change types with at least 30 tests on product 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 product pages

Bolds a heading, changes outline button text color and size, and makes hero background image fill full height instead of fixed 450px
headline text stating yoga practice fits into a busy life, unchanged wording shown twice suggesting only visual/style difference
Hides the original price, seating position, and variant selector elements and shows alternate price and variant selector elements instead
Reverses order and reduces font size of the price display, and adds bottom margin to a callout info wrapper; no text changes

Styling tests that did not

Hides SKU text, adds a page-load hiding overlay/anti-flicker mechanism, and styles buyer-counter and countdown elements without changing their wording
Hides an existing button (second link's button in the second div) from view
Changes text color to green and adds bottom padding on the targeted element, no wording change

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.