Why Your Website Is Slow (and What It's Actually Costing You)Why Your Website Is Slow (and What It's Actually Costing You)

Nobody emails you to say your website was slow. They just leave. That's what makes speed such an easy problem to ignore — the damage is invisible, and the site looks fine on your own laptop, on your own office wifi, with every image already cached in your browser.

Meanwhile a homeowner is standing in their driveway on a weak cell signal, tapping your contact page, watching a white screen. Three seconds in, they hit back and tap the next result. You never knew they were there.

Here's what actually makes sites slow, how to check yours without guessing, and what to fix first.

What "slow" actually means

Google measures three things, and they map neatly onto what a visitor feels.

The first is how long until the biggest thing on screen shows up — usually your hero image or headline. Under 2.5 seconds is the target. The second is how quickly the page responds when someone taps a button or opens a menu. Under 200 milliseconds. The third is whether the page jumps around while it loads. You've felt this one: you go to tap a link, an image finally loads above it, everything shifts, and you tap the wrong thing.

You don't need to memorize the acronyms. You need to know that all three are measurable, and all three are fixable.

Measure it honestly, not flatteringly

Run your site through Google's PageSpeed Insights. Two things matter about how you read the result.

First, look at the field data at the top — that's real visitors on real phones over the last month. The lab score below it is a simulation. The field data is the truth. If there's no field data, your traffic is too low for Google to collect it, and the lab score is your best proxy.

Second, test the pages that actually make you money. Everyone tests the homepage. Your leads come in through a service page, a listing page, a contact form. Test those. On mobile. The mobile score is the one that counts, because that's where most of your traffic is.

The usual suspects, roughly in order

**Images.** This is the number one cause, and it isn't close. Someone uploads a 4,000-pixel photo straight off a camera to fill a 600-pixel space, and the visitor downloads all of it. Every photo on a site should be sized to what it's displayed at, saved as WebP, and compressed. Images below the fold should load only when someone scrolls to them. Fixing images alone often cuts load time in half.

**Autoplay video headers.** A looping video hero looks great in a design review. On a phone, it's a multi-megabyte download competing with everything else on the page. If you want one, it needs a poster image that appears instantly, a compressed file, and no video at all on mobile.

**Cheap hosting.** If the server takes a second and a half to even start responding, nothing you do to the page will save you. This is the fix nobody wants to hear because it costs money every month, but shared budget hosting is a tax you pay in lost visitors. Add proper caching and a CDN so your files are served from somewhere near the visitor.

**Plugin pileup.** On WordPress, plugins accumulate. A slider plugin from the old design, two SEO plugins that half-overlap, a form builder nobody uses. Each one loads its own scripts and styles on every page, whether that page uses it or not. Audit the list once a year and be ruthless.

**Third-party scripts.** Chat widget, heat map, two analytics tags, a Facebook pixel, a review carousel, a booking embed. Every one of those is a request to somebody else's server, and you inherit their speed. Keep the ones that earn their spot. Delete the rest.

**Fonts.** Loading six weights of a custom font when you use two is a common, quiet drag. Load only what you use, self-host it, and set fonts to display fallback text immediately so words appear while the font arrives.

What to fix first

If you do nothing else: compress and resize your images, then check your hosting response time. Those two account for the majority of the problem on most business sites, and neither requires a redesign.

After that, cut third-party scripts, then trim plugins, then handle fonts. Save the deep technical work — code splitting, deferring scripts, server tuning — for a developer. It matters, but it's the last 20% and it's the hardest 20%.

When speed isn't the real problem

Chasing a perfect 100 score is a trap. Going from a 92 to a 98 changes nothing a customer will ever notice. Going from a 30 to a 70 changes everything.

And a fast site that's confusing is still a site that doesn't convert. Speed gets people in the door. What's on the page decides whether they call you. If your load time is already reasonable and leads are still thin, the problem is your message, your proof, or your call to action — not your milliseconds.

How we handle it

We build performance in rather than bolting it on at the end. Images get processed before they're ever placed, hosting gets specified as part of the build, and every site gets tested on a throttled mobile connection before launch — not on the fast office wifi where everything looks great.

If your current site feels sluggish and you're not sure why, run it through PageSpeed Insights on mobile and look at the field data. It'll tell you more in thirty seconds than a month of wondering.