Why your website is fast at home and slow everywhere else

Sites feel fast next to origin and slow abroad because every request pays that RTT. Cloud CDN and Anycast DNS move the first hop.

Get started Performance

If the office is in the same city as the origin, every local test is a lie about Tokyo, Sao Paulo and Cape Town. Those users are not slow. They are far.

RTT compounds

DNS, TLS, HTML, then fonts, then JS, then images — each round trip adds the same ocean. A CDN hit collapses most of those to a nearby PoP.

Peering beats a pin on a map

A PoP without peering is still a long driveway. 14,000+ peering partners and 120+ IXPs are how 210+ locations stay on-path.

DNS has a country too

If authority is unicast in one region, the lookup is already slow. Anycast Cloud DNS answers close to the resolver.

Lab from more than one continent

Add checks from the markets you sell in. If TTFB tracks distance, buy edge, not more origin CPU.

Continue on Aptranet

Frequently Asked Questions

Is this always a CDN problem?

If the gap appears only far from origin, yes first. If it is slow next to origin too, profile the application.

Will one extra origin region fix it?

Multi-region apps still need DNS steering and a CDN for reusable bytes. Another origin is for state, not for CSS.

Does 30 ms average mean every city is 30 ms?

It is a worldwide average on the Aptranet network, not a promise for a single last mile. The point is not paying transoceanic RTT on every asset.