Software is usually demonstrated on a new laptop with office internet. It is usually used on a phone, on mobile data, sometimes with one bar of signal. A system that feels instant in the meeting room can take far longer to open in the barangay where the service is needed. We build for the second place, not the first.
What people here actually use
Start with the device. In October 2026, phones accounted for 60.79 percent of web use in the Philippines as measured by Statcounter, against 37.68 percent for desktop computers.1 Among phones, 86.28 percent ran Android.2 That figure does not say how many are entry-level models, and we have found no public figure for the Bangsamoro. We assume many are, and we test on that assumption.
Then the connection. Ookla's Speedtest Global Index, updated in September 2026, put the Philippines' median mobile download speed at 66.97 megabits per second, ranked 72nd among the countries it measures. The median fixed broadband speed was 119.03 megabits per second.3
A median is the middle value, so half of all those tests were slower than that. We also assume a national figure leans toward the places where most tests are run. We read it as the best case, not the normal case, for a user far from a city center.
Why the weight of a page matters
Page weight is the total size of everything a browser must download to show a page: the text, images, fonts and program code. The HTTP Archive, in its 2024 Web Almanac, found that the median page sent to phones in October 2024 weighed 2,311 kilobytes, about 2.3 megabytes. That is 357 percent more than ten years earlier. Images made up the largest part, with a median of 900 kilobytes on mobile home pages.4
The same report is direct about who pays for this. Heavy pages weigh most on people who cannot afford high-end devices or fast connections with generous data allowances, and in the worst cases the page becomes practically unusable for them.4
There are two costs. One is time, because a slow connection takes longer to carry a bigger page and a slow phone takes longer to process it. The other is money, because a person on a metered data plan pays for every megabyte, including the ones spent on decoration they never asked for.
How speed is measured in plain terms
Google publishes three measures called the Core Web Vitals. Each one describes something a user feels.5
The first is how soon the main content appears, which should be within 2.5 seconds of the page starting to load. The second is how quickly the page reacts when you tap or type, which should take 200 milliseconds or less, a fifth of a second. The third is whether things jump around while loading, the reason you sometimes tap the wrong button because the page shifted under your thumb. That is scored on a scale where 0.1 or less is good.5
The important detail is how the targets are judged. A page meets them only if 75 percent of real visits do, counted separately for phones and desktops.5 A site cannot pass by being fast for its best-equipped visitors.
- Loading: the main content shows within 2.5 seconds.
- Response: a tap gets a reaction within 200 milliseconds.
- Stability: the layout does not shift while you read or tap.
Sending pages that are already made
The biggest decision is where the page gets assembled. In many modern systems the server sends a nearly empty page and a large bundle of program code, and the phone builds the page itself. Google's engineering guidance notes that this approach is difficult to make and keep fast on mobile devices, because the code tends to grow as the system grows.6
The alternative is to prepare the page ahead of time and send it ready to read. When pages are built once, before anyone asks for them, the server does not have to generate the page for each request, and the first content appears quickly and consistently.6 The phone only has to display what it receives.
Our own website works this way. Every public page is prepared when we publish a new version of the site, and the server hands over finished pages. We think this suits most public information: service guides, requirements, announcements and directories change a few times a week, not a few times a second.
Loading the heavy parts late, or not at all
Images are the next target. Browsers can now be told to wait before fetching an image that is further down the page, and to fetch it only when the reader scrolls near it.7 A visitor who reads the first two paragraphs and leaves never pays for the photographs at the bottom.
The same thinking applies to video and animation. On our home page the video player is not loaded until a visitor presses play, and the animated background stops drawing when it is scrolled out of view. Features like these are easy to add and easy to forget to restrain.
The last technique is the plainest: leave things out. Every font, tracking script and decorative effect is a download. Before adding one, we ask what the user would lose without it. Often the honest answer is nothing.
What to expect and what to ask
If you are buying or commissioning a system, ask to see it on the cheapest phone your staff or clients own, using mobile data, not office Wi-Fi. Time how long the first screen takes to become usable. Ask the supplier how much data one visit uses, and what happens when the signal drops halfway through a form.
A supplier who has thought about these questions will have answers ready. In our view, speed on modest equipment is a matter of fairness as much as engineering. A public service that only loads well on an expensive phone has quietly chosen who gets served first.
Sources
- Desktop vs Mobile vs Tablet Market Share Philippines. Statcounter Global Stats, October 2026.
- Mobile Operating System Market Share Philippines. Statcounter Global Stats, October 2026.
- Philippines's Mobile and Broadband Internet Speeds - Speedtest Global Index. Ookla, September 2026.
- Page Weight, chapter 16 of the 2024 Web Almanac. HTTP Archive, 2024-12-30.
- Web Vitals. web.dev, Google, 2020-05-04, updated 2024-10-31.
- Rendering on the web. web.dev, Google, 2019-02-06, updated 2026-01-05.
- Browser-level image lazy loading for the web. web.dev, Google, updated 2024-08-13.