A slow website is like a shop with a door that sticks. Some people shove it open anyway. Most just walk on to the next one. The frustrating part is you never see the customers you lost, so it's easy to pretend the problem doesn't exist.
Speed affects two things at once: whether people stick around, and whether Google trusts your site enough to rank it. Google measures part of this with a set of scores called Core Web Vitals. Let's walk through what they are and, more importantly, what to do about them.
Why speed is worth the trouble
Every extra second a page takes to load, more people leave. That's been measured over and over, and the drop is steep on mobile, where connections are patchy and patience is thin. For an online store or a business running paid ads, a slow page means you're paying for clicks that bounce before the page even appears.
Then there's ranking. Google has said plainly that page experience, including speed, is a factor in search. It's not the biggest one, content and relevance still lead, but when two pages are otherwise close, the faster one wins. And since AI search tends to pull from pages that already rank, speed feeds into that too.
What Core Web Vitals actually measure
Google boiled site experience down to three numbers. The names are clunky, but the ideas are simple:
- Largest Contentful Paint (LCP)
- How long until the main thing on the page (usually the big image or headline) shows up. Aim for under 2.5 seconds. This is the "has it loaded yet" feeling.
- Interaction to Next Paint (INP)
- How quickly the page responds when someone taps or clicks. Aim for under 200 milliseconds. This is the "is this thing frozen" feeling.
- Cumulative Layout Shift (CLS)
- How much the page jumps around while loading. Aim for under 0.1. It's the "I tried to tap the button and it moved" annoyance.
You can check all three for free with Google's PageSpeed Insights or the Core Web Vitals report in Search Console. They'll show you real numbers from real visitors, not just a lab test.
The usual culprits behind a slow site
- Huge images. A photo saved straight off a camera can be several megabytes when it only needs to be a few hundred kilobytes.
- Too many scripts. Every chat widget, pop-up, analytics tag, and social embed adds weight and delay.
- Cheap or distant hosting. If your server is slow or far from your customers, everything else is slower by default.
- No caching. Without it, the browser rebuilds the whole page from scratch on every visit.
- Bloated themes and page builders. Convenient to set up, often heavy and messy under the hood.
Images are almost always the first fix
On most sites I look at, images are the biggest single drag. The fix isn't complicated: resize them to the size they actually display at, compress them, and use modern formats like WebP. Load images below the fold only as the visitor scrolls to them. That one pass often takes a page from sluggish to snappy without touching anything else.
Which fix to do first, by effort and payoff
Speed work has a bad reputation because people start in the wrong place. They read a PageSpeed report top to bottom and try to clear every warning, including the ones worth a tenth of a second. Then they run out of patience before getting to the two changes that would have halved the load time.
So here's the order I work in. The rows at the top are cheap and make a visible difference. The rows at the bottom cost real time and money, and only earn their place once everything above them is done.
| Fix | Effort | Typical gain | Worth doing when |
|---|---|---|---|
| Compress and resize images | An afternoon | Large, often the single biggest win | Always. Start here |
| Lazy-load below-fold images | An hour | Large on long pages | Any page with more than three or four images |
| Remove unused scripts and widgets | An hour of auditing | Medium to large | You've added a chat box, pop-up, or three analytics tags |
| Turn on caching | Minutes on most hosts | Medium for repeat visitors | Always. It's usually a toggle |
| Add a content delivery network | A morning | Medium, large if your visitors are far away | Your audience spans more than one country |
| Self-host or preload fonts | An hour | Small to medium, fixes text that pops in late | Text visibly shifts or flashes while loading |
| Move to faster hosting | A day, plus money | Medium to large | The server itself is slow after everything above |
| Rebuild on a lighter platform | Weeks, plus real money | Large, but so is the cost | The theme or page builder is the actual bottleneck |
If you only ever do the first four rows, you'll be faster than most of your competitors and you won't have spent anything but a day of attention.
Test on a real phone, not just a score
A green score on a desktop test can hide a page that feels awful on a mid-range Android handset over mobile data. Pull your site up on an actual phone, off wifi, and count the seconds before you can read something. That number is what your customers experience, and it's the one I trust over any dashboard.
How to make your site faster
- 1Measure first with PageSpeed Insights so you know your starting point and your worst pages.
- 2Fix your images: resize, compress, switch to WebP, and lazy-load the ones lower down.
- 3Cut scripts you don't need. Every third-party widget earns its place or it goes.
- 4Turn on caching and, if your audience is spread out, a content delivery network.
- 5If the platform itself is the problem, consider a lighter, purpose-built site instead of fighting a bloated theme.
Fast isn't a luxury feature you add at the end. It's part of whether the site works at all.
You don't need a perfect score. Chasing 100 out of 100 can waste days for a point nobody feels. Get into the green on the three vitals, make sure the site feels quick on a normal phone, and spend the rest of your energy on content and offers.
If your site's slow and you're not sure why, a performance audit is usually the fastest money you'll spend. My web development work is built around sites that are fast from the first line of code. Get in touch if you want me to take a look.
Frequently asked questions
Aim for your main content to appear within about 2.5 seconds on a typical mobile connection. Faster is better, but under that threshold puts you in good shape for both users and Google's Core Web Vitals.