Why your site feels slow — and what actually fixes it

“My site feels slow” is one of the most common things owners say to us, and it's usually true. The good news is that slow websites are slow for a short, boring list of reasons. You don't need to understand code to figure out which one is yours. You just need to know where to look.

First, get a real number instead of a feeling. Open Google's free PageSpeed Insightsand run your own address. It's the same measurement industry uses, it's free, and it tells you what's actually slowing the page down. Google publishes target thresholds for what it calls Core Web Vitals — you can look those up and hold your site to them. Check the mobile score, not just desktop; mobile is where most of your visitors are and where sites struggle most.

Now, the four usual culprits.

1. Images that are way bigger than they need to be

This is the number one cause we see, and it's the easiest to fix. A photo straight off a phone or a stock site can be five, ten, twenty times larger than the space it fills on screen. The browser downloads the whole giant file and then shrinks it down — so your visitor waits for pixels they never actually see.

What actually fixes it:

• Resize images to roughly the size they're displayed at before you upload them. A photo shown 800 pixels wide doesn't need to be 4,000.
• Save them in a modern format like WebP, which is dramatically smaller than an old JPEG or PNG at the same quality.
• Let images below the fold load only as the visitor scrolls to them (“lazy loading”). Most modern site tools do this automatically.

2. Too many fonts, or fonts loaded the slow way

Custom fonts make a site feel designed. They also cost time, because the browser has to fetch each font file before it can paint text the right way. Load four families in six weights each and you've got a pile of files the visitor is quietly waiting on.

The fix is restraint: one or two typefaces, only the weights you actually use, and settings that let text show immediately in a fallback font while the custom one loads, so nobody stares at a blank space. If you're not sure how your fonts are set up, that's a fair question to ask whoever built the site.

3. Third-party scripts — the silent tax

This is the sneaky one. Every add-on you bolt onto a site — a chat widget, a tracking pixel, a reviews carousel, a booking embed, a pop-up builder, three different analytics tools — is code loaded from someone else's server. Each one is a little tax on load time, and they add up fast. We regularly see sites where half the loading time is stuff the owner forgot they installed.

What actually fixes it: audit the list of third-party tools, remove the ones you don't use, and load the survivors so they don't block the page from showing up. A good developer can defer most of them so your content paints first and the extras load quietly after.

4. Where the site lives

Two sites with identical code can feel very different depending on where they're hosted. Cheap shared hosting crams many sites onto one tired server; when a neighbor gets busy, you get slow. And if your server sits in one city while your customers are across the country, every request makes a long round trip.

The fix is decent hosting plus a CDN — a content delivery network, which keeps copies of your site in data centers around the country so it's served from somewhere near each visitor. For most small-business sites this is inexpensive now, sometimes free, and it's often the single biggest jump for the least ongoing effort.

The honest order to fix them in

If you do nothing else: shrink your images, then look at your third-party scripts. Those two account for most of the slowness on most sites, and neither requires rebuilding anything. Fonts and hosting are worth doing too, but they're usually a smaller win.

And keep it in proportion. Speed is one of five places a site leaks customers — a fast site with a confusing message still loses people. If you want the full picture, that's what the Leak Map frame is for.