Skip to main content
inconclusive+0.7% lift

Landing Page: Sitewide CTA

Hypothesis

Adding a sitewide CTA back into the desktop nav

CTALanding PageEnergy & UtilitiesCTANavigationundefinedTest ArchiveWeb AnalyticsUsabilityAttention

Test Results

1.26%
Control CR
1.23%
Variant CR
434,312
Sample size
37
Days run
Control1.26%
Variant1.23%

Key Learning

Context: The primary call-to-action on the landing page isn't converting at its potential — design, copy, or placement may be the bottleneck.

What was tested: Adding a sitewide CTA back into the desktop nav

Result: No statistically significant difference was detected. CTA changes that don't move the needle often mean the bottleneck is elsewhere — consider testing the surrounding context or the value proposition instead.

How to Apply This to Your Site

This experiment tested landing page: sitewide cta but produced no statistically significant change. The test was run on a landing page page in the energy & utilities industry. Inconclusive results suggest this particular change may not be a priority — focus testing effort on higher-impact areas.

Before you test: Consider that cta tests typically require large sample sizes to detect small effects. This test ran for 37 days — plan for at least that long.

This result reached 95% statistical confidence, meaning there is a very low probability the observed effect was due to chance. Results at this confidence level are generally considered reliable for making business decisions.

What Was Tested

Adding a sitewide CTA back into the desktop nav

Methodology

Primary Metric
Transactions
Confidence Level
95%
Lift Range
-1.3% to 2.7%

Build On These Learnings

Save your own experiments, spot winning patterns across your test history, and stop repeating what's already been tried.

Related Experiments

Explore More Experiments