Above-the-fold testing
'Above the fold' is the portion of a page visible without scrolling, which varies by viewport. Above-the-fold testing experiments with what occupies that first screen — headline, value proposition, primary CTA, hero media — because it sets first impressions. Measure it with scroll-depth and visibility events rather than assumptions, since the fold position differs across devices and the goal is the downstream conversion, not the click alone.
The fold is a range, not a line
There is no single fold: phones, laptops, and large monitors reveal different amounts before any scroll. Above-the-fold testing therefore optimises the first screen for the viewports that matter most to your traffic, usually starting mobile-first. The content that lands there — the headline, the core benefit, the primary action — disproportionately shapes whether a visitor stays.
- Fold position depends on viewport and device
- First screen sets the value proposition fast
- Optimise for your dominant viewport mix
Measure, don't assume
Instrument scroll-depth and element-visibility events so you know what users actually saw, then run a proper A/B test on the variant first screens. Judge variants on the downstream conversion, not on above-the-fold clicks alone — a louder first screen that wins clicks but loses checkouts is not a win. Pair quantitative scroll data with qualitative review to understand why a layout works.
The long-debated 'everything must be above the fold' rule is contradicted by scroll-tracking evidence; let data decide.
How it appears in analytics and logs
Low scroll-depth past the fold suggests the first screen failed to earn the scroll; high engagement above with weak conversion suggests a content-CTA mismatch.
Diagnostic use case
Test which message and CTA occupy the first visible screen, validating with scroll-depth data so changes are judged on conversion, not opinion.
What WebmasterID can help detect
WebmasterID's first-party scroll and CTA events show how far visitors get and whether the above-the-fold CTA earns clicks.
Common mistakes
- Cramming everything above the fold instead of earning the scroll.
- Optimising for one viewport and ignoring the device mix.
- Judging the test on above-fold clicks rather than conversion.
Privacy and accuracy notes
Scroll-depth and visibility tracking use aggregate interaction events; no personal data is required to measure fold engagement.
Related pages
- Sticky CTA testing
A sticky (fixed-position) CTA stays pinned to the viewport — a header bar, footer button, or floating button — so the primary action remains reachable however far the user scrolls. On long pages this can prevent users from losing the action; the cost is screen real estate, especially on mobile, and the risk of distraction. Test it on conversion with scroll and click data, balancing reach against clutter.
- Copy and CTA testing
Copy and call-to-action (CTA) tests change words — a headline, a value proposition, button text — and measure the effect on conversion. The discipline is to isolate the copy change, and to judge it on the downstream macro conversion, not just the click, since punchier wording can raise clicks while lowering completions. This page frames honest copy testing.
- Heatmaps overview
A heatmap aggregates many users' interactions into a colour-coded overlay on a page: click maps show where people tap, scroll maps show how far down they read, and move maps show pointer movement. They are a quick qualitative read on attention and friction, but they aggregate away context and can mislead on responsive layouts and dynamic content.
- CTA tracking docs
Track whether the first-screen CTA earns clicks.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.