How to Speed Up a Slow Website (Core Web Vitals, Plainly)

Why a slow website costs you more than patience

A slow site quietly bleeds money. People leave before it loads, so you never get the enquiry. Google notices the drop-off and ranks you lower, so fewer people find you in the first place. And AI search engines, which read your pages like a crawler does, struggle with heavy, sluggish sites too. Speed isn't a vanity metric — it's the difference between a visitor who converts and one who's already gone.

The good news: most slowness comes from a handful of usual suspects, and you don't need to be technical to understand them. This guide explains what's actually going on and what genuinely moves the needle — in plain English.

What Core Web Vitals actually measure

Core Web Vitals is Google's official name for three things it measures about how a page feels to a real person. Strip the jargon and they're simple:

• Largest Contentful Paint (LCP) — how long until the main thing on the page (usually the big image or headline) shows up. Google wants this under 2.5 seconds. This is the one people mean when they say "it's slow to load."
• Interaction to Next Paint (INP) — when you tap or click, how quickly the page responds. If a button feels laggy, this is why. Under 200 milliseconds is the target.
• Cumulative Layout Shift (CLS) — how much the page jumps around as it loads. You know the feeling: you go to tap something, an ad or image drops in, and everything shifts. Google wants this close to zero.

Together they answer one question: does the page feel fast, responsive and stable to a real human? That's what Google now rewards — and it's exactly what a visitor wants too.

The usual reasons a website is slow

Before the fixes, the causes. Nine times out of ten, a slow site is slow because of one or more of these:

• Huge, unoptimised images. The single most common culprit. A photo straight off a phone or camera can be several megabytes; on a web page it should be a fraction of that. Oversized images are the number one thing dragging load times down.
• Too many plugins or scripts. Every plugin, tracking tag, chat widget and font adds weight and requests. On a typical bloated site, half the load time is third-party scripts doing very little.
• Cheap or overloaded hosting. If your site sits on a slow, shared server crammed with hundreds of other sites, no amount of tidying will make it quick. The foundation matters.
• No caching. Without caching, the server rebuilds the whole page from scratch for every single visitor. Caching serves a ready-made version instantly. Its absence is a big, invisible tax.
• A bloated theme or page builder. Off-the-shelf themes and drag-and-drop builders load enormous amounts of code you'll never use, "just in case." It all has to download before the page appears.
• No lazy loading. By default, some sites try to load every image on the page at once — even the ones far down that nobody's scrolled to yet. Lazy loading defers them until they're needed.

The fixes that actually move the needle

In rough order of impact-for-effort — do the top ones first:

• Compress and resize every image. Biggest win, least glamour. Serve images at the size they're actually displayed, in a modern format (WebP or AVIF), properly compressed. This alone often halves load time.
• Turn on caching. Page caching and browser caching mean returning visitors and the server both stop redoing work. Near-instant win on most sites.
• Cut the dead weight. Audit your plugins and scripts and remove anything you don't genuinely use. Every one you delete is weight gone. Be ruthless with chat widgets, unused tracking and "social" scripts.
• Fix layout shift. Set explicit dimensions on images and reserve space for anything that loads in (ads, embeds, banners) so the page doesn't jump. This is a small job with a big feel-good payoff.
• Lazy-load below-the-fold content. Load what's on screen first; defer the rest until the visitor scrolls to it. The page becomes usable far sooner.
• Get on hosting that's built for speed. If the foundation is slow, everything else is patching. Proper hosting with a content delivery network (CDN) makes a genuine, measurable difference.
• Then measure again. Run the page through Google's PageSpeed Insights before and after so you can see what worked — and where the next bottleneck is.

How to check your own site's speed (free, in five minutes)

You don't need to guess or pay for a tool to start:

• Google PageSpeed Insights — paste your URL in and it grades your Core Web Vitals, tells you your real-world scores, and lists specific fixes in priority order. This is the one to trust.
• Your own phone, on mobile data. Turn off Wi-Fi and load your site as a customer would. If it feels slow to you, it's costing you visitors. The stopwatch in your pocket is honest.

Note the score and the top three flagged issues. That's your fix list. Most of the wins on it are the ones above — images, caching and dead weight.

When a rebuild beats another round of fixes

There's an honest limit to tuning. If your site's built on a bloated theme, a heavy page builder and years of accumulated plugins, you can chase speed for months and still land in the amber. At some point the foundation is the problem, and the cheapest fix is a clean rebuild rather than endless patching.

That's a large part of why we build the way we do — clean, custom code instead of a stack of plugins, on hosting built for speed. We hold our builds to a 93+ performance score and sub-two-second loads, and it's part of why our own work has been recognised at Awwwards: fast and well-built aren't a trade-off, they're the same discipline. If you'd rather have the numbers built in from day one than tuned back in later, that's how we build fast websites.

The rule of thumb: if the fixes above get you into the green, keep tuning. If you're doing them and still stuck, the site itself is the bottleneck — and a rebuild pays for itself in the visitors you stop losing.

FAQ

Why is my website so slow?

Almost always one of a few things: oversized images, too many plugins and scripts, no caching, or slow hosting. Run your URL through Google PageSpeed Insights — it'll tell you exactly which, in priority order. Images are the most common single cause.

What are Core Web Vitals in simple terms?

Three things Google measures about how a page feels: how fast the main content loads (LCP), how quickly the page responds when you tap (INP), and how much it jumps around while loading (CLS). Together they measure whether a page feels fast, responsive and stable to a real person.

What's a good website load time?

Aim for the main content to appear in under 2.5 seconds, and ideally under 2 on a decent connection. Past about 3 seconds you start losing a meaningful share of visitors before the page even finishes.

Will a faster website help my Google ranking?

Yes — Core Web Vitals are a ranking factor, and speed also cuts the bounce rate that drags rankings down indirectly. It won't outweigh great content and relevance, but a fast site helps and a slow one actively hurts.

Can I speed up my site myself or do I need a developer?

The big wins — compressing images, enabling caching, removing unused plugins — are often doable yourself on a platform like WordPress. Deeper issues (a bloated theme, poor hosting, code problems) usually need a developer, or a rebuild if the foundation's the problem.