Guesswork
Try a brighter button.
No reason. No evidence. No way to tell.
120 conversion experiments for product designers. Each one has an annotated before and after, a clear hypothesis, measurement guidance and sourced examples.
Signups are down. Can you improve this page?
IllustrativeA message most designers know.
A visible change is not yet an experiment.
Try a brighter button.
No reason. No evidence. No way to tell.
Visitors may face competing choices. Test the hierarchy, measure signups, watch sales enquiries.
Every experiment opens like this (PR-03, pricing): the change, the reasoning, what to check, how to measure it and what could go wrong.
IllustrativeFictional product, not GoodScool, not observed data.
Pricing-page visitors spread across the plans with no clear pattern, a large share pick the cheapest plan or leave, and replays show them hovering over all three plans before deciding.
With several plans and no guidance, a buyer must work out which one fits. A visible recommendation may act as a default: some buyers will accept it and others will use it as a reference point. If the recommendation is not honest, buyers who notice may lose trust.
Add one "Recommended" label to the plan that genuinely suits most buyers, leaving prices, features and layout unchanged.
If the plan that fits most buyers carries an honest "Recommended" label, then first-period revenue per pricing-page visitor may increase because buyers who would stall or default to the cheapest plan get a reasoned starting point.
No public example is linked to this experiment, and the record says so.
The real LP-02 brief. Switch versions, then see the reasoning.
Proposed testFictional product. No measured winner.
Plausible mechanism
A reason to test, not evidence of an effect. 3 public examples are linked: 2 reported helping, 1 mixed. See them.
Seen both?
Seen both?
If the secondary hero action is demoted from a button to a text line, then signup completion per exposed visitor may increase without a fall in sales-contact requests because one dominant action could reduce the effort of choosing at the decision point.
A second button becomes a quiet text line.
Headline, primary button, destinations, layout and traffic.
Signups per exposed visitor rise by the minimum effect set before launch, with sales requests inside tolerance.
A higher share of clicks on the primary button alone.
Describe what you are seeing. The library finds matching experiments. It searches its own text, not your site.
Shoppers see shipping and fees only at the last step and may leave when the total jumps.
At the last step shoppers may hesitate when they can't quickly verify what they're buying and when it arrives.
In a multi-step checkout, shoppers can't tell how many steps remain and may quit midway.
First-time buyers may hesitate to pay because they are unsure they can return the order.
Two similar hero buttons split attention, so some visitors may delay choosing either.
Referred visitors land on the generic page and may not see who invited them or what the offer is.
Real proof exists on the page but sits far from the button, so it may not be seen at the moment of decision.
A page too short for a considered purchase leaves doubts; one too long for a warm visitor adds friction.
People who signed up but never activated stall at one step and get no reminder of where they stopped.
New users meet optional setup steps before the first-value action and leave before they see any payoff.
A blank account leaves users unsure what to build first, so many stop before creating anything.
A generic first session makes users configure things before they see anything relevant.
141 public examples from 109 organizations, including the ones that did not work.
Reported as helping
Dropped a second button on a first screen
One team, one test. A reason to try it, not a number to expect.
Reported a mixed result
Replaced a carousel with one static hero
The metric you choose decides whether it looks like a win.
Reported as hurting
Showed all-in prices from the first listing
When a cost appears is a trade-off, not a free win.
Reviewed by an AI editor. No human expert has reviewed these records yet.
75 of 120 experiments have a linked example. The rest say so.
Evidence labels are not proof.
Product designers who own conversion-sensitive journeys. CRO practitioners can use it as a reference of design interventions. It is not a statistics course.
No, but be comfortable with metrics. Every brief names the metric, guardrails and events, so you can hand it to an analyst.
No. It helps you identify, frame and plan an experiment. You run it with your own tools.
No. They are illustrative screens of fictional products, labelled as such.
No. Each is a hypothesis to test in your context, and every record shows an evidence label. Some changes could lower conversion, so every brief lists trade-offs.
141 public records from 109 organizations, each with its source, what was reported and what is uncertain. 75 of 120 experiments have one.
Yes: copy as Markdown, download or print.
No. It runs in your browser through your GLE account and stores nothing. Its content was written and checked by an AI editing process, with no human expert review yet.
120 experiments, 141 sourced examples and an honest account of what they cannot tell you.