Yes, a slow website loses you booked work, and the frustrating part is you rarely see it happen. Someone taps your link, waits a beat too long for the page to appear, and backs out before they ever reach your contact form. There is no bounced email, no missed call, no trace in your inbox. The job simply goes to whoever loaded first.
Speed matters because a website is a decision, not a document. A visitor is weighing up whether to trust you with their money and their time, and a page that stalls, jumps around or ignores the first tap chips away at that trust before you have said a word. Google has been clear that speed affects whether people stay and act, which is why it is worth treating as a business problem rather than a technical one.
What Core Web Vitals actually measure
Core Web Vitals are Google’s way of putting numbers on how a page feels to use. There are three of them, and each maps onto a moment in a real visit. The current set is Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
- Largest Contentful Paint (LCP) is how long the main content takes to appear. Google treats 2.5 seconds or less as good. This is the wait a visitor feels before they can even read what you do.
- Interaction to Next Paint (INP) measures how quickly the page responds when someone taps or clicks. A good score is 200 milliseconds or less. It replaced First Input Delay as a Core Web Vital on 12 March 2024, so if your last review predates that, it is out of date.
- Cumulative Layout Shift (CLS) is how much the layout jumps around as it loads. Google treats 0.1 or less as good. High CLS is the reason a thumb lands on the wrong button and the visitor gives up.
You do not need to memorise the thresholds. What matters is that each one describes a place where a real person can quietly decide you are not worth the effort.
How a slow page breaks the enquiry journey
Picture the path a new customer takes. They find you, they wait for the page, they read enough to feel reassured, then they act. Every stage sits on top of the one before it. A slow LCP means they judge you on a blank screen. A sluggish INP means the enquiry form feels broken the moment they touch it. A jumpy layout means they tap the wrong thing and lose their place.
None of this shows up as a complaint. It shows up as an enquiry that never arrives. That is what makes slow sites so easy to ignore and so expensive to keep. The work you can see in your diary is only the work that survived the wait.
It gets worse on mobile, where most people first meet a small business, often on a patchy connection between other things. A page that feels acceptable on your office broadband can be a test of patience on a phone in a car park. If you only ever check your own site from a fast desk connection, you are grading the version almost none of your customers see.
Speed is only half the job. The page still has to point somewhere
Fast loading buys you attention. It does not tell the visitor what to do with it. A quick page that dumps someone onto a wall of text with no obvious next step still loses the enquiry, just a few seconds later than a slow one would.
This is why speed and structure work together. A page that loads fast and then makes the next action obvious is what turns a visit into a booking. If you want to go deeper on that side of the problem, our piece on designing a service website around the next customer action covers how to build every page towards a single clear step. Treat speed as the thing that gets people in the door, and structure as the thing that walks them to the counter.
How to see the problem for yourself
You do not have to guess. Google reports Core Web Vitals for your real visitors inside Search Console, based on how actual people experienced your pages rather than a one-off test. Our guide to Google Search Console walks through where to find that report and how to read it without a technical background.
For a quick spot check, run your busiest pages through a free speed tool on a mobile setting, not desktop. Test the pages that actually earn you work, usually your homepage and your main service pages, not the ones nobody visits. If the tool flags LCP, INP or CLS as needing improvement, you now have a specific list rather than a vague sense that the site feels slow.
What to fix first
Most speed problems on service-business websites come from a short list of usual suspects, and you can make real progress without a full rebuild.
- Oversized images. Photos exported straight from a phone or camera are often far larger than they need to be. Compressing and correctly sizing them is frequently the single biggest win for LCP.
- Heavy add-ons. Chat widgets, booking embeds, tracking scripts and page builders each add weight. Keep the ones that earn their place and remove the rest.
- Layout that settles late. Reserving space for images and banners before they load stops the page jumping and fixes CLS.
- An overloaded homepage. Sliders, video backgrounds and endless sections all slow the first impression. Simpler usually loads faster and converts better.
If your site is built on a tired platform stuffed with plug-ins, there comes a point where patching costs more effort than rebuilding on something lean. That is a judgement call, not a rule, but a site you keep fighting is rarely worth the fight.
Where Kilij fits
We build hand-made websites for UK service businesses with Core Web Vitals in mind, so pages load quickly and hold up on a phone. Alongside the site, our catering software Pala handles the enquiries that come in across WhatsApp, Instagram, email and the website itself. Put together, the aim is simple: more of the visits your fast site earns turn into booked work rather than quietly slipping away.