Speed9 min readOctober 31, 2026

Why is my website so slow?

Seven things cause almost every slow website. Here’s what each one costs you, how to spot it, and what fixing it looks like.

The load racetime to main content, phone connection
0s2s4s6s8s10s Google's "good" line · 2.5s WordPress sitewith a page builder Hand-builtbusiness site This website 11.2s 2.6s 0.9s
Largest Contentful Paint from Lighthouse, mobile preset, measured October 2026. The first is a marketing agency’s own homepage; the second is a roofing company’s site; the third is gbfm.dev.

A slow website doesn’t look broken. It loads eventually, the photos are nice, and when you check it on your own phone over Wi-Fi it seems fine. The problem is what happens on someone else’s phone, on a weak signal, in the five seconds before they give up.

The good news: almost every slow site is slow for one of the same seven reasons. None of them are mysterious, and most are fixable without starting over. Here they are, roughly in order of how often I find them.

10%

of visitors lost for every extra second a page took to load, in the BBC’s own testing

+8%

in sales for Vodafone after a 31% improvement in how fast the main content appeared

43%

better bounce rate for The Economic Times after passing Google’s speed thresholds

Sources: Google’s web.dev case studies, which link to the original reports.

First, find out how slow it actually is

Don’t guess. Google gives away the tool it uses itself. Go to pagespeed.web.dev, paste in your address, and wait about a minute. You’ll get a score out of 100 and a list of what’s wrong, for phones and for desktop separately. Look at the phone result first. It’s almost always worse, and it’s where a lot of your visitors are.

The number that matters most is Largest Contentful Paint, or LCP. That’s how long it takes for the biggest thing on the screen, usually your main photo or headline, to show up. Google’s own line is 2.5 seconds. Under that is good. Over 4 seconds is what Google calls poor.

Largest Contentful PaintGoogle’s thresholds
0s2.5s4s6s+ GoodNeeds improvementPoor most sites I’m asked to look at: 4–8s
Thresholds from Google’s web.dev documentation. The marker is my own experience, not a statistic.

Now the seven causes. Each one comes with what it costs you and what the fix looks like.

01Images that are far too big

This is the number one cause, by a mile. A photo straight off a phone is 3 to 8 megabytes and about 4,000 pixels wide. On your website it’s shown at maybe 800 pixels wide. The visitor still downloads the whole thing, then their phone shrinks it. Multiply by every photo on the page and you’ve got a site that moves 30 megabytes to show a few pictures of your work.

What it costs: this is usually the whole difference between a 2-second site and an 8-second one.

The fix: every image gets resized to the size it’s actually displayed at, saved in a modern format (WebP or AVIF, which are a fraction of the size of JPEG and PNG at the same quality), and told its dimensions so the page doesn’t jump when it loads. Images further down the page wait until you scroll near them. Done properly, the same page goes from 30 megabytes to under 1.

02Too many scripts

Chat widgets. Tracking pixels. A review slider. A pop-up tool. The Facebook thing. Each one is a piece of code that has to download and run before the page is usable, and they add up fast. A page with ten plugins can easily spend three or four seconds just running code before it responds to a tap.

What it costs: the page looks loaded but doesn’t respond. Buttons that don’t work for a few seconds feel broken, and people leave.

The fix: remove what you don’t use. For what’s left, load it after the page is up, not before. A chat bubble doesn’t need to be the first thing that loads.

03A heavy theme or page builder

Most small-business sites are built on a template with a drag-and-drop builder on top. That’s convenient, but the builder ships code for every feature it offers, not just the ones you use. Your three-page site loads the same machinery as a thousand-page one.

This is measurable. Every year the HTTP Archive tests millions of websites and publishes the median Google performance score by platform. On phones, none of the major platforms clear 60 out of 100.

Median performance score on phones, by platformout of 100
05090 DudaWixWordPressWeeblySquarespace 5955383330
0–49 poor50–89 needs improvement90–100 good
Median mobile Lighthouse performance score by CMS, 2024. Source: HTTP Archive Web Almanac 2024, CMS chapter.

What it costs: a permanent handicap. You can optimize images and remove plugins and still be stuck in the 40s, because the platform itself is the weight.

The fix: on a builder, use the lightest theme you can and resist adding features. If speed matters to your business, this is the point where a site built from scratch makes sense: it only contains what your site needs.

04Cheap or far-away hosting

Before any of your page can load, the server has to answer. On a $4-a-month shared plan, your site shares a computer with hundreds of others, and the first byte can take over a second to arrive on a bad day. If the server is on another continent from your customers, add more.

What it costs: half a second to a second and a half, before anything else even starts.

The fix: hosting that keeps copies of your site in many locations and serves the nearest one (a CDN). For most business sites this is cheap or free, and it’s what fast sites use by default.

05Web fonts loaded the wrong way

Custom fonts are fine. Loading six weights of three families from a third-party server, before the text is allowed to appear, is not. Visitors stare at a blank page while fonts download, or watch the text flash and reflow when they arrive.

What it costs: a blank or jumping page for the first second or two, which is exactly when people decide whether to stay.

The fix: two or three font files, hosted on your own domain, in the compressed woff2 format, with the text shown in a fallback font first and swapped once the real one lands. Done right, nobody notices the swap.

06Embeds: maps, videos, social feeds

A YouTube video embedded on your page loads YouTube’s entire player, whether or not anyone presses play. A Google Map does the same. An Instagram feed pulls in a whole app. One embed can weigh more than the rest of your page combined.

What it costs: several seconds and a lot of data for a video most visitors won’t watch.

The fix: show a still image that looks like the video or map, and only load the real thing when someone clicks it. Visitors can’t tell the difference, except that the page is fast.

07Things that jump around while loading

You go to tap a button and an image loads above it, pushing it down, so you tap an ad instead. That’s a layout shift, and Google measures it (it calls it Cumulative Layout Shift). It’s caused by images without set sizes, fonts arriving late, and banners that get injected at the top after the page is up.

Layout shiftthe image arrives late and the button moves
image, no size set
Call now
When the image has its width and height written in the code, the browser leaves the right-sized gap and nothing moves.

What it costs: mis-taps, frustration, and a lower Google score (layout shift is a quarter of the performance grade).

The fix: every image and embed gets its dimensions set so the space is reserved before it loads. Fonts are matched to their fallbacks so text doesn’t reflow. Nothing gets inserted above content that’s already on screen.

What to do about it, in order

If you’re fixing an existing site, this order gets you the most for the least effort:

  1. Run the test at pagespeed.web.dev on your phone result and write down the LCP number.
  2. Shrink the images. Biggest win, least risk. Resize, convert to WebP, add dimensions.
  3. Delete plugins and embeds you don’t truly need. Replace videos and maps with click-to-load versions.
  4. Sort out the fonts. Fewer files, self-hosted, swapped in after the text shows.
  5. Move to better hosting if your first byte is slow.
  6. Re-run the test. If you’re still under 50 after all that, the platform is the problem, and that’s a different conversation.
Honest note

A site built from scratch isn’t automatically fast. I’ve seen hand-coded sites with 10-megabyte hero images. What a custom build gives you is the option of being fast, because nothing is on the page that you didn’t put there. Every site in my gallery is tested the same way you’d test it: paste the address into Google’s tool and read the number.

Speed isn’t a feature you add at the end. It’s what’s left when you stop adding things.

Want me to look at your site?

Send me the address and I’ll tell you what’s slowing it down, what it’s missing, and what I’d fix first. No charge, no pressure.

Get a free look →