Page Speed and Conversion Rate: Why a Slow Site Costs You Enquiries, Not Just Rankings
Page speed is a conversion rate problem wearing a technical costume. What the Core Web Vitals thresholds actually mean for your enquiries, why more traffic makes the leak worse, and the handful of fixes that are worth doing first.

Most businesses file page speed under "something the developer sorts out". That is exactly why it never gets sorted. Page speed is a conversion rate problem wearing a technical costume, and if your traffic is healthy while your enquiries are flat, it belongs near the top of your list. Nobody abandons a page because a testing tool gave it 47 out of 100. They abandon it because they tapped a button and nothing happened.
The useful shift is to stop reading speed as a score and start reading it as a sequence of moments where a visitor decides whether to carry on.
The three moments that matter
Google's Core Web Vitals are worth understanding, not because they feed a ranking signal, but because they describe those moments better than anything else you have easy access to. There are three, and each has a published threshold: Largest Contentful Paint should happen within 2.5 seconds, Interaction to Next Paint should be 200 milliseconds or less, and Cumulative Layout Shift should stay at 0.1 or below. The targets are assessed at the 75th percentile of page loads, split between mobile and desktop.
Translated out of the jargon, they are three questions every visitor asks without knowing they are asking them.
Has anything useful appeared yet? That is Largest Contentful Paint. Usually your hero image, your headline, or whatever tells someone they have landed in the right place.
Did the page respond when I touched it? That is Interaction to Next Paint. A tap on the menu, a form field, a filter, an add-to-basket button.
Is the page going to stop moving? That is Cumulative Layout Shift. Content jumping around as late-loading images and cookie banners shove it down the screen.
A visitor who cannot answer all three favourably within a couple of seconds has already formed a view of your business, and it is not a flattering one.
More traffic will not fix this
The instinct when enquiries dip is to buy more visits. It is the wrong move and an expensive one. If a slow page loses a fixed proportion of the people who land on it, doubling your traffic doubles the number of people you lose. The leak gets bigger, not smaller.
On paid channels it is worse, because you pay for the click before the page has a chance to fail. Google states plainly that ad quality affects where your ad appears and how much you pay per click, and landing page experience is one of the components it assesses. A slow, awkward landing page does not only lose the visitor you just bought — it makes the next visitor cost more. That is the part most advertisers miss when they audit their Google Ads account and find nothing obviously wrong with the campaigns themselves.
The numbers that exist, and the ones that do not
Be sceptical of speed-to-conversion statistics. The industry recycles a small pool of unsourced claims about how many milliseconds cost how many percentage points, and almost none of them trace back to a primary source or to a business remotely like yours.
What does exist is documented case work. Google's own round-up of Core Web Vitals business impact records Vodafone Italy improving Largest Contentful Paint by 31 per cent and seeing 8 per cent more sales, alongside a set of similar results from other brands. That is useful evidence that the relationship is real. It is useless as a prediction of what your site will do. The honest position: faster pages convert better, the size of the gain depends entirely on how bad you were and what you sell, and anyone quoting you a precise figure in advance is guessing.
What to fix first
Most sites do not need a rebuild. They need three or four specific things removed.
Images. The single most common cause of a slow first impression is an enormous hero image served at full resolution to a phone. Compress it, resize it, serve a modern format. Dull work, disproportionate payoff.
Third-party scripts. Chat widgets, heat mapping, review carousels, three separate analytics tags, an orphaned pixel from an agency you stopped working with two years ago. Each one costs you. Open your tag manager and delete anything whose purpose you cannot state out loud.
Reserved space. Layout shift is nearly always fixable by declaring dimensions for images, ads and embeds so the page does not rearrange itself as things arrive.
The cookie banner. It loads early, covers your headline and shoves everything below it. It does more damage to conversion than most people credit it with.
If your site sits on an ageing theme with a dozen plugins fighting each other, the maths sometimes favours a rebuild over another round of patching. That is a decision to make deliberately, though, not a default — and it is the kind of call we work through as part of our web development work.
Measure it where it actually happens
Lab tools run your page on a simulated device in ideal conditions. They are good for catching regressions before release and poor at telling you what your customers experience on a five-year-old Android phone on Manchester city-centre 4G. Field data — real users, real devices — is what you act on.
Then connect it to something commercial. Speed work that is not tied to enquiry volume, form completions or revenue is impossible to defend in the next budget conversation, and it will be the first thing cut. Pick the page that matters most, usually your main landing page or the step immediately before your form, and track what changes there rather than chasing a site-wide average upwards.
That is the whole discipline: treat speed as conversion rate work with a technical implementation, rather than a technical task with a vague commercial rumour attached to it.
If your traffic looks fine and your enquiries do not, we will tell you which of the two is actually broken. Get in touch and we will look at the pages that matter instead of the score out of 100.
