
Discover Tests Reordering Its Homepage "How Can We Help?" Nav
Discover.com is running a live A/B test that swaps the order of Personal Loans and Online Banking in its homepage quick-nav. Here's what it likely signals about the funnel.
Maya Patel
Senior CRO Strategist · · Updated
Discover.com is quietly testing something most visitors will never consciously notice: the order of three icons. On the homepage's "How can we help?" utility nav, our vision-AI analyser caught a variant showing Credit Card, Personal Loans, Online Banking — a departure from the default sequence of Credit Card, Online Banking, Personal Loans seen across four other visits. The pattern repeated on a second Chrome visit, which rules out a rendering fluke and points to a real, running experiment (confidence: 82%, vendor_sdk_active).
It's a small surface. But small surfaces on high-traffic homepages are exactly where CRO teams find outsized, cheap wins — and this test is a clean example of how to structure that kind of bet.
What Actually Changed
The test is confined to three product-category shortcuts sitting below Discover's primary hero. In the control, Online Banking sits in the second position, ahead of Personal Loans. In the variant, Personal Loans moves up one slot, ahead of Online Banking. Credit Card holds the top spot in both — unsurprising, given it's Discover's flagship product and the highest-intent entry point for most visitors.
No copy changed. No iconography changed. No layout changed. This is a pure ordering test, which matters for how we should interpret it: any lift or drag observed is attributable almost entirely to position, not to messaging or visual weight.
Why Position Alone Moves Behavior
Serial position effects are well documented in navigation research — users scan left-to-right (or top-to-bottom) and disproportionately engage with the first two or three items before attention decays. Optimizely's field notes on A/B testing call out navigation menu structure specifically as a lever with outsized influence on engagement, precisely because it's the first decision architecture a visitor encounters.
For Discover, that means the current default — Online Banking in slot two — is likely capturing clicks that Personal Loans would otherwise get, purely on the strength of position, not necessarily user intent. If Personal Loans is a strategic growth priority (margin, LTV, or portfolio diversification away from card-only revenue), that's a real opportunity cost worth quantifying.
Running the ICE Math
Framing this with Impact, Confidence, Ease:
- Impact: Moderate. Homepage nav clicks are a top-of-funnel signal, several steps removed from a funded loan. Even a strong CTR lift on the icon needs to survive the loan application flow, credit decisioning, and funding steps before it shows up as revenue. I'd model this as a driver of application starts, not originations, in the first read.
- Confidence: Reasonably high that CTR on Personal Loans will lift when it moves up a slot — serial position effects are one of the more reliable findings in UX research. Lower confidence on whether that CTR lift survives down-funnel, since clicking a nav icon is a much lower-commitment action than clicking a loan CTA.
- Ease: Very high. This is a config change in a nav component, not a redesign. No new content, no engineering lift beyond the test harness itself.
That combination — moderate impact, high confidence on the primary metric, near-zero cost — is why this is exactly the kind of test that should be running constantly on a homepage this size, rather than treated as a one-off. Contentful's framing of CRO as an ongoing comparison discipline rather than a single event applies directly here: the real value isn't this one reorder, it's the cadence of testing nav hierarchy as product priorities shift quarter to quarter.
The Confidence-Lift-Risk Tradeoff
Worth being explicit about what this test can't tell Discover on its own:
- Confidence: High that this is a low-noise, high-signal test given the traffic volume a homepage like discover.com receives. Statistical power shouldn't be the bottleneck.
- Lift: The upside is bounded. Reordering three icons won't meaningfully change how many people arrive already intending to check a card balance versus shop personal loans. This test measures marginal attention capture, not demand creation.
- Risk: Essentially none downside-wise. Worst case, Personal Loans clicks stay flat and Discover reverts. There's no plausible scenario where this reorder meaningfully hurts Credit Card or Online Banking engagement, since Credit Card's position is untouched and Online Banking users are typically high-intent, low-navigation-dependent (they're heading to a login flow they already know).
That asymmetry — capped downside, plausible upside — is the profile of a test that should ship regardless of outcome size, because the cost of running it is near zero.
What to Watch If You're Building the Same Test
If a nav-reorder test is on your roadmap this quarter, a few things I'd insist on before calling it:
- Segment by returning vs. new visitors. Returning users who bank online already know where that icon lives and may click it out of habit regardless of position — muting the apparent effect of the reorder for that segment while overstating it for new visitors.
- Track past the click. Icon CTR is a vanity metric if you don't tie it to application starts and, ideally, funded-loan rate. A test that lifts nav CTR by 15% but shows no downstream funnel movement isn't a win, it's noise with a good story attached.
- Watch for cannibalization. If Personal Loans CTR rises and Online Banking CTR falls by a proportional amount, you haven't grown the pie — you've just reshuffled it. That's still useful information if Personal Loans is the higher-value action, but it's a different result than incremental lift.
Workshop Digital's breakdown of CRO testing makes a similar point: the value of A/B testing isn't the test itself, it's the discipline of tying surface-level changes back to a specific business hypothesis you're willing to be wrong about.
The Takeaway
Nav ordering tests are among the cheapest experiments you can run and among the easiest to mis-scope. Discover's test is well-bounded: three items, no copy or design variables, clear hypothesis. If you're auditing your own utility nav this sprint, don't just ask "what should be first" — ask what metric two slots down the funnel you're willing to hold this test accountable to before you ship the winner.
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.