Above-the-fold teardown: the 7 conversion leaks on your first screen

The decision is made before the scroll. A visitor lands on your page, spends a few seconds with whatever is visible without scrolling, and either commits to going further or leaves. Everything below the fold (your features, your testimonials, your pricing, your FAQs) only gets seen if the first screen earns it.

That is the observable shape of how people use the web. What is less obvious is that the first screen fails in a small, predictable set of ways. The same leaks turn up on SaaS homepages, lead-gen landing pages, and e-commerce product pages alike. Once you can name them, the teardown gets faster, the hypotheses get sharper, and the experiments get likelier to move the number. Here are the seven, and the experiment to run for each.

Leak 1: a vague value proposition #

The most expensive above-the-fold problem is a headline that never answers the visitor’s first question: “Is this for me, and what do I get?”

Vague headlines come in a few recognisable forms. The category claim (“The leading platform for modern teams”) describes the product, not the outcome. The clever-but-opaque line (“Work differently”) sounds good in a workshop and means nothing to a first-time visitor. The superlative pile (“Powerful, flexible, and seamless”) is simultaneously true of every competitor, so it differentiates nothing.

The mechanism is simple. If a visitor cannot tell within seconds whether your offer is relevant to their situation, they leave, and they attribute the confusion to you, not to themselves.

The experiment: write three headline variants, each naming a specific outcome, a specific audience, and ideally the trade-off avoided (“without X”). Run an A/B test on the headline and sub-headline only: no other changes, so the result is clean. Measure a downstream conversion event (trial, demo, purchase), not clicks alone. If traffic is too thin for a clean test, run a five-second test with five people from your target audience and ask each to recall what the product does. Accuracy of recall is your signal.

Leak 2: competing or too many CTAs #

A page with multiple primary CTAs is a page with no primary CTA. When you give a visitor three equally prominent buttons (“Start free trial,” “Book a demo,” “Watch the video,” “See pricing”), you have handed them the prioritisation decision. Visitors do not want to prioritise. They want to be guided.

The leak is cognitive. The visitor spends decision energy on which action to take rather than on whether to take the one you actually want. More options at equal visual weight reliably reduces total action-taking.

The fix is not always to delete options. It is to establish hierarchy. One primary CTA gets the dominant treatment: colour, size, placement. A secondary action, if genuinely needed, becomes a quieter text link or ghost button. That hierarchy is your recommendation to the visitor, made visible.

The experiment: strip the first screen to a single highest-intent CTA. If your analytics show a secondary action driving real conversion, test demoting it to a text link rather than removing it outright. Measure the primary conversion event, not CTA clicks: a button can earn more clicks while the page converts less.

Leak 3: no proof near the decision #

Trust has to be earned at the moment it is needed, not somewhere below the fold most visitors will never reach.

Imagine a SaaS pricing page. The headline makes a promise, the CTA asks for a commitment, and the nearest social proof is a testimonial block five scrolls away. The visitor is being asked to trust before they have been given a reason to. That gap between claim and proof is exactly where conversions leak.

The principle (consistent with Nielsen Norman Group’s work on how people scan pages) is that credibility cues placed adjacent to the primary CTA outperform the same cues positioned elsewhere. A customer logo bar directly under the headline, a one-line metric beside the CTA, or a short quote tied to the precise outcome the headline promises all close the trust gap at the moment it matters.

The experiment: move your strongest proof element (one real quote, one specific metric, one recognisable logo bar) into the first screen, directly adjacent to or beneath the primary CTA. Keep everything else unchanged. Measure downstream conversion. If you do not yet have proof worth placing there, social proof that persuades covers what actually moves people versus what reads as filler.

Proof placed next to the decision does work. Proof buried below the fold is decoration.

Leak 4: the form asks for too much #

If your first-screen conversion action involves a form (a sign-up, a lead capture, a demo request), every field is a tax. The visitor is doing quiet arithmetic: is what I get worth what I am giving up?

Say a lead-gen form asks for first name, last name, email, phone number, company name, company size, job title, and how they heard about you. That is eight fields before a visitor has seen a single proof of value. The Baymard Institute’s research on checkout abandonment finds form length to be a consistent driver of abandonment, and the same dynamic plays out on lead-gen and SaaS sign-up forms.

The harm of unnecessary fields is not just the time they cost. It is the signal they send: “We need a lot from you before we will help you.” That triggers proportional hesitation.

The experiment: identify the minimum data required to deliver value on the next step: not what the CRM would like, not what the sales team prefers for enrichment, but what the next step actually needs. Cut every field beyond that. Run the reduced form against the full one, and collect the rest progressively once you have delivered something worth staying for. The friction audit is a structured way to find these taxes across the whole flow.

Leak 5: slow mobile LCP #

