How a slow website loses customers: measure it in two minutes, and what to fix

Most people in Thailand open your site on a phone using mobile data, not office wifi. Google's own research found that each additional second of load time measurably increases the number of people who leave. This article covers what that costs you, how to measure it yourself, and the causes we find most often.

1. What a slow site actually costs

• Customers lost before they see anything. They tap back to the results before learning what you sell.
• Ranking. Speed is a ranking factor, and it hurts again indirectly when people bounce.
• Ad budget. You pay for the click and they never wait for the page.
• Credibility. A site that stalls reads as a business that does not pay attention.

The painful part is that you cannot see the loss. People who leave before the page loads often are not counted at all.

2. Measure it yourself in two minutes

Open PageSpeed Insights, enter your address, and look at two things.

• The mobile score. Under 50 needs urgent work, 50–89 is passable, 90 and above is good.
• When the main content appears. It should be under 2.5 seconds.

The most honest test is simpler: turn off wifi and open your site on mobile data, counting the seconds until you can read it. If it feels slow to you, it feels slower to someone with no attachment to your business.

3. The five causes we see most often

Oversized images

The number one cause. Photos uploaded straight from a camera at 3–5 MB each, when the page displays them a few hundred pixels wide. Ten of those is a 30 MB page.

Plugins nobody uses

Themes load the code for every feature they ship with, used or not. We routinely find sites that sell nothing online still loading a full shopping cart on every page.

Too many font weights

Each weight is a separate file. Four weights in two languages is eight files to wait for.

Background video

Beautiful on a desktop. On mobile data it asks the customer to download tens of megabytes before seeing anything.

Hosting far away

If the server is on the other side of the world, every page begins with a round trip before anything loads.

4. What you can fix without rebuilding

• Resize images before uploading. A normal page image should be under 200 KB. WebP is around 30% smaller than JPG at the same quality.
• Turn off unused plugins. Go through them one at a time.
• Drop background video on mobile and use a still image.
• Cut font weights to two per language.

Those four often halve load time without touching the structure.

5. Why static sites are faster by nature

An ordinary site works like this: someone opens a page, the server queries a database, assembles the page, then sends it. Every visit, every page.

A static site has the pages already built. A request is answered with a file that already exists, and those files sit in data centres around the world, so each visitor is served from the nearest one.

It is also safer, because there is no database and no plugins to exploit, and cheaper to host because nothing has to compute.

6. Repair or rebuild

• Repair if the structure and content are sound and the problem is images and plugins.
• Rebuilding usually wins if the mobile score is under 30, the theme is old, and the page structure no longer matches the business.
• Rebuild if you cannot edit the content, nobody maintains it, or the original developer is unreachable.

If you are unsure, send us the link for a free review and we will tell you plainly which it is.

FAQ