Why your website is slow

Why is your website slow? In most small business sites I review, the answer is one of a short list: oversized images, a heavy theme or page builder, too many plugins, third-party scripts like chat widgets and trackers, web fonts, and cheap or overloaded hosting. The good news is that the first two or three fixes usually bring most of the improvement, and some you can do yourself.

Speed matters because people visiting a local business site are often on a phone, on mobile data, in a parking lot or between jobs. If the page takes too long, they go back to Google and tap the next result. You never see them in your enquiries, only as a bounce in analytics.

How to measure speed without fooling yourself

Before fixing anything, measure honestly.

• Test on a real phone with Wi-Fi off. Your office connection hides problems your customers see.
• Use Google PageSpeed Insights. Look at the mobile tab and the "Core Web Vitals" section, which reflects data from real visitors when there is enough of it.
• Check several pages, not only the homepage. Service pages and blog posts often carry heavier images.
• Write the results down so you can compare after each change.

Do not chase a perfect score. A score is a lab estimate; what matters is how fast the main content appears and how soon visitors can tap the button they came for.

Cause 1: images that are far too big

The most common culprit. A photo straight from a modern phone can be several megabytes, and the browser downloads all of it even when it is displayed at the size of a postage stamp.

Fix: resize images to the largest size they actually appear at, compress them, and use modern formats like WebP or AVIF. Add lazy loading so images below the fold load only when the visitor scrolls. On many sites this alone makes a visible difference.

Cause 2: a heavy theme or page builder

Multipurpose themes and visual builders ship code for hundreds of features you never use: sliders, galleries, animations, icon sets. Every visitor downloads it anyway.

Fix: switching off unused modules helps a little. The real fix is a lighter build. This is one of the reasons I hand-code sites or build them on a light custom CMS: the page carries only what it needs. If you are weighing platforms, the comparison in WordPress or a custom website goes into this in more depth.

Cause 3: too many plugins

Each plugin may add its own scripts and styles to every page, plus database queries on the server. Twenty plugins doing small jobs can slow a site more than one big feature.

Fix: list your plugins and ask of each one: does it earn its place? Remove anything unused, replace overlapping ones, and keep the rest updated.

Cause 4: third-party scripts

Chat widgets, review carousels, booking embeds, social feeds, heat-mapping tools and several tracking pixels each load code from someone else's server. You cannot control how fast those servers are.

Fix: keep only scripts you actually use and review. Load trackers through Google Tag Manager so you can see and manage them in one place. Delay non-essential widgets until after the page is usable. And if you have three analytics tools doing the same job, pick one.

Cause 5: web fonts

Four font families with six weights each can add a surprising amount to every page.

Fix: use one or two families, only the weights you need, host them with the site, and set them to show fallback text immediately so visitors are not staring at a blank page.

Cause 6: hosting

Very cheap shared hosting can be slow to answer the first request, especially at busy times. Distance matters a little too: a server far from Canada adds delay to every request.

Fix: choose hosting suited to your site's size, with server-side caching and a CDN for static files. Hosting is not where you should save the last few dollars. With my clients, hosting is agreed individually based on what the site needs.

Cause 7: no caching

Without caching, the server builds each page from scratch for every visitor.

Fix: enable page caching and browser caching, and serve static files through a CDN. On most platforms this is a setting, not a project.

Cause 8: video and animations

Background video on the first screen and scroll animations look impressive in a presentation and cost real seconds on mobile.

Fix: replace autoplay video with a still image and a play button. Keep animation subtle and light.

Fix it or rebuild it?

Here is how I usually decide with clients:

Situation	Usually better to
Images and caching are the main problems	Fix: a few days of work
A few heavy plugins or scripts	Fix: remove or replace them
A page builder theme everywhere, slow on every page	Rebuild: the weight is built in
The site is slow and also outdated or not converting	Rebuild with speed in the plan from day one

If the fixes cost almost as much as a new site and leave you with the same old structure, rebuilding is the better deal. A rebuild with me keeps your domain and moves your content, with redirects so Google does not lose track of your pages. You can read more on the website speed optimization page or, if a rebuild looks likely, on website redesign.

A ten-minute self-check you can do today

1. Open your homepage on your phone with Wi-Fi off and count how long until you can read the headline.
2. Run the page through PageSpeed Insights and note the mobile results.
3. Right-click the largest photo on your homepage and check its file size.
4. Count your plugins or embedded widgets.
5. Ask yourself whether each one brings customers.

If the numbers worry you, send me the address. I won't promise a specific score, because no honest developer can, but I'll tell you what slows the site and what it would take to fix. The first 30-minute consultation is free.