Nobody has ever bought because a page was long, and nobody has ever left because a page was short. They buy when every question they had was answered before they reached the button, and they leave when one was not. Length is the by-product of that, not a strategy. Here is how awareness, price and commitment set the number of questions, what a long page has to contain to earn its length, and the order that lets a visitor stop reading the moment they are ready.
The long-versus-short debate persists because both sides have examples that work. A one-screen page converts beautifully for a free tool from a known brand; a page that scrolls for minutes converts beautifully for a four-figure course from a stranger. Both are right, because neither length caused the result. The page was as long as the number of things the visitor needed to know before acting, and no longer.
So the useful question is not "how long should my page be" but "how many objections stand between this visitor and this action." Count those, answer each one once, in the order the visitor raises them, and the page is finished. A short page for an offer with many objections is not clean, it is silent at the moment doubt appears. A long page for an offer with few objections is not thorough, it is a visitor scrolling past the button looking for the catch.
Most pages we score get this wrong in a specific way: they are long in words and short in answers. Three sections restate the benefit, nothing addresses "what if it does not work for my case," and the call to action is reached by people who have been told the same thing five times and the thing they were worried about zero times.
If you want to know which questions your page leaves open, a landing page audit scores objection handling alongside the other eleven conversion dimensions and ranks what is missing.
Three things about the visitor and the offer decide how much the page has to say. Rate your situation on each before you write a section.
A visitor who already knows your product and just needs the link has one question: where is the button. A visitor who knows the problem but not that a solution exists has to be walked from the problem to the category to you. The less the visitor knows on arrival, the more the page has to teach, and teaching takes space. Traffic source is the proxy: branded search and email are high-awareness; cold social and display are low.
Price is the size of the mistake if the visitor is wrong. A free download costs nothing to regret, so the page needs almost no reassurance. A purchase that would need an explanation to a partner or a finance lead needs the page to pre-write that explanation. As price rises, the visitor raises more objections, and each needs an answer on the page or in a call, and a page is cheaper than a call.
Separate from price: how hard is this to undo, and how much of the visitor's own effort does it demand? A monthly plan they can cancel is low commitment even if not cheap; a migration of all their data is high commitment even if free. Switching costs, setup time, team adoption and lock-in all raise the number of "what happens if" questions, and every one of them belongs on the page.
A long page is long because it contains answers, in the visitor's words, to the things that stop them. "Does this work for a team my size?" gets a section that names the size and shows a customer at it. "What if I already use something else?" gets a section on switching, with how long it takes. "What happens after I pay?" gets the first week described in plain steps. Each of those earns its scroll.
Padding is everything else: the second way of saying the benefit, the feature grid with no consequence attached, the stock-photo band with a slogan, the values section, the "why us" that is really "about us." Padding does not just waste the visitor's time; it sits between a question and its answer, so a visitor scrolling to find out whether you handle their case gives up before they reach the section that says yes.
The test for any section is to name the objection it answers. If you cannot write it as a question a real visitor would ask, the section is padding regardless of how well it is designed. If you can, keep it, and make sure the heading contains the question so a scanning visitor can find it.
On a long page, order matters more than length. The visitor should be able to leave for the button at any point and never feel they missed something they needed. That means objections appear in the order they arise, and the call to action repeats after each cluster.
The headline states the change, the subhead says for whom and how, and one specific piece of proof sits beside the button. The visitor who already knows they want this converts here; everyone else now knows what the rest of the page is arguing for.
Before explaining the product, show that you understand the situation the visitor is in, in their language. This is where low-awareness traffic catches up: they recognise themselves and decide the page is worth their time.
Three or four steps from signing up to the first result. This answers "what do I actually have to do," which is the first objection for anything with setup. Screenshots of the real product beat illustrations of it.
Now the testimonials, case summaries and results, each tied to a specific type of customer. Place the proof that answers "people like me" here, and keep one quote back to sit beside the final button.
Every remaining question gets a short section with the question as its heading: switching, team size, data, support, what happens if it does not fit. This is the block that makes the page long, and it is the block that earns the length.
What is included, what it costs, what the terms are, what happens next. No surprises left for the checkout. A visitor who reaches this section has done the work; do not make them hunt for the answer.
Repeat the promise in one line, place the strongest quote beside the button, and label the button with the outcome. The visitor who read everything is now out of questions; make the next step unmistakable.
Cutting is not deleting sections until the page looks short. It is removing everything that is not an answer and merging answers that repeat.
Go through the page top to bottom and write, next to each section, the objection it exists to resolve. Sections with no question are the first cut. Sections with the same question are merged into whichever one answers it with proof.
The benefit stated in the hero does not need a second section stating it again with icons. Keep the version with the specific result and delete the one with adjectives. Most pages lose a third of their length here with no loss of information.
If the pricing objection arises at the first screen for your audience, the pricing answer cannot wait until the bottom. Reorder so each answer appears where the question would form; a page often gets shorter just because the visitor stops scrolling to hunt.
Within a section, keep the sentence that contains the fact and delete the sentences that set it up. "Switching takes one afternoon; here is the importer" does not need a paragraph on how painful switching usually is.
Most visitors read on a phone, where every section is twice as tall. Open the live page, scroll at reading speed, and note the moment you would leave. That moment is either a missing answer or a stretch of padding; fix whichever it is.
A short page wins when the visitor arrives with almost no questions. That happens in a few recognisable situations: the traffic is warm, as with your own email list or branded search; the ask is small, as with a free tool, a template, a waitlist, or a trial that needs no card; the product is already understood, so the page is a confirmation rather than an argument; or the decision has effectively been made elsewhere, such as a referral from someone the visitor trusts.
In those cases every extra section costs attention and gives nothing back. The page is the promise, one line of proof, the button, and perhaps a single line that removes the one remaining doubt.
The mistake in the other direction is just as common: a short page for a high-price, high-commitment offer to cold traffic, built because a famous page in another category is short. That page is not clean. It is leaving every objection to the visitor's imagination, and the imagination is not on your side.
The arrangement of those few sections is covered in our guide to landing page structure which walks through what each section has to do and in what order.
Answer these before adding or removing a single section.
A landing page should be exactly as long as the number of questions the visitor needs answered before acting, and no longer. Three variables set that number: how much the visitor already knows on arrival, how much the offer costs, and how hard it is to undo or how much setup it demands. Warm traffic, a small ask and a low commitment mean a short page with the promise, one proof and a button. Cold traffic, a high price and a real commitment mean a long page where each objection gets its own section. Count the objections first, then let length follow.
Neither length converts better in general, because length does not cause conversion. Pages convert when every doubt the visitor has is resolved before they reach the call to action. A long page converts better when the offer raises many objections and the page answers each of them once with evidence; a short page converts better when the visitor arrives nearly decided and extra sections only delay the action. A long page full of restatements and feature grids converts worse than a short one, because it is long in words and short in answers.
A long landing page contains answers, in the visitor's own words, to the specific things that stop them from acting: whether it fits their size, how switching works, what happens after payment, what support looks like. Each section can be labelled with the question it resolves. A padded page is long because it repeats the benefit, adds feature grids without consequences, inserts slogans over stock images and includes sections about the company rather than the visitor. Padding sits between questions and answers, so visitors scrolling for reassurance give up before reaching it.
Label every section with the objection it answers; cut sections that have no question and merge sections that share one. Delete restatements of the benefit, keeping the version with a specific result. Move each remaining answer to the point where the visitor would raise the question, which often shortens the page simply because people stop hunting. Within sections, keep the sentence that holds the evidence and remove the sentences that set it up. Finally, read the live page on a phone at scrolling speed and fix the first spot where you would leave.
Run your page through the same diagnostic. The free preview takes about a minute — no signup.
Audit my page