Average time spent on a landing page: what to measure, and when to worry

Average time on page is a reassuring metric: a single number, easy to track, that seems to measure interest. In reality it's one of the most ambiguous numbers in analytics. A visitor who stays four minutes may be gripped by your argument — or lost, hunting for information they can't find. A visitor who leaves in twenty seconds may have rejected your offer — or found exactly what they came for and clicked the CTA. Before optimising the number, you need to understand what it actually measures, and what research says about how people consume pages.

What research says about dwell time

The most useful finding comes from a study by Liu, White and Dumais, presented at the SIGIR conference in 2010, which analysed dwell time on more than 200,000 web pages using browsing logs from over 10,000 users. Their conclusion: time on page follows a Weibull distribution with "negative aging" — in other words, the first seconds are by far the deadliest. A page goes through ruthless triage on arrival: a large share of visitors leaves almost immediately, but the longer a visitor stays, the more likely they are to keep staying (see the study). For a landing page, the consequence is direct: the battle for time on page is won in the first ten seconds — the headline, the visible promise and the load speed matter more than everything that comes after.

Why "average time" is a loaded number

• The average flattens the distribution. If half your visitors leave in five seconds and the other half read for three minutes, the average shows ~1 min 30 — a figure that describes no real visitor. Look at the distribution, not the mean.
• The last screen often isn't counted. Many tools measure time between two pageviews: on a standalone landing page with no next page, visit time can be underestimated or logged as zero depending on the tool. Check how your analytics handles this before comparing numbers.
• An open tab is not a read. The visitor who opens your page, switches tabs and comes back ten minutes later inflates the metric without reading a word more.
• Long time ≠ interest. High time with a low conversion rate often signals confusion: the visitor is hunting for the price, the proof, the button — and not finding them.

The right reflex: cross time with behaviour

On its own, time on page says almost nothing; crossed with two other signals, it starts to talk. Time + scroll depth: long time with scroll stopping at 30% signals a blockage near the top; a full scroll in a few seconds signals skimming without reading. Time + conversion: this is the decisive cross. Short time and high conversion? Your page is efficient — don't make it longer. Long time and low conversion? Visitors are interested but something blocks them before the form — usually an unaddressed objection or a badly placed CTA. A heatmap and session recordings then show precisely where visitors linger and where they drop, far better than an aggregate number.

What's a "good" time by page type?

There is no serious universal benchmark, but the logic is simple: expected time should match the reading time of what's needed to decide. An email capture page with a lead magnet is decided in under a minute: a multi-minute average there would be a symptom, not a win. Conversely, a long sales page for a high-commitment product — a course, a coaching offer like the coach consultant template — takes a serious prospect several minutes to read. The useful comparison is never an external benchmark: it's your own page's trajectory, before and after each change, ideally validated by an A/B test.

Three concrete moves if your visit time looks off

1. Very short time and high bounce: work on the first impression — headline promise aligned with the ad or link that brought the visitor (message match), fast loading, a first screen that states the offer clearly.
2. Long time but few conversions: hunt for the missing objection. No price, invisible guarantee, social proof buried too low — visitors scroll looking for an answer before giving up.
3. Decent time but partial scroll: the break is where the scroll stops. Tighten that section, add a visual relay or an intermediate CTA to restart the read.

Scroll depth: how many visitors actually see the bottom of your landing page?

You polished seven sections, but how many visitors see the seventh? Scroll depth turns that question into a curve: at each section, a percentage of the remaining audience. It's one of the simplest and most decisive diagnostics for reorganizing a landing page.

