About this tool
A page load is four journeys wearing one coat. DNS lookup turns the name into an address — slow here means a sluggish resolver or a domain with heavy records. The connection adds a handshake, and for HTTPS a second, encrypted one. Then comes the wait for the first byte, the truest measure of the server itself: database queries, application code and hosting quality all hide inside that single number. Finally the download, whose duration is mostly arithmetic — size divided by bandwidth.
Honesty about vantage point matters more than the numbers. This snapshot is taken from this site's server, so it measures the experience of a well-connected machine near other servers — a baseline, not a phone on a train in another country. A page that is slow even from here is slow for everyone; a page that is fast here may still crawl on a congested mobile network far away. Use the snapshot comparatively: before and after a hosting change, your page against a competitor's, the homepage against the heavy product page. The fetch runs through this site's gateway, follows redirects to the final page, and reports the downloaded size alongside the timings.
How to use it
- Paste the full address of the page to time.
- Press Take snapshot.
- Read the four timings and the size — the largest number names the bottleneck.
Good to know
- A first-byte wait over ~600 ms from a server baseline points at the application or hosting, not the network — caching or a plan upgrade, not a CDN slogan, is the fix.
- Run the snapshot three times and compare the middle result; single timings catch other tenants' busy moments on shared infrastructure.
- Compare like with like: a 3 MB page will always download slower than a 300 KB one. Size is a speed feature all by itself.
Frequently asked questions
Why is my own test on my phone slower?
Because your phone is further away, on a busier network, doing more work per byte. This snapshot is the server-side baseline — the floor below which your page cannot go.
What is a good first-byte time?
Under 200 ms is strong, 200–600 ms is typical of ordinary shared hosting, and beyond that the server or application needs attention.
Does the snapshot load images and scripts too?
No — it times the main document itself, which is where the journey starts. A page whose document is fast but which then loads megabytes of extras needs its assets audited separately.
More Network tools
IP Lookup
Look up an IP address: its hostname, version and address class — or leave it blank to inspect your own.
DNS Lookup
Read the live DNS records for any domain — A, AAAA, MX, NS, TXT, CNAME, SOA and CAA, straight from DNS.
HTTP Headers Checker
See the exact response headers any web address sends — status, security headers, caching and server clues.
SSL Checker
Inspect any site's HTTPS certificate: who issued it, when it expires, and which names it covers.
Whois Lookup
Read the public Whois record for a domain: registrar, creation date, expiry and registration status.
Redirect Checker
Follow a web address hop by hop: every redirect, its status code, and where the chain finally lands.
Making videos too? Try our YouTube Video Analyzer, or browse the full Toolkit and the free YouTube tools.