Why your website is slow — and what actually fixes it

A slow website costs you twice: visitors leave before they convert, and Google quietly ranks you lower for it. The frustrating part is that most "speed fixes" people try — a new theme, a caching plugin, a faster host — treat symptoms while the real bottleneck sits untouched.

Here's what actually makes sites slow, and what actually fixes it.

Measure before you touch anything

Speed is not a feeling. Google publishes the exact metrics it uses — Core Web Vitals — and they're the scoreboard:

• LCP (Largest Contentful Paint) — how long until the main content shows up. Aim for under 2.5s.
• INP (Interaction to Next Paint) — how quickly the page responds when someone clicks or types.
• CLS (Cumulative Layout Shift) — how much the page jumps around while loading.

Run your site through PageSpeed Insights and read the field data, not just the lab score. That tells you what real visitors experience, which is what Google actually ranks on.

The usual real culprits

In practice, slow sites are almost always one of these:

• Unoptimized images. The single most common cause. A hero image exported at full resolution can be larger than the rest of the page combined. Right-size them, compress them, serve modern formats.
• Render-blocking scripts. Third-party tags — chat widgets, analytics, ad pixels, A/B tools — each add a delay. Most sites carry several they no longer use.
• Too much JavaScript up front. Shipping the whole app before showing anything is the classic single-page-app tax. Code-split so the first screen loads first.
• Layout shift from unsized media. Images and embeds without dimensions push content around as they load, tanking CLS and annoying everyone.

Notice what's not on the list: your host, most of the time. Upgrading servers rarely fixes a front-end problem.

The fixes that move the needle

In rough order of impact for most sites:

1. Compress and right-size images, and lazy-load the ones below the fold.
2. Audit third-party scripts and delete the ones you don't need. Defer the rest.
3. Code-split so the initial load ships only what the first screen needs.
4. Set explicit dimensions on images and embeds to kill layout shift.
5. Cache and use a CDN so repeat visits and distant visitors are fast.

None of these are glamorous. All of them are measurable — which is the point. You fix, you re-measure, you keep what worked.

Why it's worth it

Core Web Vitals are a ranking factor, but the bigger win is trust. A fast site feels credible; a slow one makes people wonder what else is neglected. For a company whose website is often the first impression, that gap is expensive.

If your site undersells you — slow, clunky on mobile, or just tired — that's exactly the kind of thing our web & brand work fixes: fast, accessible, measured, and shipped. And when the bottleneck turns out to be behind the scenes, that's a backend systems conversation.