Let's be precise up front: scrolling isn't reading. A visitor can sweep through the page in two seconds of mouse wheel without absorbing anything, or spend two minutes on the first screen. Scroll depth measures exposure — which sections had a chance to be seen — not attention, which is better read in time spent on the page and in heatmaps, whose scroll maps are in fact the visual rendering of the same data. The three metrics complement each other: scroll says how far, time says how much, the heatmap says exactly where. Survey methodology has studied scrolling closely: a study by Peytchev, Couper, McCabe, and Crawford published in 2006 in Public Opinion Quarterly ("Web Survey Design: Paging Versus Scrolling") compared, across more than 10,000 respondents, questionnaires presented as one long scrolling page versus successive short pages, measuring how the scrolling format changes completion behavior — scrolling isn't a neutral gesture, it's an engagement decision that design can encourage or discourage. The authors extended this work to mobile, where Mavletova and Couper (2014, "Mobile Web Survey Design: Scrolling Versus Paging") show the trade-offs differ on small screens — a useful reminder: your desktop and mobile scroll curves must be analyzed separately.

Three concrete decisions scroll data enables

• Place the CTA where visitors actually are — if half the audience stops mid-page, a single final button works for the other half only; repeat the CTA at the depths still populated (see how many CTAs on a landing page).
• Cut the dead sections — a section almost nobody reaches that doesn't serve the conversion of the most motivated is maintenance cost with no benefit: remove or merge it, and the page gains speed and clarity.
• Prioritize A/B tests by exposure — testing a section seen by 15% of visitors mechanically caps the measurable effect; the scroll curve is one of the best impact criteria for prioritizing your tests.

The 5-second test: checking that a landing page is understood instantly

You know your offer by heart, so your page seems crystal clear to you. The 5-second test breaks that illusion in three minutes, with any guinea pig and zero tools: if a stranger can't say what you sell after 5 seconds, neither can your visitors.

Five seconds might sound arbitrarily short. Research suggests it's actually generous. A study by Lindgaard, Fernandes, Dudek and Brown published in 2006 in Behaviour & Information Technology — with a title that became famous, "Attention web designers: You have 50 milliseconds to make a good first impression!" — showed that the visual appeal judgement of a web page forms in a fraction of a second, and that this snap judgement correlates strongly with the one made after longer examination (see the study). That first aesthetic judgement then colours everything else: work by Tractinsky, Katz and Ikar published in 2000 in Interacting with Computers ("What is beautiful is usable") showed that interfaces perceived as beautiful are also judged easier to use, independently of their actual ergonomics (see the study). In five seconds, a visitor has had ample time to judge the look and read the headline: if the message doesn't land within that window, it won't land.

The method, step by step

1. Prepare the capture: the page's first screen, exactly as it really displays — preferably the mobile version, the one most visitors will see. No scrolling: you're testing what sits above the fold.
2. Pick testers who don't know the offer: three to five people are enough to surface recurring problems. Avoid your co-founders and anyone who watched the page being born.
3. Show the screen for 5 seconds, timed, then hide it. Say nothing while it's displayed.
4. Ask the questions without helping: note the answers verbatim, including the silences and the "uh"s.
5. Repeat after every fix: the test costs three minutes — run it on every iteration of the page.

Heatmaps and session recordings: how to spot (and fix) friction on your landing page

A Google Analytics dashboard tells you 92% of visitors leave your landing page without converting — but never why. Heatmaps and session recordings fill that gap: how to read them, which tools to use, and what they will never replace.

The two get lumped together in conversation, but they answer different questions.

Heatmap vs. session recording: two tools, two jobs

• A heatmap aggregates the behavior of hundreds or thousands of visitors into a single image: where they click (click map), how far they scroll (scroll map), where their mouse lingers (attention map). It gives a statistically solid overview — but an anonymous one.
• A session recording replays one specific visitor's journey, second by second: mouse movements, clicks, hesitations, backtracking. It proves nothing on its own, but it tells a story — and ten recordings watched back to back often surface a pattern no chart would have shown.

Landing page bounce rate: why 80% isn't necessarily a problem

"Our landing page has an 85% bounce rate, it's a disaster." Not so fast: on a single-goal page, where the visitor by design has nowhere else to go, bounce rate doesn't measure what people think it does. Here's how to read this metric on a landing page — and above all, when to genuinely worry about it.

