Why Is My Website So Slow? A Non-Technical Guide

Images are the cause about half the time — usually a photo uploaded straight from a phone. Too many plugins, third-party scripts and cheap shared hosting cover most of the rest. You can diagnose it yourself in ten minutes with PageSpeed Insights, free, no account. Test on mobile, not desktop. Most slow sites are fixable in hours, not weeks — don't let anyone sell you a rebuild before they've shown you the diagnosis.

Why is my website so slow?

Most slow websites are slow for one of seven reasons: oversized images, too many plugins, third-party scripts, cheap hosting, no caching, a bloated theme, or unoptimised code. Images are the most common single cause, and also the cheapest to fix.

The important thing to know before you spend money: slowness is diagnosable. You do not have to take anyone's word for why your site is slow, and you should be suspicious of a quote that arrives before a diagnosis.

How do I find out what's actually wrong?

Go to PageSpeed Insights (Google's free tool, no account needed), paste your URL, and read the Mobile tab.

Three numbers matter, and Google calls them Core Web Vitals:

Underneath the scores, PageSpeed lists specific opportunities in plain-ish English. You don't need to action them yourself — but you now have a list, and anyone quoting you can be asked to address it directly.

The seven causes, in the order they're usually to blame

1. Images uploaded at full size

A photo from a modern phone is often 4–6 MB and several thousand pixels wide. Displayed in a 600-pixel-wide slot on a website, the browser still downloads the whole thing.

Ten images like that is 50 MB. On a phone on mobile data, that's a page that takes fifteen seconds. The fix is resizing images to the size they're actually displayed at and serving them in a modern format. It's the highest-impact, lowest-cost change on most sites, and frequently the only thing that needs doing.

2. Too many plugins

Every plugin adds code that loads on every page — often on pages where it does nothing. A contact form plugin loading its scripts on your blog is pure waste. Sites accumulate these: a plugin gets installed to try something, the idea gets abandoned, the plugin stays.

3. Third-party scripts

Chat widgets, analytics, ad pixels, review embeds, cookie banners, font loaders. Each one is a request to someone else's server, and you're at the mercy of their speed. One slow tracking script can hold up your entire page. Worth auditing honestly: is the live chat widget you added two years ago producing enquiries? If not, it's costing you speed for nothing.

4. Cheap shared hosting

On budget shared hosting your site sits on a server with hundreds of others. When one of them has a traffic spike, everyone slows down. If your site is fast at 3am and slow at 2pm, this is a strong suspect. Hosting is one of the few places where spending a little more produces an immediate, measurable difference.

5. No caching

Without caching, your server rebuilds the same page from scratch for every single visitor. Caching stores the finished version and hands it out. It's usually a configuration change rather than a build.

6. A bloated theme or page builder

Multipurpose themes ship with features for every possible use case and load code for all of them whether you use them or not. Drag-and-drop page builders often generate deeply nested markup that browsers work hard to render. This one is genuinely expensive to fix, because the fix is usually a rebuild — be sure it's actually the cause before accepting that diagnosis.

7. Unoptimised code

Everything shipping in one large bundle, no lazy loading, blocking scripts in the page head. Relevant for custom-built sites; less commonly the cause on template sites, where causes 1–6 usually get there first. If you want the developer-level version, I've written up ten React performance fixes ordered by real-world impact.

Does website speed actually affect my business?

Yes, in two ways, and the first matters more.

People leave. Slow pages lose visitors before they ever see what you sell — and a visitor who leaves at three seconds costs you the same as one who never arrived.

Google notices. Core Web Vitals are part of Google's page experience signals. Speed alone won't outrank better content, but between two comparable pages it's a tiebreaker.

For a business site, the first reason is the one to act on. Someone who found you, tapped your link and gave up while it loaded was your warmest possible lead.

Test on mobile, not desktop

Your site probably feels fine to you — you're on a laptop, on wifi, with the site already cached in your browser. Your customer is on a phone, on mobile data, visiting for the first time. That's the experience that counts. PageSpeed Insights shows you both; read the mobile tab.

What should I do about it?

• Run PageSpeed Insights on your three most important pages, mobile tab. Free, ten minutes.
• Fix the images first. Resize and compress them. This is often the entire problem.
• Remove what you don't use. Plugins, chat widgets, tracking scripts you no longer read.
• Check your hosting if the site is slow at busy times and fine at quiet ones.
• Get a quote for the rest — and make sure the quote references your actual PageSpeed results.

One caution: if someone tells you the site needs rebuilding without first showing you a diagnosis, get a second opinion. A rebuild is sometimes the right answer. It shouldn't be the first answer.

Frequently asked questions

How fast should my website load?

Aim for a Largest Contentful Paint under 2.5 seconds on mobile — that's Google's threshold for "good". In practice, anything under three seconds feels fine to a visitor and anything over five loses a meaningful share of them before the page appears.

Will making my website faster improve my Google ranking?

It can help, but it's a tiebreaker rather than a main lever. Core Web Vitals are part of Google's page experience signals, so between two similar pages the faster one has an edge. Speed won't lift a page above better, more relevant content.

Why is my website fast on my computer but slow on my phone?

Two reasons: your computer has more processing power and usually a better connection, and your browser has already cached the site from previous visits. Your first-time mobile visitor has neither advantage. Always judge performance from the mobile test.

Do I need to rebuild my website to make it faster?

Usually not. Most slow sites are fixed by resizing images, removing unused plugins and scripts, and enabling caching — hours of work, not a rebuild. A rebuild is genuinely warranted when a bloated theme or page builder is the root cause, but that should be demonstrated with a diagnosis first.

How much does it cost to speed up a website?

Image and plugin cleanup is typically a few hours' work. Hosting upgrades are an ongoing monthly cost. A full performance rebuild is a project-sized number. Get the diagnosis before the quote — it's the only way to know which of those three you're actually looking at.

Where to start

Run PageSpeed Insights on your homepage, mobile tab, right now. Whatever it says at the top of the opportunities list is almost certainly your answer.

Speed is one symptom of a site quietly underperforming, and nine others worth checking are usually cheaper to fix than this one. If the real complaint is that nobody is finding the site at all, that's a different diagnosis — start here instead. And if you're weighing up whether any of it needs paying for, that line is drawn here.

For developers: the browser-side detail behind causes 6 and 7 goes further in the React performance list linked above, and the type-level habits that stop a lot of it being written in the first place are in TypeScript patterns for React.

If you'd like someone to read the results with you, book a free 30-minute call — and if the fix is an afternoon of image work, I'll tell you that rather than quote you a rebuild.