Home / Insights / Article

All insights

Website fixes

Why is my website slow? How to find the cause and fix it

Fine on your office Wi-Fi, painfully slow on a customer's phone? Here's how to measure speed properly, read the numbers, find the usual culprits and fix them in the order that makes the biggest difference.

In short: most slow small business websites are slow for a handful of fixable reasons: oversized images, too many third-party scripts and widgets, heavy themes or page builders, web fonts loaded badly, and slow or uncached hosting. Test your key pages on mobile with PageSpeed Insights, read the real-visitor data first, find which of the three Core Web Vitals is failing, and fix the biggest cause behind that one metric before touching anything else.

"My website is slow" is one of the most common complaints we hear from small business owners, and it comes up again and again in small business forums alongside broken forms. The frustrating part is that a site can feel fine on your office Wi-Fi and still be painfully slow for a customer on a phone with a weak signal. This guide explains how to measure speed properly, what the numbers mean, the usual causes, and the fixes that make a real difference, in the order we'd tackle them.

Why speed matters for a small business

Speed affects two things you care about: whether people stay long enough to contact you, and how Google sees your pages.

  • Customers. Most local searches happen on phones. If the page is blank or jumping around for several seconds, people go back and tap the next result. You never see them, because they leave before they do anything.
  • Search. Google's Search Central guidance recommends achieving good Core Web Vitals and says they align with what its core ranking systems seek to reward. Speed won't outrank a more relevant page on its own, but a slow page makes everything else you do work harder.

So the goal isn't a perfect score. The goal is a page that shows its main content quickly, responds when tapped and doesn't jump around, for real visitors on real phones.

How to test your website speed properly

  1. Pick three pages that matter. Usually your homepage, your most important service or product page, and your contact or booking page. Test each one separately; they are often slow for different reasons.
  2. Run them through PageSpeed Insights and look at the Mobile tab first. Mobile is where most problems show up.
  3. Read the top section before the score. If your site has enough traffic, the top of the report shows real-visitor data from the Chrome User Experience Report: how actual Chrome users experienced the page over the past 28 days. This is what Google uses for Core Web Vitals.
  4. Then read the lab test below it. The performance score and the list of opportunities come from Lighthouse, a simulated test on a single device and connection. It is great for finding causes but it isn't what your visitors experienced.
  5. Open Search Console. The Core Web Vitals report groups similar pages and shows which ones are "Poor" or "Need improvement" on mobile and desktop. If your site is small, it may say there isn't enough data; in that case rely on the lab test and on trying the site yourself on a phone using mobile data.
  6. Write the numbers down. Keep a simple note of each page's results before you change anything, so you can see whether a fix worked.

What the numbers mean

Google's Core Web Vitals are three measurements. According to web.dev, a page passes when at least 75% of visits meet the "good" threshold for all three, measured separately for mobile and desktop.

MetricWhat it measuresGoodPoorUsual causes when it fails
LCP (Largest Contentful Paint)How long until the main content, often the hero image or headline, appears2.5 s or lessOver 4 sHuge hero image, slow server, render-blocking CSS and fonts, lazy-loaded hero
INP (Interaction to Next Paint)How quickly the page responds when someone taps or clicks200 ms or lessOver 500 msToo much JavaScript: chat widgets, trackers, sliders, heavy builders
CLS (Cumulative Layout Shift)How much the page jumps around while loading0.1 or lessOver 0.25Images without set sizes, late banners and pop-ups, ads, fonts swapping

Two other numbers help with diagnosis. Time to First Byte (TTFB) shows how long the server takes to start sending the page; if it's high, the problem starts before the browser does anything. Total Blocking Time appears in the lab test instead of INP, because a simulated test has no real taps; a high TBT usually points to the same JavaScript problems that hurt INP. INP replaced the older First Input Delay metric as a Core Web Vital in 2024, so ignore older guides that still talk about FID.

The seven usual causes of a slow small business site

1. Images that are far too big

This is the most common cause we see. A phone photo uploaded straight to the site can be several megabytes and thousands of pixels wide, even though it's shown at a few hundred pixels. It isn't just photos: in one recent small business website thread, an owner discovered their tiny favicon file was over 1 MB. Check the lab report for "Properly size images" and "Serve images in next-gen formats".

