Why your website loads slowly — and how to fix it

A customer messages you: “your website takes forever to load.” You open it yourself and watch a white screen spin for a few seconds. It feels mysterious, but most slow websites share the same handful of culprits — and you can fix several of them without touching code. Here are the four most common ones, in order of how often they show up, plus how to diagnose your own site with a free Google tool.

The number one culprit: heavy images

This is the problem I see on almost every slow site. A restaurant owner shoots twenty dishes on their phone, 4–5MB each, and uploads them straight to the website. The homepage alone ends up carrying close to a hundred megabytes of photos — on mobile data that means a long wait, and visitors rarely wait.

Here’s what few people realize: a phone screen only needs a few hundred kilobytes per image to look perfectly sharp. A 5MB photo and a 300KB photo look identical on screen; the only difference is how long your visitor sits there waiting.

On a phone screen, a 5MB photo and a 300KB photo look identical — the difference is how long your visitor waits.

The fix: compress images before uploading. Convert them to WebP — a lightweight image format that keeps the sharpness at a fraction of a JPG’s size. Google’s free tool squoosh.app does it right in the browser: drag a photo in, download the compressed copy. While you’re at it, resize photos to around 1,200–1,600 pixels wide — plenty for any website.

Cheap hosting, or a server too far away

Hosting is where your website lives — a server somewhere that stores the whole site. Bargain plans cram hundreds of websites onto one machine, so at peak hours every site on it crawls.

Server location matters just as much. I once looked at the website of a Da Lat homestay: every guest was Vietnamese, but the server sat in the US. Every tap sent data on a round trip halfway around the planet before anything appeared.

The fix: ask your provider directly — “where is the server located?” — and pick a plan hosted in Vietnam or Singapore. Switching hosts sounds like a big deal, but the new provider usually migrates your site for free, and the price difference is small. Your visitors will feel it immediately.

Bloated themes and stacked plugins — the classic WordPress ailment

The usual story: you buy a theme — a ready-made design — that looks gorgeous in the demo. But those themes tend to be “multipurpose”, carrying code for hundreds of website styles; you use one style, yet every visitor downloads the whole bundle. Then over the years you add plugins — bolt-on extras: one for bookings, one for popups, one for stats, one for Facebook sharing. Each adds a little weight, and together the page has to pull down a pile of stuff before it can show anything.

I once counted 23 plugins on a spa’s website. The owner could remember using about six.

The fix: open the plugin list and deactivate anything you can’t remember the purpose of (don’t delete yet). Run the site for a week; if nothing’s missing, delete them for good. No code required. A bloated theme is harder — replacing it means rebuilding the design, which brings us to the last section of this article.

Too many things embedded from outside

An auto-playing YouTube video, a Facebook chat box, a map, three or four fonts loaded from overseas — every embed makes your page wait for yet another server to respond. None of these is bad on its own; the problem is stacking them all on one page.

One spa site I reviewed had the full combo: an autoplay intro video, a chat widget, fancy fonts, plus an ad-tracking script. On a phone, the page loaded inch by inch.

The fix: keep the one or two embeds that actually bring in customers and drop the rest. For video, show a cover image and load the video only when someone taps play — never autoplay. Swap the chat box for a simple Zalo button, far lighter and what Vietnamese customers reach for anyway. Keep one font, two at most.

Diagnose it yourself with PageSpeed Insights

No need to guess which problem your site has. Google offers a free tool called PageSpeed Insights (pagespeed.web.dev): paste in your website address, hit analyze, and wait about half a minute for the results.

• Check the Mobile score first — most of your visitors are on phones, and the mobile score is always the harsher one.
• Scroll to the suggestions: the tool names the exact images that are too heavy and the embeds that eat the most time.
• You don’t need to understand every technical term. If it keeps mentioning images, images are your culprit; if you spot YouTube or Facebook in the list, it’s the embeds.

Run it once before your fixes and once after, and watch the score climb — satisfying, and proof you fixed the right thing.

When to patch, and when to rebuild

If the site is fairly new and slow mostly because of heavy images and a few spare plugins, patch it: an afternoon of compressing images and removing plugins — plus a hosting move if needed — makes a difference visitors can feel.

But some sites never get better no matter how much you patch: four or five years old, a theme that stopped receiving updates, fixing one thing breaks another, and PageSpeed stays red. That’s when a rebuild makes sense — add up the money and hours spent patching over the years and it often equals the cost of a new site, except the new site cures the disease for good.

At Seawin Tech we build websites the static way: every page is pre-built into finished files, so it appears the moment a visitor opens it — no server assembling the page on each view. No multipurpose theme, no plugin stack, so there’s nothing left to slow down over the years.