Two businesses offer the same service in the same town. One website appears higher in search and turns more of its visitors into enquiries. Very often the difference is not the design, the copy or the budget. It is that one site loads in a second and the other takes six.
Why speed moves rankings
Google has used page experience signals in ranking for years, and Core Web Vitals made it explicit: how fast your largest content paints, how soon the page responds to a tap, how much the layout jumps around. Sites that fail these get outranked by sites that pass, all else being equal. In local search, where a dozen similar businesses compete for the same three map slots and ten results, all else usually is equal.
Why it moves enquiries even more
Ranking is only half the loss. Mobile visitors abandon slow pages in droves; the probability of someone leaving roughly doubles as load time goes from one second to five or six. Every abandoned load was a person who searched for what you sell, found you, and gave up before your page appeared. You paid for that visitor with all the work that got you ranked, then lost them to a spinner.
Measure yours in two minutes
- Open PageSpeed Insights and run your homepage.
- Read the mobile score, not the desktop one. Your customers are on phones; the desktop score flatters everyone.
- Run your most important service page too. Homepages get optimised; the pages that actually convert often get forgotten.
Mobile above 90 is genuinely fast. Seventy to ninety is average, which means beatable. Below 70, speed is actively costing you rankings and enquiries.
The fixes, ranked by effort
Cheap and quick
- Compress the images. The single most common problem is a 4MB photo behind a heading. Modern formats and sensible dimensions turn megabytes into tens of kilobytes with no visible difference.
- Remove what you do not use. Chat widgets nobody answers, popups, three analytics tools and a heat map. Each one is another download before the page settles.
- Lazy load below the fold. Images further down the page can wait until the reader gets there. One attribute per image.
Structural, and worth knowing about
- The theme and page builder tax. A typical WordPress theme with a page builder ships hundreds of kilobytes of scripts and styles on every page whether that page uses them or not. You can optimise around the edges, but the floor stays high.
- Static beats assembled. Sites generated as plain files ahead of time (the way modern frameworks like Astro work) skip the database round trip entirely and serve from a CDN near the visitor. This is how a page loads in under a second without anyone doing heroics.
The honest summary
If your site is fundamentally sound, an afternoon of image compression and widget pruning often moves a mobile score twenty points. If your site is a heavy theme on shared hosting, you can spend that afternoon every month and never get near the sites built fast from the start. That is not a sales line; it is why we put speed in the foundations checklist rather than the finishing touches.