2. Third-party scripts and widgets

Chat bubbles, booking calendars, review widgets, social feeds, video embeds, heatmaps and several analytics tags each load their own code from someone else's server. Individually they look harmless; together they can make the page slow to load and slow to respond. Booking and calendar embeds are frequent offenders, sometimes loading megabytes of code even when they're far down the page.

3. Heavy themes and page builders

Multi-purpose themes and drag-and-drop builders load the code for every feature they offer, whether you use it or not. Each extra plugin can add more. That's why a simple five-page site can end up heavier than it needs to be.

4. Web fonts loaded badly

Several font families in many weights, loaded from an outside server, can hold up the text and cause it to jump when the font arrives. Most small business sites need one or two families and three or four weights at most.

5. Slow or overloaded hosting

If TTFB is consistently high, the server is the bottleneck. Cheap shared hosting, a server far from your customers, or a site that builds every page from scratch on every visit all show up here.

6. No caching or compression

Without caching, returning visitors download the same files again and the server repeats the same work. Without compression, every file is bigger than it needs to be. The lab report flags these as "Serve static assets with an efficient cache policy" and "Enable text compression".

7. Layout that jumps

Images and embeds without width and height set, cookie banners that push content down, and pop-ups that appear after the page has loaded all cause layout shift. Visitors tap the wrong thing, and CLS fails.

The fixes, in the order we'd do them

Fix the metric that's failing, starting with the biggest cause behind it. Here's the order that usually gives the most improvement for the least effort.

  1. Resize and compress images. Export images at no more than about twice the size they're displayed, use modern formats such as WebP or AVIF where your site supports them, and serve smaller versions to phones using responsive image markup. Replace any oversized favicon or logo file.
  2. Load the main image first. Never lazy-load the hero image or anything visible on first screen. Give it priority (for example with fetchpriority="high") and lazy-load images further down the page instead.
  3. Audit every third-party script. List each widget and tag and ask: does this bring in enquiries or sales? Remove anything that doesn't. For the rest, load them only when needed. A chat widget or booking calendar can show a simple button that loads the full tool when tapped, and a video can show a thumbnail until someone presses play.
  4. Remove unused plugins and theme features. Deactivate and delete plugins you don't use, turn off builder modules you don't need, and avoid installing a plugin to fix a speed problem caused by too many plugins.
  5. Simplify fonts. Cut down to the families and weights you actually use, host them on your own domain where possible, and use font-display: swap so text shows straight away.
  6. Turn on caching and compression. Page caching, browser caching and text compression are usually settings in your hosting or platform, not code changes. A content delivery network can help if your customers are spread out geographically.
  7. Stop the jumping. Set width and height on every image and embed, reserve space for banners, and avoid pop-ups that appear over content on phones.
  8. Look at hosting last, but don't ignore it. If TTFB stays high after caching is on, it's time for better hosting or a lighter build.

After each change, re-run the lab test on the same pages and compare with your notes. Remember that the real-visitor data in PageSpeed Insights and Search Console covers the past 28 days, so improvements take several weeks to show fully there.

A worked example

Here's how this works on a typical service business homepage (an illustration, not a client site). The mobile lab test flags slow LCP, high Total Blocking Time and a few layout shifts.

  • LCP: the hero is a full-width photo uploaded straight from a camera, and the theme lazy-loads it. Resizing it, converting it to WebP and removing lazy loading on that one image tackles the biggest problem.
  • Blocking time: a chat widget, a reviews carousel and a booking calendar embed all load on page load. The owner keeps the booking calendar but loads it from a "Book now" button, swaps the carousel for three written testimonials, and removes the chat widget nobody used.
  • Layout shift: the cookie banner pushes the page down. Making it overlay the bottom of the screen instead stops the jump.

None of these steps needed a rebuild, and each one removed something visitors were waiting for without seeing any benefit.

Speed fixes that backfire

