Find where your site or API is slow - worldwide

Run a global latency test for your website or API from 5 regions in seconds.

No account required.

Test Your Website or API

Start with a preview snapshot: one request per region.

Enter your website URL (https://example.com ) or API endpoint.

Human Check

Cloudflare Turnstile protects this form from automated abuse.

Runs from 5 global locations automatically
Europe - AmsterdamNorth America West - San FranciscoNorth America East - MontrealAsia - SingaporeAsia - Tokyo

Results in under a minute

Fast to Run

Send a single request per region and see results fast.

Global Snapshot

Amsterdam, SFO, Montreal, Singapore, Tokyo.

Straight to the Point

Latency, status, and regional comparison.

How do popular services hold up worldwide?

See how well-known sites and APIs feel from different regions, from normal loads to rougher response times.

View all benchmarks →
How fast is Google thumbnail

How fast is Google

www.google.com

47ms
Typical
47 ms
On a bad day
80 ms
Best region
Singapore
How fast is Google Fonts thumbnail

How fast is Google Fonts

fonts.googleapis.com/css2?family=Geist:wght@400;500;60...

16ms
Typical
16 ms
On a bad day
74 ms
Best region
Singapore
How fast is npm Registry thumbnail

How fast is npm Registry

registry.npmjs.org

22ms
Typical
22 ms
On a bad day
40 ms
Best region
San Francisco

Latest articles

Short takes on latency tradeoffs that matter when you need to ship, not read a textbook.

View all articles →
Learn5 min read

How to test your API latency from multiple regions without setting up infrastructure

Your laptop says the API is fast. Your users on the other side of the world are telling you something else.

A practical guide to checking API latency from several regions, understanding what the numbers mean, and turning that into an infrastructure decision.

Published April 3, 2026Read article
Learn4 min read

TTFB: the number that determines whether Google can rank your site

You've probably never measured it. It's probably the biggest performance problem you have.

Time to First Byte controls when rendering can begin, which is why it quietly drags down LCP, Core Web Vitals, and search performance.

Published March 19, 2026Read article