Landing page load time: how many seconds before you lose your visitors?
Published on 18 July 2026 · 8 min read
You polished the headline, the form, the testimonials — and the conversion rate is still low. Before touching the copy, measure something else: how long the page takes to appear. A visitor who clicks an ad or a Google result arrives with fresh intent and very little patience; if the page takes too long to respond, that intent dissolves before they even see your promise. Speed isn't a technical footnote to copywriting — it's the first line of your sales pitch.
What the studies say about speed and conversion
Two studies, run at very different scales, converge on the same conclusion: the relationship between speed and conversion isn't linear — it collapses past a certain threshold.
- Google (mobile study, Think with Google / SOASTA): bounce probability increases by 32% as load time goes from 1 to 3 seconds, and by 90% at 5 seconds. On mobile, 53% of visitors simply leave a site that takes longer than 3 seconds to load.
- Portent analysed more than 100 million page views across around twenty B2B and B2C sites: pages that load in 1 second convert at an average of 39%, versus 1.9% at 2.4 seconds and only 0.6% at 5.7 seconds — a gap of more than 60x between the two ends of the sample.
The exact figures vary by study and by industry, but the pattern is consistent: every second gained under the 3-second mark pays off proportionally more than the last, and every second lost beyond it costs proportionally more than the last. It's not a curve you can smooth over with good storytelling — a visitor who already closed the tab will never read your headline.
The threshold that actually matters: 3 seconds, not 5
Remember two numbers rather than a full dashboard. Under 1 second: the zone where the page feels instant, where the attention captured by an ad or a Google search arrives intact at your promise. 3 seconds: the hard ceiling — beyond it, more than half of mobile visitors have already left before the page even settles. Between the two, every tenth of a second gained translates into visitors who stay long enough to read your headline. Treating "under 1 second" as the goal and 3 seconds as the line never to cross gives you a clear target, including one you can hand to a developer.
Why so many landing pages are slow
Slowness rarely comes from one big problem: it accumulates, script by script, plugin by plugin.
- Sliders and carousels on the homepage: several full-width images loaded at once, often uncompressed.
- Multiple web fonts pulled from a third-party server, each adding a request and a delay before the text renders.
- Stacked third-party scripts: a Meta pixel, a Google Ads pixel, a chat widget, a heatmap tool, an exit popup — each adds its own network call, sometimes several hundred milliseconds on its own.
- Generic themes and page builders (Elementor, Divi and similar) that load the CSS and JavaScript for dozens of unused features on top of what the page actually displays.
- Unoptimised images: photos exported straight from a camera or a stock library, never resized or converted to a modern format.
- Cheap shared hosting, which responds slowly whenever it shares resources with other sites at the wrong moment.
This is also one of the clearest points in our Next.js vs WordPress for a landing page comparison: a slow WordPress site is almost never a fatality of the CMS itself, but the direct consequence of stacked plugins and a generic theme — a structural problem no one-off tweak fixes for good.
How to measure your page's real speed
Don't trust your own impression when opening the page on your office computer over fibre: that isn't the condition most of your visitors are in. Three checks are enough:
- PageSpeed Insights (Google's free tool): gives a score and the three Core Web Vitals that matter — LCP (how fast the largest visible element appears), INP (responsiveness to interaction) and CLS (visual stability while loading). The mobile report matters more than the desktop one.
- GTmetrix or WebPageTest: let you simulate a 4G connection instead of office wifi, and see precisely which resource (image, script, font) is blocking the render.
- A manual test on 4G, phone in airplane mode then mobile data turned back on: nothing replaces the real experience of an impatient visitor.
The levers that actually make a difference
Roughly in order of impact, from the most rewarding to the most marginal:
- Images: compress them, resize to the size actually displayed, convert to WebP or AVIF, and defer loading (
loading="lazy") for anything below the first screen. This is almost always the fastest win to get. - Fonts: stick to one or two families, self-host them instead of calling a third-party server on every visit, and use
font-display: swapso text renders immediately in a fallback font while loading. - Third-party scripts: audit every tracker and widget. A poorly loaded live chat or ad pixel can add one to two seconds on its own; load them deferred (
async/defer) and drop the ones whose data nobody looks at anymore. - Static generation: a page pre-built and served from a CDN generally responds much faster than one assembled on the fly by a CMS and its plugins on every visit.
- Hosting: for a page whose job is to convert, entry-level shared hosting is rarely the right trade-off against the cost of the traffic feeding it.
What not to sacrifice for a few extra milliseconds
Chasing speed can easily go too far: stripping a page of its testimonials, product photos or trust badges shaves off a few milliseconds and loses far more in persuasive power. The goal isn't the lightest possible page, but the fastest page given what it needs to convince — see the 9 sections of a landing page that converts for what should stay. Optimise the weight of images and scripts, not the content that sells.
The shortcut: start from an already fast foundation
The biggest speed win doesn't come from fine-tuning after the fact, but from the technical foundation you choose in the first place. LanderKit templates are pre-generated Next.js pages (no CMS, no plugins, no server call on every visit), with images already optimised and no superfluous script — the most common baseline for clearing 90 on PageSpeed Insights without touching a thing. This matters especially on a single-product ecommerce page like our ecommerce product template, where every visitor who abandons during load is a lost cart — you can test its real-world speed on the live demo. The same logic applies to a high-volume waitlist page like our SaaS waitlist template, where speed directly determines how many signups you collect before launch.
Speed is just one lever of a converting landing page, but it's the one that gates all the others: a perfect form or an irresistible CTA are worthless if half your visitors already left before seeing them. For the full picture, read our guide on 12 concrete levers to increase your landing page conversion rate.
FAQ
Frequently asked questions
What load time should a landing page aim for?
Aim for under one second, and treat 3 seconds as a ceiling you never cross: beyond it, studies (Google) measure that more than half of mobile visitors leave the page. Measure with PageSpeed Insights on mobile, not on a comfortable office connection.
Does load time really affect SEO?
Yes, both directly and indirectly. Core Web Vitals (LCP, INP, CLS) are an official Google ranking factor, even if its weight stays moderate next to content relevance. Indirectly, a slow page raises the bounce rate, a signal Google reads as a sign of poor experience.
Does a chat widget or a tracking pixel really slow the page down?
Yes, often more than people think: a poorly loaded live chat widget or ad pixel can add one to two seconds on its own, especially on mobile. Best practice is to load it deferred (async/defer) and regularly audit which scripts are still actually useful.
Should you pick Next.js over WordPress just for speed?
Speed isn't the only criterion, but it carries real weight: a pre-generated Next.js page starts without a database or a plugin engine to query on every visit, which explains the performance gap seen in practice. The full comparison (cost, security, maintenance) is in our Next.js vs WordPress for a landing page article.
How do I know if my current landing page is too slow?
Run it through PageSpeed Insights (free) and check the mobile report: a score under 50 or an LCP beyond 2.5 seconds signals a problem to fix first. Follow up with a manual test on your phone over 4G, without wifi, to feel what an impatient visitor actually experiences.
Read next
Related articles
- Loading screens (skeleton screens) on a landing page: premium effect or conversion killer?A loading animation before the hero appears gives the impression of a "polished" site. Most of the time, it's also an obstacle deliberately placed between your visitor and your value proposition. What research says about perceived wait time, and the rare cases where a loading screen genuinely helps conversion.
- Speed-to-lead: how fast should you follow up on a lead from your landing page?The form is filled in, the lead sits in your inbox: the hard part looks done. In reality, everything is decided now — research shows the window to turn that contact into a booked call is measured in minutes, not days.
- Form abandonment: measuring and reducing it on a landing pageA visitor who starts filling in your form has already covered 90% of the journey: they clicked, read, and decided to act. Losing them at that step is the most expensive leak in your funnel — and the most fixable, because form abandonment can be measured field by field and its causes are well documented. The full method, from measurement to fixes.