Mida's agent reads your own results and tells you what is worth testing next.

Try it for FREE now

Do styling A/B tests work on product pages?

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

Headline tests carry a higher published rate on product pages — 18% on 100+ tests — though see the note below before reading that as a recommendation.

The numbers

Won 11% No measurable change 73% Lost 17%
product pagesall page types
Tests analysed250+1,000+
Beat control11%11%
No measurable difference73%
Lost to control17%
Median lift when it won +20.7%

Median traffic per variant was 3576 visitors.

What else is worth testing on product pages

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

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

What tests on product pages measured

A win rate only means as much as the thing being counted, so this is what these tests were actually optimising for.

measured outcomeshare of tests
Purchase / order complete56%
Add to cart13%
Lead / form submission9%
Signup / registration6%

Outcomes below 5% of the set are not listed, so these do not sum to 100. How the outcome was measured moves the win rate a lot — see the methodology.

Why this table is not a ranking

These rates are not like-for-like. How often a test wins depends partly on what it chose to measure: a goal that records a soft signal — a click, a scroll — clears the bar more often than one that records a purchase. Across this data, tests measured against a proxy goal win 13%, against 9% for tests measured against a business outcome.

Categories differ a lot in that mix — proxy goals account for anywhere from 2% to 41% of a category's tests.

Hold the metric fixed and the spread narrows sharply. Comparing only tests measured against a business outcome, the gap between the highest and lowest category falls from 9 points to 6 — at which point the intervals overlap and the categories are not statistically distinguishable.

So read the table as a description of what happened, not as a ranking of what works. If you want the comparison to mean something, compare categories that were measured the same way. The methodology page has the full breakdown.

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

  • It hid multiple images and several div elements on the page while leaving the text unchanged.

    E-commerce+20.7%

  • It hid the comparison modal panel and the two-column grid section from view.

    E-commerce+22.2%

  • The sticky item-info bar was restyled and repositioned, and a product thumbnail image was added next to the title while the text stayed the same.

    E-commerce+19%

  • The page showed the Afterpay paragraph, and then that paragraph was hidden.

    E-commerce+17.7%

Styling tests that did not

  • The taxes notice and product title gained a show-price class, and the inline price list was forced to display beside the title.

    E-commerceNo significant difference

  • The product link title and product link options elements were hidden from view.

    E-commerceNo significant difference

  • It hid an existing banner element within the banners section on the product pages.

    E-commerceNo significant difference

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.

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.