Real experiments. Real outcomes. Actionable patterns. Browse A/B tests with problem-to-solution framing, results, and recommendations for what to test next.
The story behind this win is the iteration discipline. The first attempt at this homepage redesign changed two systems at once (messaging + routing) and produced an ambiguous result: the entry metric moved slightly positive while downstream metrics moved meaningfully negative. The team correctly identified that the routing change — which inadvertently replaced direct links to a personalized plan-search experience with modal-driven entry into a generic flow — was the downstream killer. The iteration restored the original routing and kept ONLY the homepage hierarchy changes. All funnel metrics moved directionally positive in lockstep (entry +2.38%, mid-funnel +7%, conversion +11.81%) — none stat-sig individually but consistent enough across the funnel to justify shipping. Element-level diagnostics confirmed the mechanism: the segment CTAs the team intended to promote saw a 26-30% lift in unique-visitor interaction, while the unchanged hero banner stayed flat (as expected). Two key behavioral observations: (1) page-length reduction surfaced a 4x lift on a previously buried bottom-of-page zip code input — proving the secondary lesson that 'less page' can mean 'more conversion real estate'; (2) desktop strongly outperformed mobile, with the suspected cause being mobile's lead-with-form pattern (zip code above hero) — putting the form before the message creates friction. The broader transferable insight: when a messy test confounds multiple variables, the right move is to isolate one variable in the next test, not to abandon the hypothesis.
Problem: How "Maybe later" is implemented on the content page can meaningfully affect conversion — this element is worth testing.
Problem: The information hierarchy on the product may not match how users actually scan and process the content.
Problem: How "Ux pattern optimization" is implemented on the home landing can meaningfully affect conversion — this element is worth testing.
Problem: The primary call-to-action on the product isn't converting at its potential — design, copy, or placement may be the bottleneck.
Problem: How "Ux pattern optimization" is implemented on the home landing can meaningfully affect conversion — this element is worth testing.
Problem: How prices are displayed on the listing directly influences perceived value and willingness to buy.
Problem: The information hierarchy on the listing may not match how users actually scan and process the content.
Problem: Users on the product don't feel confident enough to proceed — they need reassurance that their data and money are safe.
Problem: Visual elements on the product aren't doing enough to communicate value, build trust, or guide users toward the next step.
Problem: Visual emphasis on the product may not be drawing attention to the right elements — size, color, and contrast guide the eye.
Problem: Users can't quickly find relevant products or content on the home landing, leading to frustration and early exits.
Problem: The primary call-to-action on the home landing isn't converting at its potential — design, copy, or placement may be the bottleneck.
Problem: How "Ux pattern optimization" is implemented on the home landing can meaningfully affect conversion — this element is worth testing.
Problem: The information hierarchy on the listing may not match how users actually scan and process the content.
Problem: Multi-step processes on the home landing can overwhelm users if they can't see how far along they are or how much is left.
Problem: Users arriving at the product can't efficiently find what they're looking for, increasing bounce rates.
Problem: The first screen of the product must immediately communicate value — if it doesn't, users bounce before scrolling.
Problem: The information hierarchy on the product may not match how users actually scan and process the content.
Problem: How "Ux pattern optimization" is implemented on the product can meaningfully affect conversion — this element is worth testing.
Build on what's already been learned. Save your own experiments, surface winning patterns, and make every test count.