Time how fast a site's server answers
Type an address. We time one request from our server: DNS, connect, TLS, time to first byte and download, with the HTML size and compression. It measures the server, not page rendering. Free, no account.
How the test works
- The address is parsed first: http and https only, ports 80 and 443 only, no usernames, no IP addresses and no internal names such as localhost. Anything else is refused before any request.
- The name is resolved and every address it points to must be public. Private, loopback, link-local (cloud metadata included), multicast and reserved addresses are refused, and the connection goes to the address that was checked.
- We time one GET from our server: resolving and checking the name, opening the connection, the TLS handshake, the wait for the first byte and downloading the HTML (3 MB at most). Redirects are followed and timed too.
- We ask for gzip, deflate or Brotli, so you see whether the server compresses, and report the bytes sent.
- Only the HTML document is fetched. Images, scripts and styles are not downloaded and nothing is rendered.
What this measures, and what it does not
This is server response time, measured from our server. It is not Core Web Vitals, not Lighthouse and not what a visitor on a phone sees. For those, use PageSpeed Insights, which shows lab results and, for busy sites, field data from real Chrome users. Server time is still worth knowing: a slow first byte delays everything that comes after it.
A first byte over a second usually points at slow hosting, no page caching or a heavy plugin. That is a concrete fix to offer a local business. To find businesses to check, search 67Leads by trade and city.
Get 67 leads free No card. Search free with contacts masked.
Page weight checkerHTTP headers checkerRedirect checkerWebsite down checkerMobile-friendly test
Questions
web.dev's guide treats 0.8 seconds or less as good for real visitors and over 1.8 seconds as poor. Measured from a server, as here, times are often lower than a visitor on a phone network sees.
No. PageSpeed loads the whole page in a browser and reports Core Web Vitals. This test times only the server's answer for the HTML, which is the first step of that load.
Server load, caching and the network change from moment to moment. This is one sample; run it a few times and look at the typical value.
Our server may already have the answer cached from an earlier lookup. A first-time visitor can wait longer.
No. Our server fetches the address you enter, times each step of the request and reports what it found. No AI model is involved, and the address and result are not stored.
More free tools
Local business counterNo-website business finderLead list previewCold email template generatorAI crawler checkerllms.txt generatorllms.txt checkerLocal business schema generatorFAQ schema generatorrobots.txt generatorMeta tag checkerSchema markup checkerNAICS code lookupSIC code lookupSSL certificate checkerRedirect checkerBroken link checkerPage weight checkerLead list column mapperMerge tag checkerOpen Graph checkerCanonical tag checkerSitemap validatorHTTP headers checkerHeading structure checkerImage alt text checkerHreflang checkerDNS lookupAI Overview readiness checkerIndexability checkerRobots.txt testerMixed content checkerFavicon checkerSocial profile finderNofollow link checkerAll Website checks toolsAll tools