Singapore hosting for sites an ocean from their server.
A European origin is around two hundred milliseconds away from Singapore before it does anything. Caching hides that on the front page and nowhere else.
Caching cannot fix distance.
It fixes the pages that repeat. Everything personal, transactional or logged-in still has to reach the origin, and from Asia that is where a European server becomes obvious.
The origin on the same side of the world
Checkout, admin and every signed-in page reaches the origin. From Singapore to Europe that is a fifth of a second before the server starts thinking, on every single request.
Round trips that add up
A page needing several sequential requests multiplies the distance. Reducing how many of those leave the region matters more here than anywhere closer to Europe.
Built for phones on mobile networks
Southeast Asian traffic is overwhelmingly mobile, often on connections where each extra request costs more than each extra kilobyte. Pages are assembled with that trade in mind.
PDPA questions answered plainly
Singapore's regime asks who holds the data and what happens when it moves. We will tell you where the origin and the backups are rather than naming a region cluster.
Regional reach, one origin
Malaysia, Indonesia, Thailand and the Philippines are all within a short hop of an in-region origin, and none of them are within a short hop of Frankfurt.
Two hundred milliseconds you cannot cache away.
Every guide says put a CDN in front of it. That works until somebody logs in, and then the geography of the origin is the only thing that matters.
- Origin placed in the Asia region
- Backups kept in the same region
- Pages built for fewer round trips
- Mobile-first delivery by default
The logged-in page tells the truth.
Any site looks fast on a cached homepage. Ask it to render a dashboard from Jakarta and the location of the origin is the entire result.
What we change for Singapore and SEA sites
Distance is not a setting you can turn off, so every row is about paying it fewer times.
| Setting | What we do | Why |
|---|---|---|
| Origin region | Placed in Asia rather than fronted by an Asian edge | An edge cache cannot answer a signed-in page, so from Singapore a European origin adds roughly a fifth of a second to every request that matters. |
| Round trips per page | Reduced in preference to reducing bytes | At this distance each additional sequential request costs more than the payload it carries, which reverses the usual optimisation order. |
| Mobile delivery | Assumed as the default rather than the fallback | Southeast Asian audiences are overwhelmingly on phones, frequently on networks where latency varies far more than bandwidth does. |
| Backup region | Held in the same region as the origin | Restoring across an ocean turns a short recovery into a transfer measured in hours, which is when the region of the backup stops being paperwork. |
| Data location disclosure | Stated per site for PDPA purposes | Singapore's regime asks who holds the data and where it goes, and a cluster name is not an answer to either question. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
I already use a CDN. Do I need an origin in Asia?
Does one Singapore origin cover the region?
Should I optimise images or reduce requests first?
What about PDPA?
Put the server on your side of the ocean.
Move the site to an Asia origin - migration is free, backups included.