Free tool · Network & server
Website response time and uptime check
Is the site up, and how fast does the server answer? Three timed requests show DNS, connection, TLS, time to first byte and total time for each run.
Response Time Checker
What it measures
Where the waiting happens
The check sends three requests to the address, a quarter of a second apart, from HUB’s server. The first follows any redirects; the next two go straight to the final address. Each request is broken into phases, so you can see whether time is lost in DNS, the network, the TLS handshake or the application.
DNS
How long it takes to resolve the domain name to an address. Usually a few milliseconds when cached.
Connect and TLS
The TCP connection and the HTTPS handshake. High values point to distance from the server, network congestion or an overloaded server.
Time to first byte
From the start of the request until the first byte of the response arrives: connection time plus the server’s processing time. The median of the three runs is the headline number.
Total and availability
Total time to download the HTML, its size, the HTTP status and protocol, and whether the site is up. The HTML is measured, not images or scripts.
Why it matters
Everything else waits for the first byte
The browser cannot start rendering, and no image or script can load, until the HTML starts arriving. A slow time to first byte delays every other metric, including Largest Contentful Paint. web.dev’s guidance treats 0.8 seconds or less as good and more than 1.8 seconds as poor.
Slow server responses usually come from uncached pages that run expensive database queries, too little server capacity, or a server far from visitors without a CDN. Full-page caching often reduces time to first byte from seconds to tens of milliseconds for anonymous visitors.
One location, one moment
The measurement is taken from HUB’s server, not from your visitors’ devices or countries, and network conditions vary. Repeat the test at different times, and use real-user data (Chrome UX Report or your analytics) to judge actual experience.
Questions
About response time
A slow first request can be caused by redirects. Trace them with the HTTP Status & Redirect Checker.
Is this a ping test?
It replaces one. Classic ping uses ICMP, which many servers block and which says nothing about whether the website works. Timing real HTTP requests shows whether the site answers and how quickly.
Why is the first run slower?
DNS lookups, connection setup and cold caches on the server or CDN often make the first request slower. The median of three runs smooths that out.
Can it monitor my site continuously?
No, it runs when you ask. For continuous monitoring and alerts, use an uptime monitoring service; HUB can set one up as part of an operations plan.
Why is TTFB fast here but the site feels slow?
Time to first byte covers only the HTML response. Large images, render-blocking scripts and third-party tags can still make the page slow to use.
This tool came from ToolsPing?
Yes. It replaces ToolsPing’s ping tool, which ran the system ping command, with HTTP timing that needs no shell access.
Need help with what
the tools found?
HUB engineers implement technical SEO, performance, security and AI-readiness fixes on WordPress, Magento, custom PHP and modern JavaScript stacks.