Visitors don't leave a page at a constant rate: the vast majority of abandonments concentrate in the very first seconds. A study by Liu, White and Dumais published in 2010 at the SIGIR conference (see the study), based on the analysis of hundreds of thousands of real dwell times, shows that time spent on a page follows a Weibull distribution with strong "negative aging": the risk of a visitor leaving peaks in the first moments, then drops sharply — a page stakes everything on an initial evaluation phase of a few seconds. The operational translation: a high bounce rate is fought above the fold first — immediate headline clarity, visible promise, fast loading — well before optimising the bottom of the page. That's exactly what the 5-second test checks.

The three diagnostics to cross-check before concluding

• Conversion rate first: a page converting at 8% with an 80% bounce rate is doing its job — the 80% includes the curious and the mistargeted. A page converting at 0.5% with an 80% bounce rate has a real problem. Reference ranges are in our article on the average conversion rate.
• Time on page and scroll next: a bounce after 3 seconds and a bounce after 90 seconds of reading don't mean the same thing. Average time on page and scroll depth separate immediate rejection from last-minute hesitation.
• Actual behaviour last: a heatmap and session recordings show where visitors stop, what they skim and the exact point where they drop off — bounce rate says they leave, the heatmap says from where.

Micro-surveys on a landing page: one question to learn why visitors leave without converting

GA4 tells you that 97% of a landing page's visitors leave without converting, but never why: too expensive, unsure about the offer, just browsing. A single-question micro-survey fills that gap without hurting the experience — as long as you follow a few rules that research has already validated.

The good news is that a single question is enough to get an actionable signal. Psychometric research has specifically tested the reliability of single-item measures on the perceived usability of an online store: Christophersen and Konradt (2011), in a study published in the International Journal of Human-Computer Studies, showed that a single-item measure can reach adequate reliability, validity and sensitivity for assessing an online store's perceived usability, provided the question targets a global judgment rather than a specific detail (see the study). In other words: dropping down to one question from four isn't a measurement compromise — for this type of global judgment ("why are you leaving without taking action?"), one well-chosen question already carries most of the signal.

Designing the question: closed options, never free text

• "Does the price feel right to you?" — useful on a page where the price is visible before departure; answers in 2-3 options (too expensive / reasonable / still comparing).
• "What's missing for you to decide?" — broader but still multiple-choice: more technical detail / customer reviews / a guarantee / a demo / other.
• "Were you looking for something else?" — diagnoses poor targeting or an ad that doesn't match the landing page.
• "Where are you in your decision?" — distinguishes a visitor who isn't ready yet (worth recontacting later) from one who has already decided against the offer.
• An "other" option with an optional text field — never mandatory, but useful for the 5 to 10% of respondents motivated to elaborate.

How many users do you actually need to test a landing page?

"You only need to test with 5 users": Jakob Nielsen's formula has become a product design dogma, applied as-is to landing pages. It comes from a real calculation — but it answers one specific question, not every question you have before a launch.

In 1993, Jakob Nielsen and Thomas Landauer published a mathematical model of usability problem discovery in the proceedings of the CHI’93 conference (Nielsen & Landauer, 1993). Analysing eleven existing studies, they showed that problem detection follows a Poisson process: each additional tester mostly re-finds problems already spotted by earlier ones, with returns diminishing fast. Their calculation produced the number that became a cult figure in interface design — a single tester finds on average 31% of a page's usability problems, five find about 85%, and beyond that, each extra tester costs the same recruiting effort for an ever-smaller gain. A few years later, Nielsen popularised this result as "you only need to test with 5 users," a line that turned into a CRO dogma — including for landing pages. The problem: that dogma answers one specific question, not every question you have before launching a page.

Where the number "5" actually comes from

• 1 tester: about 31% of problems found
• 2 testers: about 52%
• 3 testers: about 67%
• 5 testers: about 85%
• 10 testers: about 97%

Time on page is neither a goal nor a score: it's a thermometer. The only metric that pays is conversion — time helps you understand why it rises or stalls. LanderKit templates are structured for that journey: a first screen built to survive the ten-second triage, then sections that answer objections in the order visitors raise them.