MistakeWhy it backfiresDo this instead
Chasing a 100 scoreThe lab score is a simulation; real-visitor Core Web Vitals matter moreAim to pass all three metrics on mobile for your key pages
Stacking speed pluginsOverlapping optimisation tools can conflict and break layouts or formsUse one well-configured caching setup and fix the causes
Lazy-loading everythingLazy-loading the hero image makes LCP worsePrioritise the first-screen image, lazy-load the rest
Testing only on desktop Wi-FiHides the problems your phone visitors haveTest on mobile data and read the Mobile tab
Deleting scripts blindlyCan break analytics, booking or your contact formRemove one at a time, then test enquiries still arrive

That last point matters: after any speed work, send yourself a test enquiry from your phone. A fast site that silently drops enquiries is worse than a slow one. If your form has been flooded with junk, our guide to stopping contact form spam covers fixes that won't slow the page down.

When to fix and when to rebuild

Most sites can be made noticeably faster without a rebuild. A rebuild starts to make sense when the slow parts can't be removed: a heavy builder that the whole site depends on, a theme that loads everything on every page, many plugins doing basic jobs, or hosting you can't change. If you'd also like to update the design or content, our website redesign checklist explains how to rebuild without losing your Google rankings. Keeping a site fast after it's fixed is part of regular upkeep; our guide on whether a website care plan is worth it explains what needs doing and how often.

Website speed checklist

  • Tested the homepage, a key service page and the contact page on mobile in PageSpeed Insights
  • Read real-visitor data first and noted which Core Web Vital fails
  • Checked the Core Web Vitals report in Search Console
  • All images resized and compressed; favicon and logo files small
  • Hero image not lazy-loaded and given priority
  • Every third-party script justified; widgets load on demand
  • Unused plugins and theme features removed
  • One or two font families, a few weights, text visible straight away
  • Caching and compression switched on
  • Width and height set on images and embeds; no jumping banners
  • Test enquiry sent from a phone after every change
  • Results re-checked in four weeks once the real-visitor data has updated

For the wider picture beyond speed, see our small business website checklist, and if your site is fast but still quiet, read getting visitors but no enquiries.

FAQ

Why is my website slow on mobile but fine on desktop?

Phones have slower processors and often weaker connections than an office computer, so heavy images and JavaScript hurt them far more. PageSpeed Insights tests mobile with a simulated slower device for that reason. Fix the Mobile results first; desktop usually improves too.

What is a good PageSpeed score?

Treat the score as a guide, not a target. What matters more is passing Core Web Vitals for real visitors: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, for at least 75% of visits.

Does website speed affect Google rankings?

Google recommends good Core Web Vitals and says they align with what its ranking systems reward, but relevance and helpful content matter more. A fast page won't outrank a more relevant one, while a slow page can lose visitors who would have contacted you.

Why hasn't Search Console updated after I fixed my site?

The Core Web Vitals data in Search Console and PageSpeed Insights is based on real visits over the previous 28 days, so improvements show gradually. Use the lab test to confirm a fix straight away, then check the field data again after about four weeks.

Will a speed plugin fix my slow website?

It can help with caching and compression, but it can't remove the real causes, such as oversized images, unnecessary widgets or a heavy theme. Several overlapping optimisation plugins can also conflict. Fix the causes first and keep one well-configured caching setup.

How much does it cost to make a website faster?

It depends on the cause. Resizing images and removing unused widgets can take an afternoon; replacing a heavy builder or theme is a bigger job that can approach the cost of a rebuild. Measure first, so you know which kind of problem you have before you pay for anything.

Next step

If your site is slow and you'd rather not spend weekends fighting plugins, we can help. Aurel Digital builds fast, hand-coded small business websites, landing pages and online stores without heavy page builders, and tests them on real phones before launch. You own the domain, hosting and code, and sites start from $300 with a fixed quote.

Want to know why your site is slow? Send us your web address or email James at james@aureldigitals.com, and we'll tell you honestly whether it needs a few fixes or a rebuild.

Related: Small business website checklist 2026, Getting visitors but no enquiries?, Is a website care plan worth it?, Contact form spam: how to stop it

About the author: James is the founder of Aurel Digital, a remote studio founded in 2026 that builds websites, stores and apps for brands, nonprofits and service businesses. More about James and Aurel Digital.

Work Contact Call