Nobody enjoys waiting for a web page. A customer standing in a parking lot with one bar of signal, searching for a locksmith, will not wait for your site to finish loading. They will tap the next result. A slow website quietly loses calls, bookings and sales, and it can hurt your visibility in search as well.
Google measures real-world website experience through a set of metrics called Core Web Vitals. The name sounds technical, but the ideas behind it are simple: how quickly the main content appears, how quickly the page responds when you tap, and whether things jump around while loading. This guide explains each one in plain English, shows you how to test your own website and lists the practical fixes that make the biggest difference for small business sites.
Why website speed matters to a local business
Speed matters for three reasons.
It affects customers. People are impatient, especially on mobile. A page that takes too long to show anything useful makes visitors leave, and those who stay are more likely to give up before filling in a form or calling.
It affects advertising results. If you pay for clicks from Google Ads or social media, every visitor who leaves before the page loads is money wasted. Faster landing pages convert more of the traffic you already pay for.
It can influence search visibility. Google has said that page experience, including Core Web Vitals, is one of many signals it uses in ranking. It is not the most powerful factor, and great content still matters most, but when two pages are otherwise similar, a faster and more stable one has an advantage. Speed also supports your wider local SEO efforts.
The three Core Web Vitals explained
Largest Contentful Paint (LCP): how fast the main content appears
LCP measures how long it takes for the biggest visible element, usually a hero image, a large heading or a banner, to appear on screen. It reflects how quickly the page feels useful.
- Good: 2.5 seconds or less
- Needs improvement: between 2.5 and 4 seconds
- Poor: more than 4 seconds
Interaction to Next Paint (INP): how quickly the page responds
INP measures how responsive the page feels when someone taps, clicks or types. If a menu takes a moment to open or a button seems to ignore a tap, INP is probably poor. It replaced an older measure called First Input Delay in 2024.
- Good: 200 milliseconds or less
- Needs improvement: between 200 and 500 milliseconds
- Poor: more than 500 milliseconds
Cumulative Layout Shift (CLS): how stable the page is
CLS measures unexpected movement. You have probably tried to tap a button just as an advertisement loaded above it and pushed everything down. That is layout shift, and it is frustrating.
- Good: 0.1 or less
- Needs improvement: between 0.1 and 0.25
- Poor: more than 0.25
Google assesses these numbers at the 75th percentile of real visits, which means that most of your visitors, not just the lucky ones, should get a good experience.
How to test your website
You do not need to be a developer. Use these free tools:
- PageSpeed Insights: enter your page address and get results for mobile and desktop, along with a list of suggested improvements. It shows both real-user data (when enough visits exist) and a lab test.
- Google Search Console: the Core Web Vitals report groups your pages into good, needs improvement and poor, based on real visitors over time.
- Lighthouse in Chrome: built into Chrome’s developer tools, useful for repeat testing while you make changes.
Test your most important pages: the homepage, your main service pages and any landing page you send ad traffic to. Always check the mobile result first, because that is where most problems appear, and compare results over several runs since scores can vary.
Remember the difference between field data, collected from real visitors, and lab data, simulated in a controlled test. Field data is what Google uses for Core Web Vitals, while lab data helps you diagnose problems.
The most common causes of slow small business websites
Most speed problems come from a short list of culprits:
- Oversized images, often photos straight from a camera or phone.
- Too many plugins, widgets and scripts.
- A cheap or overloaded hosting plan.
- Heavy page builders and themes that load far more code than needed.
- Third-party scripts for chat, analytics, advertising and social media.
- Custom fonts loaded poorly.
- No caching.
- Embedded videos and maps that load immediately.
The good news is that a few focused fixes often produce big improvements.
Fix 1: Optimize your images
Images are usually the largest files on a page, and the hero image is often the LCP element.
- Resize images to the size they are displayed. A 4,000 pixel wide photo shown at 800 pixels wastes bandwidth.
- Compress them with an image optimization tool or plugin.
- Use modern formats such as WebP or AVIF, which are smaller than JPEG at similar quality.
- Lazy load images that are below the fold so they only load when needed. Do not lazy load the main hero image, since that delays LCP.
- Set width and height attributes so the browser reserves space and avoids layout shift.
- Serve responsive images so phones download smaller versions than desktops.
Fix 2: Tame fonts
Fonts can delay text and cause shifts. Use as few font families and weights as you can, host them on your own server where possible, preload the most important font file and use a `font-display: swap` setting so text appears immediately in a fallback font while the custom one loads. Using a good system font stack costs nothing and loads instantly.
Fix 3: Reduce third-party scripts
Every chat widget, tracking pixel, social feed and tag adds code the browser must download and run. Audit what is on your site and remove anything you do not use or whose value is unclear. Load the remaining scripts asynchronously or after the page is interactive. If you use a tag manager, review it regularly because old tags tend to accumulate.
Heavy scripts are also the main cause of poor INP, since they block the browser from responding to taps.
Fix 4: Clean up code and plugins
If you use WordPress or another content management system, plugins are both a strength and a risk.
- Remove plugins you do not need.
- Choose lightweight themes and be cautious with page builders that add a lot of markup.
- Keep everything updated for security and performance.
- Avoid loading plugin scripts and styles on pages that do not use them.
For small business sites with a handful of pages, a clean, lightweight build is usually faster, easier to maintain and cheaper to host than a bloated one. This is one of the reasons a professionally built website can outperform a template with many add-ons.
Fix 5: Improve hosting and caching
Even a perfect site is slow on weak hosting. Look at how quickly the server responds, often called time to first byte. Good steps include:
- Choosing reliable hosting in a region close to your customers.
- Enabling page caching, so pages are prepared once rather than built for every visit.
- Using a content delivery network (CDN) to serve files from locations near visitors.
- Enabling compression such as Gzip or Brotli.
- Keeping your PHP version and database healthy if you use WordPress.
Fix 6: Prevent layout shift
To keep pages stable:
- Always specify dimensions for images, videos and ad slots.
- Reserve space for cookie banners, announcement bars and embeds.
- Avoid inserting content above existing content after the page has loaded.
- Load fonts in a way that does not cause the text to jump.
- Be careful with animations that move elements instead of fading or transforming them.
Fix 7: Make interactions responsive
For INP, the goal is to keep the main thread free. Reduce the amount of JavaScript, split large scripts into smaller pieces, remove unused code and avoid long tasks that freeze the page. If a menu or form feels slow, test it on a mid-range phone rather than a fast laptop, because many customers do not have the latest device.
Where to start: a prioritized checklist
- Run PageSpeed Insights on your homepage and main landing page, on mobile.
- Fix the LCP element first, which is usually an image.
- Compress and resize all large images.
- Remove unnecessary plugins and scripts.
- Add width and height to images and reserve space for banners.
- Turn on caching and check your hosting quality.
- Retest and compare with the first run.
- Check Search Console after a few weeks to see real-user data improve.
Do not chase a perfect 100 score. Aim for good Core Web Vitals on real visits and a page that feels fast on a normal phone.
Frequently asked questions
Is a perfect PageSpeed score necessary?
No. The score is a lab estimate. What matters is that real visitors have a good experience and that your key pages pass the Core Web Vitals thresholds.
How long does it take for improvements to show in Search Console?
The report uses real-user data collected over a rolling period, so changes can take several weeks to appear fully.
Will a faster website bring more customers?
Faster pages usually reduce abandonment and improve conversion, especially on mobile. They are not a substitute for a clear offer and good content, but they make everything else work better.
Can I fix this myself?
Many fixes, such as compressing images and removing unused plugins, are manageable. Deeper issues like code, hosting and script loading often need a developer.
Want a website that loads fast on every phone?
We build lightweight, mobile-first websites and landing pages with performance in mind from the start, and we can audit your current site and tell you what is slowing it down. Learn about our web design and development service, or send us your website address for a free review.