Is Your Website Too Slow? Simple Speed Fixes for Small Businesses
Your website is too slow if its main content takes longer than 2.5 seconds to appear for most visitors, or if the page jumps about while loading. Test it free with Google PageSpeed Insights. The usual fixes for small business sites are smaller images, fewer plugins and scripts, and better hosting.
How do you check if your website is slow?
Run your homepage and your busiest service page through PageSpeed Insights, Google's free test, and look at the mobile results first. The report has two parts, and they answer different questions.
The top section shows field data: how real Chrome users experienced your page over the previous 28 days, according to Google's documentation. If your site is small, this section may say there is not enough data. The lower section is lab data, a simulated load on one device and connection, which Google describes as useful for debugging but which may not capture real-world bottlenecks.
Then do the human test. Open your site on your own phone, on mobile data, with Wi-Fi off. Count how long until you can see the headline and the phone number. That is what a customer standing in a flooded kitchen experiences.
What do the Core Web Vitals scores mean?
Core Web Vitals are three measurements Google uses to judge loading, responsiveness and stability. Google's web.dev guide sets these "good" thresholds, measured at the 75th percentile of page visits on mobile and desktop:
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content (usually the hero image or headline) appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
The overall performance score in PageSpeed Insights is graded separately: 90 and above is good, 50 to 89 needs improvement, below 50 is poor. Do not chase a perfect 100. Aim to pass the three Core Web Vitals on mobile.
Does website speed affect your Google ranking?
Speed matters to Google, but relevance matters more. Google's Core Web Vitals page says good page experience aligns with what its ranking systems seek to reward. Its page experience guide is just as clear that it "always seeks to show the most relevant content, even if the page experience is sub-par."
In practice, a fast page that does not mention the service and the area will not rank for "emergency electrician Bromley". A slow page loses the customers who do find it. Fix both, and start with whichever is worse. Our local SEO strategies guide covers the relevance side.
What slows down a small business website?
On the sites we review, the same few causes come up again and again:
- Huge images. Photos uploaded straight from a phone or camera, then shrunk by the browser. The file is still full size.
- Sliders and background videos at the top of the page, which delay the main content.
- Too many plugins or apps. Each one can add scripts that load on every page, even where they are not used.
- Third-party widgets: chat bubbles, review carousels, social feeds, booking embeds and several tracking tags.
- Slow or overloaded hosting, which delays the very first response from the server.
- Images and adverts without reserved space, so text jumps down as they load and people tap the wrong thing.
How do you fix a slow website?
Work through these fixes in order. The first three cost nothing but time.
- Resize and compress images before uploading. A hero image rarely needs to be wider than the largest screen it will show on. Export as WebP or AVIF where your site supports it; Google's LCP guide recommends modern formats and responsive sizes.
- Never lazy-load the top image. Lazy loading delays images until someone scrolls near them, which is great further down the page. Google's lazy-loading guide warns against lazy-loading images that are in view when the page loads, especially the main one.
- Give images and embeds a fixed size. Google's layout shift guide says to always include width and height on images and video, and to reserve space for adverts and embeds. This is the main fix for a poor CLS.
- Remove what you do not use. Delete inactive plugins, old tracking codes and widgets nobody clicks. Replace a slider with a single strong photo and a clear headline.
- Look at your hosting. Time to First Byte measures how fast the server starts responding; web.dev suggests aiming for 0.8 seconds or less. If it is consistently slow, ask your host about caching or move to a better plan before rebuilding anything.
- Retest the same pages. Lab scores change as you work. Field data takes up to 28 days to catch up.
If you are on WordPress, a reputable caching plugin and an image optimisation plugin usually help, but install one of each, not five.
When is it worth rebuilding instead of fixing?
Rebuild when the speed problem is baked into how the site was made: a heavy theme loading dozens of features you do not use, a page builder adding layers of code, or a platform you cannot change. If fixing images, plugins and hosting still leaves you failing Core Web Vitals on mobile, a rebuild is often cheaper than months of patching.
Before you commit, ask any designer to show Core Web Vitals for sites they have already launched, and include speed targets in the brief. Our guides to what a small business website costs and the website launch checklist cover what to ask for. Oski Marketing builds sites from £1,600 with SEO foundations and analytics set up, and we test speed on real phones before launch.
What to do this week
- Run your homepage and top service page through PageSpeed Insights and note the mobile LCP, INP and CLS.
- Open the site on your phone with Wi-Fi off and time how long until you can see your phone number.
- Find the three biggest images on your homepage, resize them and re-upload.
- Remove any plugin, widget or tracking code you cannot explain the purpose of.
- If your top image is set to lazy-load, switch that off for that one image.
Frequently asked questions
What is a good PageSpeed Insights score?
Google's tool rates a performance score of 90 or more as good, 50 to 89 as needing improvement and below 50 as poor. The score is a lab test, though. The real-user Core Web Vitals section at the top of the report matters more, because it shows what actual visitors experienced.
Does website speed affect Google rankings?
Google says page experience, including Core Web Vitals, is something its ranking systems reward, but it also says it always tries to show the most relevant content even if the page experience is poor. Speed will not rescue a page that does not answer the search, but it can help when several pages are equally useful.
Why is my website slow on mobile but fine on my computer?
Phones usually have slower processors and less reliable connections than an office computer on broadband. Large images, heavy sliders and extra scripts hurt most on mobile. Always test on a real phone using mobile data, not just on desktop.
Will a new website fix my speed problems?
Not automatically. A new site built with the same oversized images, page builder add-ons and cheap hosting will be just as slow. Ask any web designer to show you the Core Web Vitals of sites they have already built.
Sources
- web.dev: Web Vitals
- Google for Developers: About PageSpeed Insights
- Google Search Central: Understanding Core Web Vitals and Google search results
- Google Search Central: Understanding page experience in Google Search results
- web.dev: Optimize Largest Contentful Paint
- web.dev: Optimize Cumulative Layout Shift
- web.dev: Browser-level image lazy loading
- web.dev: Time to First Byte (TTFB)
