Most business owners judge their website on a fast office connection and a recent laptop. Their customers often see it on a mid-range phone, on mobile data, while doing something else. On that phone, a page that felt instant in the office may take several seconds to show anything useful, jump around as images load, and respond sluggishly when the enquiry button is tapped.
Speed affects two things a business cares about: whether people find you in search, and whether the people who arrive go on to call, enquire or buy. This article explains how Google measures page experience, the usual reasons business websites are slow, and a practical order to fix them.
How Google measures it: Core Web Vitals
Google defines three Core Web Vitals, each measuring a different part of the experience. According to Google's documentation, a page is considered good when, at the 75th percentile of real visits, it meets these thresholds:
- Largest Contentful Paint (LCP): 2.5 seconds or less. How quickly the main content, usually the largest image or block of text, appears.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds when someone taps, clicks or types. INP replaced First Input Delay as a Core Web Vital in 2024.
- Cumulative Layout Shift (CLS): 0.1 or less. How much the page jumps around while loading, for example when a late image pushes a button down just as someone tries to tap it.
The 75th percentile matters. It means the target must be met for most of your real visitors, including those on slower phones and networks, not just on average.
What speed does, and does not, do for search
It is worth being precise here, because speed is often oversold. Google's Search Central documentation says it highly recommends achieving good Core Web Vitals for success with Search, and that page experience aligns with what its core ranking systems seek to reward. It also says Google Search always seeks to show the most relevant content, even if the page experience is sub-par, and that a great page experience can contribute to success where many helpful results are available.
In plain terms: a fast page will not rank for a search it is not relevant to, and a slow page with uniquely useful content can still rank. But where you compete with similar businesses offering similar content, speed is one of the things that can separate you.
Speed will not rescue a page nobody needs. It decides whether the people who do need it stay long enough to contact you.
What speed costs you in enquiries
The search effect is only part of the story. Every second a visitor spends looking at a blank screen or a jumping layout is a chance for them to go back and choose another result. For a business that depends on enquiries, such as a clinic, a training centre, a travel agent or a professional firm, a slow mobile site quietly reduces the number of people who reach the contact form.
Rather than relying on general figures, measure your own: record enquiries or conversions before you improve speed, make the changes, and compare over the following weeks.
Why business websites are slow
The causes are usually ordinary, and most are fixable:
- Oversized images. Photographs uploaded straight from a camera or phone, several megabytes each, displayed at a fraction of that size.
- Too many plugins and scripts. Sliders, chat widgets, multiple analytics tools, social feeds and pop-ups, each adding code that the phone must download and run.
- Heavy themes and page builders. Templates designed to do everything load code for features you do not use.
- Slow or distant hosting. Cheap shared hosting, or servers far from your visitors without a content delivery network.
- Web fonts and layout shifts. Several font files, and images or embeds without reserved space, causing the page to jump.
- No caching. Pages built from scratch on every visit when they could be served ready-made.
How to measure your own site
- PageSpeed Insights shows real-user Core Web Vitals data for your pages where enough data exists, along with a lab test and specific suggestions.
- The Core Web Vitals report in Google Search Console groups your pages by status and shows which need attention.
- Your own phone. Open your key pages on a mid-range Android phone using mobile data, not office Wi-Fi. Watch how long it takes to see the main content and to use the enquiry button.
Focus on the pages that matter commercially: the home page, main service pages, product or course pages and the contact page.
Fixes, in a sensible order
Quick wins
- Resize and compress images, and serve modern formats where your platform supports them.
- Give every image and embed fixed dimensions so the layout does not jump.
- Lazy-load images below the first screen, but not the main image at the top.
- Remove plugins, widgets and tracking scripts nobody uses or reviews.
- Enable caching and compression on the server.
Medium effort
- Use a content delivery network so files are served from closer to your visitors.
- Reduce web fonts to one or two families and weights.
- Delay non-essential scripts, such as chat widgets, until after the page has loaded.
- Upgrade hosting if server response is consistently slow.
Larger changes
- Replace a heavy theme or page builder with a leaner design.
- Rebuild key pages with a modern framework that sends less code to the browser.
- Fix slow interactions caused by heavy scripts running on every tap.
Keep it fast
Websites slow down gradually as content and plugins accumulate. Agree a few simple rules: images are resized before upload, new scripts need a reason and an owner, and Core Web Vitals are reviewed monthly in Search Console. Treat speed as part of maintenance, not a one-off project.
Where RAED fits
We audit and improve the speed of existing websites, and build new ones with performance as a starting requirement rather than an afterthought. We measure before and after so you can see what changed.
Sources
- web.dev (Google), "Web Vitals", last updated 31 October 2024. web.dev
- Google Search Central, "Understanding Core Web Vitals and Google search results", last updated 10 December 2025. developers.google.com
- Google Search Central, "Understanding page experience in Google Search results", last updated 22 September 2026. developers.google.com
