Most conversations about site speed end up being about scores. A number goes up, everyone is pleased, and nothing changes in the business. The reason to care is simpler than that: people leave. On a phone, on mobile data, in a country where connections vary enormously between one district and the next, a slow site is a closed door.
Where the time actually goes
In our experience rebuilding sites for Indonesian businesses, three things account for most of the delay, and none of them is the thing people expect.
The first is images shipped at the wrong size — a two-megabyte photograph scaled down by the browser to fill a thumbnail. The second is the page builder: a visual editor that produces a deeply nested page and loads its own framework to run it. The third is third-party scripts, especially embedded maps and chat widgets, which quietly fetch hundreds of kilobytes before anyone has asked for them.
What we do about it
We export images at the size they will actually display, and serve modern formats. We build on plain HTML and CSS, so there is no framework to download before the first word appears. And we defer anything from a third party until a visitor actively wants it — a map loads when you click it, not when you arrive.
The result is usually a site that loads in a fraction of the time on the same connection, which is not a technical achievement so much as a commercial one.