How this test works
One selected Globalping probe makes a restricted HTTP or HTTPS request without custom headers, cookies, credentials, or request bodies.
SYNTHETIC HTTP TIMING
Website Speed Test
Measure DNS, TCP, TLS, first byte and download timing.
Remote synthetic measurement
Test completedResults are ready.
How to read the result
Use DNS, TCP, TLS, first-byte, and total time to locate delay. Redirect responses describe only the returned hop, not a browser waterfall.
Frequently asked questions
What is TTFB?
Time to first byte: the delay between sending the request and receiving the first byte of the response. Under 200 ms in the same region is good; over 500 ms usually means server work is the bottleneck.
Is this the same as Google PageSpeed Insights?
No. This is a server-side timing from a single remote probe. PageSpeed Insights runs a real browser and measures Core Web Vitals, including rendering. Use each for what it's good at: server health here, front-end performance there.
Why is my website slow from another country?
Distance adds latency to every round trip, and without a CDN the routing may be suboptimal. Run the test from each region to separate unavoidable distance from fixable problems.
Does HTTPS slow down my website?
Minimally. TLS 1.3 costs one extra round trip at connection time, a few milliseconds on healthy paths, and the security gain is worth it. The exception is a misconfigured or CPU-bound TLS setup, where it genuinely slows things down.
What is a good speed test result?
Measured in the same region on a healthy site: DNS under 50 ms, TCP and TLS under 50 ms each, first byte under 200 ms, and a total time proportional to the page size. Absolute numbers depend on distance and page weight.
Learn how website speed test works
Read the guide Test website speed in 2026 from remote probes. Learn DNS, TCP, TLS and TTFB timings, benchmark numbers and Core Web Vitals limits.