
Ro's Wegovy Page Is Testing How Much Story a Pill Needs
Ro is running a live content-depth A/B test on its Wegovy landing page — a lean control vs. a richer variant with proof stats, a pill explainer, and a comparison table. Here's what the design choices reveal.
Aiko Tanaka
Design Director · · Updated
Ro's Wegovy pill landing page (ro.co/lp/weight-loss/wegovy/pdp) is quietly running two very different versions of itself. We caught it through same-run variance: five visits, five different browsers, and two distinct layouts. Visits 2, 3, and 4 (Chrome, Firefox, Edge) load a dense, storytelling-heavy page. Visits 1 and 5 (Safari and a separate Chrome session) load a stripped-down version missing entire sections. Because the minimal layout shows up identically across two unrelated browser engines — and the rich layout shows up identically across three others — this isn't a rendering quirk. It's a deliberate content-depth experiment, and at 88% confidence, one of the more interesting ones we've logged this month.
What the eye hits first
In the control, the page opens lean: hero, CTA, done. There's no stat block competing for attention before the fold breaks. That's a legitimate design position — get to the action fast, trust the brand equity of "Wegovy" to do the persuading.
The enriched variant changes the opening argument entirely. It leads with a 14% weight loss stat block — a number, bolded, sitting high in the hierarchy before any lifestyle imagery or copy block. Numbers in isolation read as proof, and proof placed above the fold is a classic F-pattern move: the eye's first horizontal sweep lands on the stat, not on a headline promise. It's the difference between telling someone "this works" and showing them a data point they can screenshot and believe on sight.
The pill explainer as a hierarchy decision
The section Ro calls "Meet the Wegovy pill" is doing real information-architecture work, not just decoration. Introducing an oral form of a drug people associate with injections requires a dedicated beat — you can't fold that into a bullet point. Giving it its own hero-style section, with presumably its own imagery and headline weight, signals to the user: this is new information, pay attention here. That's a proximity and common-region play straight out of Gestalt theory — grouping the pill explanation visually separates it from the general product pitch so it reads as a distinct, absorbable idea rather than noise buried in a longer scroll.
Pen vs. pill: the comparison table
The "Wegovy two ways" table is the boldest structural addition, and the riskiest from a scroll-friction standpoint. Comparison tables are inherently System-2 content — they ask the user to stop skimming and start evaluating, row by row, column by column. That's a deliberate trade against momentum. The control variant avoids this entirely, betting that undecided users bounce before they reach a table. The enriched variant bets the opposite: that people choosing between an injection and a pill want the side-by-side before committing, and that friction here is qualifying friction, not abandonment friction.
This is the crux of the experiment. Optimizely's framing of A/B testing as a tool for improving "a single goal like conversion rate optimization over time" applies cleanly here — Ro isn't guessing whether more content is universally better, they're isolating whether this specific piece of friction (a comparison table, mid-scroll) pays for itself in add-to-cart lift.
Lifestyle imagery and the doctor photo
Testimonials in the rich variant carry lifestyle and member photography instead of plain text quotes or stock avatars. Faces do heavy lifting in trust-building layouts — they add warmth and specificity, and they slow the scroll just enough for the quote next to them to register. Pairing that with a doctor image in the membership section is a second, distinct trust signal: one is peer proof ("people like me use this"), the other is authority proof ("a clinician stands behind this"). Running both together in the same variant suggests Ro isn't testing which trust lever works — they're testing whether trust needs layering at all, versus a leaner page that trusts the Wegovy name alone.
Reading the contrast between variants
Side by side, the real design question isn't "more vs. less content" — it's whether depth earns its scroll cost on a page this high-intent. Users arriving at a PDP for a specific drug already know roughly what they want. The control assumes they're ready to convert on brand recognition. The enriched variant assumes they still have live objections — safety, mechanism, social proof, clinical backing — and answers each one with a dedicated section before asking for the click.
Both are legitimate hypotheses, which is exactly why this is worth testing rather than assuming. As Contentful notes in its guide to conversion-focused A/B testing, the value isn't in having an opinion about what should convert better — it's in the discipline of not leaving that answer on the table. Ro is running that discipline on a page where the stakes (a semaglutide pill, a crowded weight-loss ad market, real medical trust concerns) make guessing especially expensive.
The takeaway for your roadmap
If you're running a high-intent PDP or landing page this sprint, don't treat "add more proof sections" as an obviously good idea — treat it as a hypothesis with a real cost side. Ro's test is structured well because it isolates the trade cleanly: same offer, same CTA, only the depth of educational scaffolding changes. Before you add your own stat blocks, comparison tables, or trust imagery, ask whether you're testing genuine objection-handling or just decorating a page that already converts on momentum. Pick one variant, one added section at a time if you can, and measure add-to-cart or checkout-initiation separately from scroll depth — because on pages like this, the friction and the persuasion are often coming from the exact same block.
Read next
More from the ABWatcher blog
Nov 22, 2026
Snake River Farms Tests a $25-Off Popup on Its Ad Landing Page
We caught Snake River Farms split-testing an email-capture form and $25-off modal on its landing page. Here's the math on what it would take to call a winner.
Nov 21, 2026
Snake River Farms Tests Mid-Page Email Capture on Its Ad Landing Page
SRF is A/B testing a mid-page lead-capture block and a $25-off popup against a simpler hero-only promo banner on its paid landing page, detected 2024 week-over-week.
Nov 20, 2026
Attio Is Testing a New Tier, Higher Prices, and a New Pitch
Attio is running a live pricing page test with a new $1,000 "Ultra" tier, higher Plus/Pro prices, and a new headline — here's what we caught and what it means.
Nov 19, 2026
Found Quietly Tested a 25% Price Cut on Its Pricing Page
We caught Found running a live pricing A/B test with an annual billing toggle that drops Found Plus from $35 to $26.25/mo. Here's what changed and why it matters.
Nov 8, 2026
Astro Proves "Zero Lock-In" With a Live Code Demo, Not a Claim
Astro's homepage replaces a trust badge row with a working, clickable framework demo — here's the hierarchy and interaction design behind it, detected 60% rare on astro.build.
Nov 7, 2026
Basecamp's Big Numbers: Why Hyper-Precise Stats Beat Vague Social Proof
Basecamp's homepage swaps "trusted by thousands" for 1.7 billion to-dos and 5 petabytes of data. We break down why precision beats vagueness as social proof — and how to test it.
From the glossary
Vocabulary the article uses. See all terms →
- Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
- Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
- Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
- Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
- Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
- Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See more like this
ABWatcher catches A/B tests like this across 1,000+ brands.
Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.