Page Speed and Conversion Rate, Explained
Page speed and conversion rate move together because every added second gives a visitor one more reason to leave before they buy, sign up or fill in a form.
Page speed and conversion rate move together: faster pages convert more visitors, because every added second of load time is one more moment where a visitor decides the page is not worth waiting for. The relationship is not small, and it shows up fastest in the first few seconds of load time.
It is also one input into the same testing discipline behind the rest of this cluster — see the A/B testing guide for how to prove a speed fix actually moved conversion rather than assuming it did.
Why does page speed affect conversion at all?
Because waiting is itself a cost the visitor pays before they get anything back. A slow page asks for patience before it has earned trust, and a fraction of visitors will not extend that patience — they leave, and a visitor who left converts at zero no matter how good the page would have been once it loaded.
None of this requires the visitor to consciously notice the delay. Most people who abandon a slow page do not think "this is taking four seconds, I am leaving." They simply stop waiting, often while still on the previous screen, tapping back or closing the tab before the new page has finished painting anything they could read. The cost shows up in the analytics as a bounce, not as a complaint, which is exactly why it is easy to miss without deliberately segmenting for it.
3x higher at 1s vs 5s
That gap was measured across lead-generation sites specifically, and the e-commerce side of the same study found a comparable, if slightly smaller, pattern: faster pages convert noticeably more of the visitors who land on them [1]. The BBC has reported losing an additional 10% of users for every additional second their site took to load, which is the retention half of the same story — a page that never finishes loading cannot convert anyone [2].
Which part of load time matters most for conversion?
The early seconds, disproportionately. Portent's data shows the conversion-rate curve falling fastest between one and three seconds, then leveling off — a page that goes from six seconds to five gains far less than a page that goes from two seconds to one [1]. That has a practical consequence: if your pages already load in three to five seconds, shaving the first second back is worth more than chasing the last one.
| Fix this first | Fix this after |
|---|---|
| The largest image or hero asset above the fold | Below-the-fold images the visitor may never scroll to |
| Render-blocking scripts loaded before the first paint | Scripts that only run after a click or a scroll |
| Server response time on the landing page itself | Response time on pages deep in the funnel |
| Fonts that block text from appearing | Fonts loaded for a footer nobody reads first |
Is a Core Web Vitals score the same as a conversion rate?
No, and treating it as a stand-in for one is a common mistake. Core Web Vitals measures loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint) and visual stability (Cumulative Layout Shift) — three specific, measurable properties of a page [3]. Conversion rate is a business outcome that speed influences alongside copy, design, trust and price.
Passing the thresholds is evidence a page is fast enough to stop losing conversions to speed, not proof it is already converting as well as it could. Treat a vitals fix the way you would treat any other change: as a hypothesis to test, with the conversion number as the actual scoreboard, using the same CRO hypothesis discipline you would apply to a headline or a button.
This is where a lot of speed work gets abandoned partway. A team fixes Largest Contentful Paint, the score turns green, and nobody checks whether the conversion rate actually moved. Sometimes it does not, because the slow element was not on the path a converting visitor actually took, or because something else in the funnel was the bigger constraint all along. Measuring both numbers, not just the vitals score, is what tells you whether the engineering time paid for itself. Our CRO and A/B testing service treats a speed fix the same way it treats a headline test: as a change with a predicted effect, checked against the real number afterward.
How do you know if speed is costing you conversions right now?
Segment what you already have before commissioning anything new. Pull conversion rate by page-load-time band from existing analytics — under two seconds, two to four, four and up — and look at whether the pattern from the industry studies shows up in your own funnel. It usually does.
That check matters most on the pages carrying the most traffic and the least patience: signup forms, where SaaS signup optimization already treats every extra second as a fifth form field nobody asked for, and mobile sessions specifically, where mobile conversion optimization covers the connection and rendering issues that make phones the more fragile half of the funnel. If the slowest band converts visibly worse, speed is worth a dedicated test before anything else on the roadmap.
Questions people also ask
How much does one second of load time really cost?
It varies by site, but the direction is consistent: multiple studies tie slower load times to lower conversion rates, and the drop is steepest in the first few seconds, not the last.
Does page speed matter more for mobile or desktop?
Mobile, generally, because connections are slower and less predictable, and a visitor on a phone has less patience for a page that stalls. Test both, but fix mobile first if you can only do one.
Is Core Web Vitals the same thing as conversion rate?
No. Core Web Vitals measures loading, responsiveness and visual stability. Conversion rate is a business outcome. They are correlated, not identical, which is why a vitals fix should still be validated against the conversion number.
What is the fastest way to know if speed is costing us conversions?
Segment existing analytics by load time band and compare conversion rate across the bands. If the pattern already shows up in your own data, a speed fix is worth testing before you invest in anything more elaborate.
Sources
- Site Speed is (Still) Impacting Your Conversion Rate — Portent (checked 22 September 2026)
- Why does speed matter? — web.dev (Google) (checked 22 September 2026)
- The business impact of Core Web Vitals — web.dev (Google) (checked 22 September 2026)
Find out what speed is costing your conversion rate
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- A/B Testing: The Complete GuideWhat A/B testing is, when your traffic can support it, how to run a split test that holds up, and how to read the result without fooling yourself.
- Mobile Conversion Optimization: A How-To GuideFix mobile conversion by sizing tap targets for a thumb, rebuilding forms for a small keyboard, and testing mobile separately from desktop.
- SaaS Signup Optimization: Cut Trial Drop-OffSaaS signup optimization means shortening the form, deferring the credit card ask, and testing one change at a time instead of redesigning the whole flow.
- What Is a CRO Hypothesis? A Working TemplateA CRO hypothesis names the change, the reason it should work, and the metric that proves it — anything looser is a guess wearing a hypothesis's clothes.