The short version
- Most slow small-business sites are slow for a handful of ordinary reasons: oversized images, too many plugins or third-party scripts, a heavy theme or builder, and cheap or distant hosting.
- Google’s Core Web Vitals measure three things a visitor feels: how fast the main content appears (LCP), how quickly the page responds to taps and clicks (INP), and whether the layout jumps around (CLS).
- Test with PageSpeed Insights and the Core Web Vitals report in Google Search Console, and look at real-visitor (field) data on mobile before the lab score.
- Fix the cheap things first: compress images, remove unused plugins and scripts, and turn on caching. Rebuild only when the platform itself is the bottleneck.
If you have ever asked “why is my website slow?” while watching your own homepage load on your phone, you are not alone. Slow sites are one of the most common problems I see with small-business, clinic and non-profit websites in Cambridge, Kitchener-Waterloo, Guelph and across Ontario. This guide explains, without the jargon, what usually makes a site slow, how Google measures speed with its Core Web Vitals, how to test your own site in about five minutes, and which fixes are worth doing yourself versus paying someone for.
Why a slow website costs you more than you think
Speed is not a vanity metric. A visitor who taps your listing on Google Maps is usually on a phone, often on mobile data, and comparing you with two or three competitors. If your page sits blank while theirs loads, many people simply go back and pick someone else. You never see those lost visitors; they do not show up as complaints, just as enquiries that never arrived.
Speed also matters to Google. Its guidance for site owners says it highly recommends achieving good Core Web Vitals for success in Search. To be honest about the size of the effect: relevant, useful content still matters far more for rankings than a perfect speed score. A fast site will not outrank a better answer, but a very slow one gives visitors and Google a reason to prefer someone else when the content is similar.
Core Web Vitals explained in plain language
Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor. You do not need to understand the technical details, only what each one is checking.
| Metric | What it means for a visitor | “Good” threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main thing on the page (usually a hero image or headline) appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page reacts when someone taps a button, opens a menu or types in a form | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Whether things jump around while loading, like a button moving just as you tap it | 0.1 or less |
A page passes when it hits “good” on all three for at least three out of four real visits. The web.dev overview of Web Vitals goes deeper if you are curious, but the table above is all most owners need.
How to test your website speed in five minutes
You can check your own site for free, today, without installing anything.
- Run PageSpeed Insights. Paste your homepage address into Google's PageSpeed Insights tool and make sure the Mobile tab is selected.
- Read the top section first. If your site gets enough traffic, the top shows real-visitor data labelled as what your real users are experiencing. That is the data Google uses. The 0–100 score further down is a lab test on a simulated phone; it is useful for spotting problems but it is not what Google ranks on.
- Test your most important page, not just the homepage. For a clinic that might be the booking page; for a trades business, the main service page.
- Check Google Search Console. If you have it set up, the Core Web Vitals report groups your pages into good, needs improvement and poor, so you can see whether the problem is one page or the whole site.
Do not chase a perfect 100
A lab score of 100 is nice but not necessary. If your real-visitor data is green on all three Core Web Vitals, your site is fast enough for Google and for your visitors. Spend the remaining effort on content.
Why is my website slow? The most common reasons
In my experience, a slow site almost always comes down to a few causes, often several at once. None of them mean you did anything wrong; most build up gradually as a site grows.
Oversized images
This is the most common cause by far. A photo straight off a modern phone or camera can be several megabytes, many times larger than it needs to be on screen. Upload a few of those to a homepage slider and the page becomes heavy on mobile data. It usually shows up as a poor LCP.
Too many plugins, widgets and third-party scripts
Every chat widget, social feed, review carousel, tracking pixel, pop-up tool and WordPress plugin adds code that the visitor's phone has to download and run. Each one seems harmless; together they are a common reason for poor INP, where the page looks loaded but feels sluggish when you tap it.
Heavy themes and page builders
Multipurpose themes and drag-and-drop builders are designed to do everything, so they load code for features your site never uses. That flexibility has a speed cost that is hard to tune away.
Slow or overloaded hosting
Very cheap shared hosting puts many sites on one server. If your server takes a long time to respond, every page starts late, no matter how well it is built. Hosting far from your visitors, without a content delivery network, adds delay too.
Layout that shifts while loading
Images without set dimensions, late-loading banners, cookie notices that push content down, and web fonts that swap in late all cause the jumping that CLS measures.
What to fix first, and what you can do yourself
Work through these roughly in order. The first few are cheap and often make the biggest difference.
A practical speed-fix order
- Resize and compress large images, and use modern formats such as WebP where your platform supports it
- Remove plugins, widgets and tracking scripts you no longer use or cannot say why you have
- Turn on caching (most hosts and WordPress caching plugins offer it) and a content delivery network if your host includes one
- Make sure images and embeds have fixed dimensions so the layout does not jump
- Replace a heavy homepage slider or autoplay video with a single, well-compressed image
- Move to better hosting if the server response is consistently slow
- Consider a lighter theme or a rebuild only if the steps above do not get you to good
Owners comfortable with their site's admin panel can usually handle the first three. Image compression alone sometimes moves a site from poor to good. Removing a plugin is safe to try on a staging copy or after a backup; if something breaks, put it back.
Be careful with “speed booster” plugins
Optimization plugins can help, but stacking several of them, or turning on every setting at once, often breaks menus, forms or checkout pages. Change one thing at a time and test your contact and booking forms afterwards.
When to get help, and when a rebuild makes sense
If you have done the easy fixes and your real-visitor data is still poor, the problem is usually structural: the theme, the builder, the hosting or how the site was put together. At that point more plugins rarely help.
A focused performance audit is a sensible next step. I do these at my hourly rate of $45 per hour plus HST, and the result is a written list of what is slowing your site down, roughly what each fix would cost, and which ones are worth doing. Sometimes the answer is a few hours of targeted fixes. Sometimes it is honest advice that the platform is the bottleneck and a rebuild will cost less than continually patching it.
If you are on WordPress and weighing that decision, my guide to migrating from WordPress to Next.js walks through when a rebuild pays off and how to protect your search traffic. Keeping a site fast after launch is also part of ongoing care; my post on website maintenance costs covers what that looks like. You can see every option on the services and pricing page, or get in touch about a speed audit.
Frequently asked questions
Why is my website slow on mobile but fine on my computer?
Phones have slower processors than most computers and are often on mobile data, so heavy images and scripts hurt much more. Your office Wi-Fi and a fast laptop can hide problems that most of your visitors experience. Always test on the Mobile tab in PageSpeed Insights.
Does website speed affect Google rankings?
It plays a part. Google recommends good Core Web Vitals for success in Search, but relevant, helpful content matters much more. Speed tends to make the difference when your content is similar to a competitor’s, and it always affects whether visitors stay.
What is a good PageSpeed Insights score?
Focus on the real-visitor Core Web Vitals at the top of the report rather than the 0–100 lab score. If LCP, INP and CLS are all in the good range, your site is fast enough. A lab score in the 90s is a nice bonus, not a requirement.
Will switching hosts make my website faster?
Only if hosting is the bottleneck. If the server is slow to respond on every page, better hosting helps a lot. If the real problem is large images or too many scripts, moving hosts changes very little, so fix those first.
Written by Corey Paskewitz
Corey is a full-stack web and software developer in Cambridge, Ontario. Through Corvian Labs he designs and builds websites, booking systems and custom web apps for businesses across Kitchener-Waterloo, Guelph and beyond.