Free tool
How fast does your site really answer?
We request your page from our server and time every phase of the trip, then check compression, caching, the certificate and the redirect chain.
What we measure
One real request, from our server to yours
- DNS: how long it takes to find your server
- Connect and TLS: opening the connection and agreeing encryption
- Server wait: the time your server spends before the first byte
- Download: the HTML itself, compressed or not
- Redirects: each one adds another round trip before anything shows
What we never do
Read only, and only what you ask for
We fetch the one address you type, with a plain browser-like request, and follow at most five redirects. We only connect to public addresses on ports 80 and 443. Results are kept for ten minutes so a shared link opens instantly, then deleted.
Want it fixed?
Turn a slow first byte into a fast one
Most slow sites have two or three causes: no edge caching, a slow database query on every page, or a chain of redirects. An architecture session finds yours.