You open your own website on your phone, and you wait. And wait a bit more. If it feels slow to you, it feels a lot slower to someone who has never heard of your business and has four other tabs open.
Speed matters for two reasons. People leave slow pages, often before they've seen anything. And Google uses page experience signals, including its Core Web Vitals, as part of how it ranks pages. Speed won't beat genuinely useful content on its own, but a slow site is quietly working against you.
First, measure it
Before you change anything, run your site through PageSpeed Insights. It's free and comes from Google. Test your homepage and your most important service page, and look at the mobile results first, because that's where most of your visitors are.
You'll see three Core Web Vitals. Here's what they mean in plain English:
- Largest Contentful Paint (LCP): how long the main content takes to appear. Aim for 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page reacts when someone taps or clicks. Aim for 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much things jump around while the page loads. Aim for 0.1 or less.
Got your numbers? Now for the usual suspects.
1. Huge images
This is the most common cause by a long way. A photo straight off a phone can be 4 or 5 MB. Put ten of those on a homepage and you've built a slow website without trying.
Fix: resize images to the size they're actually shown at, compress them, and use modern formats like WebP or AVIF. Images further down the page should only load when the visitor scrolls to them. This is called lazy loading, and most modern sites support it.
2. Too many plugins and scripts
Every plugin, tracking pixel, popup tool and image slider adds code the browser has to download and run. It's common to find WordPress sites running 30 or 40 plugins, half of which nobody remembers installing.
Fix: list everything that loads on your site and remove what you don't need. If two plugins do the same job, keep the better one.
3. Cheap or far-away hosting
If your customers are in India and your website sits on a crowded budget server on the other side of the world, every page request takes the long way round.
Fix: use reliable hosting with servers close to your audience, and put a CDN (content delivery network) in front of the site so files are served from somewhere near each visitor.
4. No caching
Without caching, your server rebuilds every page from scratch for every single visitor. That's a lot of wasted effort for pages that hardly ever change.
Fix: turn on page caching on the server or with a caching plugin, and set browser caching so returning visitors don't download the same files again.
5. Heavy themes and page builders
Multipurpose themes try to do everything, so they load code for features you'll never use. Drag-and-drop builders can also add layers of extra markup to every page.
Fix: a lighter theme, or a site built for your specific needs, often makes a bigger difference than any amount of tweaking. Sometimes a rebuild genuinely works out cheaper than months of patching. We compare the options in WordPress vs a custom website.
6. Fonts and code that block the page
Some files have to finish loading before the browser shows anything at all. Big font files, bloated CSS and scripts loaded in the wrong place all delay that first view of the page.
Fix: load only the font weights you actually use, defer scripts that aren't needed straight away, and keep CSS lean.
7. Third-party embeds
Chat widgets, embedded YouTube videos, Instagram feeds and Google Maps are handy. Each one also pulls in a surprising amount of outside code.
Fix: load them only when they're needed. A video can show a thumbnail until someone presses play. A map can be a simple image that opens Google Maps when tapped.
Where to start
If you only do two things this week, compress your images and remove the plugins you don't use. Then test again. Those two changes alone often make a noticeable difference.
If the site is still slow after that, the cause is usually the theme, the hosting or how the site was built in the first place. That's the point where it's worth having a developer look under the hood.
Launching a new site soon? Run through our website launch checklist too.
Is your website slow?
We'll check your site and tell you what's slowing it down and what it would take to fix it.