CRO Glossary
Above-Fold vs In-Page Testing
A test design comparing changes made to content visible on load versus changes made further down the page.
This refers to structuring an experiment (or a portfolio of experiments) so that hypotheses about immediately visible page elements are isolated from hypotheses about content a user only sees after scrolling or interacting further. It's less about one specific UI element and more about a testing strategy: deciding where in the page's information hierarchy an intervention lives, and designing measurement so you can attribute lift to the right zone.
Teams care about this distinction because the visible viewport and the rest of the page usually serve different jobs in the funnel — the initial view handles orientation and hook, while in-page content handles persuasion, objection handling, and proof. Mixing changes across both zones in a single variant makes it impossible to tell whether a lift came from the headline the user saw instantly or the testimonial they scrolled to see thirty seconds later.
Note the difference from a simple layout redesign test: here the goal is attribution and prioritization, not just visual redesign. Teams often run this as two sequential or parallel tests — one isolating a change to the immediately visible zone, another isolating a change further down — then compare lift and engagement (e.g., scroll depth, time-on-section) to decide where future testing effort is best spent.
For example, a SaaS pricing page might test a shorter, benefit-led headline in the initial view while simultaneously testing an expanded FAQ section further down. Reporting each change's lift separately, rather than as one bundled variant, tells the team whether users are converting on the strength of the hook or the strength of the supporting detail — which shapes where the next quarter's optimization backlog focuses.
Related 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 this in the wild
ABWatcher watches how top teams apply above-fold vs in-page testing.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.