Largest Contentful Paint (LCP) measures how long it takes for the largest visible element to render: usually the hero image, the headline block, or a video thumbnail. If that element takes more than the recommended 2.5 seconds to appear on a mobile connection, a meaningful share of your visitors never see the page they were meant to convert on.

For consumer and SMB-facing products, mobile traffic frequently exceeds half of all visits. A slow LCP is therefore a conversion tax applied to your largest segment before a single word of your copy is read.

Page speed and conversion covers the full picture. For the first screen specifically, the high-priority checks are: hero image format and size (WebP, sized for mobile viewports), render-blocking scripts in the <head>, and LCP elements that have been lazy-loaded by mistake. Run PageSpeed Insights against your mobile score; an LCP above 2.5 seconds is a leak to fix before any messaging experiment, because it caps the audience every other test can reach.

The experiment: measure current mobile LCP and fix the single highest-impact issue, typically hero image weight or a render-blocking resource. If you cannot tie conversion directly to LCP yet, compare bounce and engagement on mobile sessions before and after the fix.

Leak 6: the layout breaks on mobile #

A related but distinct problem: the page loads fast enough, but the first-screen layout on mobile is not the layout that was designed. The hero image crowds out the headline. The CTA sits half off-screen. The sub-headline wraps to four lines and buries the message. Desktop font sizes render as a wall of undifferentiated text at 320 pixels.

This is more common than teams realise, because QA usually happens on whatever device the designer is holding. Emulators help; testing on real devices across the viewport range your analytics actually show is the only reliable signal.

The experiment: check the first screen on at least five real devices or viewports spanning your traffic, and treat every layout failure as a bug rather than a polish item. Then watch a session-replay segment of mobile-only traffic and study the first ten seconds, and compare scroll-depth heatmaps for mobile versus desktop to see whether mobile visitors abandon before the first fold. How to read a heatmap and session replay: what to look for explain how to interpret both without sinking hours into low-signal footage.

Leak 7: distractions (carousels, autoplay, nav clutter) #

The first screen often competes with itself. A rotating carousel cycles through four value propositions, none read in full. An autoplaying background video pulls the eye off the headline. A navigation bar with twelve links hands every visitor twelve reasons to go somewhere other than the conversion action.

Each element has a surface rationale. The carousel accommodates every stakeholder’s priority. The video shows the product. The nav aids discoverability. The problem is that these rationales optimise for internal consensus, not for visitor decision-making.

Carousels in particular are well-studied. Nielsen Norman Group has documented that users rarely interact with panels beyond the first and that auto-advancing carousels are largely ignored. The attention you believe the carousel captures is mostly being lost.

The experiment: replace the carousel with a single strong static hero (best value proposition, one CTA, one proof element) and run it against the carousel control. This is a high-confidence bet: the mechanism is clear and the direction of effect is consistent across the research. For navigation, test a variant with the primary nav simplified or hidden: a minimal sticky header, or none at all on dedicated campaign pages. Measure the downstream conversion event, not time on page.

The seven leaks at a glance #

Running the teardown: a repeatable process #

You now have seven leaks. You will not fix all seven at once. Running seven experiments in parallel is not a programme, it is noise. The right move is to triage, then sequence.

Use ICE scoring for the ranking and the CRO process in five steps for the loop around it. The most common ICE error is letting cheap, low-impact wins crowd out the changes that actually move the number. Do not let ease inflate trivial work.

Frequently asked questions #

Where exactly does the fold sit?

There is no fixed pixel. The fold is whatever is visible without scrolling on a given device, and it differs across phones, laptops, and monitors. Design and test against the most common viewport in your own analytics rather than a single assumed height. And because mobile usually dominates, treat the mobile first screen as the one that matters most.

Should I run all seven experiments at once to move faster?

No. Concurrent tests on the same first screen interfere with each other and muddy attribution, and a flood of half-evidenced changes is hard to learn from. Triage, ICE-score, and run the top leaks as clean single-variable tests. Sequential compounding beats parallel noise.

What if my traffic is too low for statistically clean A/B tests?

Lead with the leaks whose mechanism is strongest and least dependent on your numbers: a vague headline, competing CTAs, a slow LCP, a broken mobile layout. Fix the highest-ICE item on the best available evidence and measure before-and-after on your primary metric. See sample size and test runtime for what your traffic can and cannot support, and statistical significance without fooling yourself before you call a winner.

Is above-the-fold optimisation still worth it if people scroll now?

Yes. People do scroll, but only when the first screen gives them a reason to. The first screen is the filter that decides who reaches the rest of your argument, so it is the highest-leverage section on the page, not a relic of no-scroll browsing.

Every visitor on your first screen has already expressed intent: they clicked an ad, followed a link, searched a term. The page’s only job is to meet that intent. Most pages dissipate it. Find the leaks, run the experiments, and convert more, guess less.