Why your page feels slow on Malaysian mobile data

A page that opens in one second on office wifi can take eight seconds on a phone in a moving car. The cause is almost never the hosting bill.

Start with the largest file

Open the page on a phone and look at what arrives first. In most builds we audit, one image weighs more than the rest of the page combined. A photo straight from a camera is three to six megabytes. On a modest mobile connection that is several seconds of waiting for a picture nobody asked for at full resolution.

The fix is boring and effective: size the file to the size it will be displayed, export to WebP, and keep hero images under a few hundred kilobytes.

Then count the scripts

Every third party script is a DNS lookup, a connection, and a download before it does anything. Chat widgets, tracking pixels, font loaders, carousel libraries. Each one is a promise to be slow later in exchange for convenience now.

We ask one question per script: what breaks if this is not here? If the answer is “nothing visible”, it goes.

Then check what the server does

If the page is generated on every request, the server does work before it sends anything. On shared hosting with a busy neighbour, that work can take a second all by itself. A static page has nothing to generate, which is why a small business page usually belongs as a file.

How to decide

Measure on a real phone on real mobile data, not in a desktop browser with throttling switched on at the end. Then fix the biggest file first, remove scripts second, and only then consider changing hosts. In our experience the host is the last suspect, not the first.