Measure how long a page takes to respond, right from your browser.
This measures response time from your current location and connection. Results will differ from lab tools that simulate fixed network conditions from data-center locations.
Website Speed Test measures how long it takes to receive the base HTML document from a URL, giving you a quick, honest signal of server responsiveness — how fast the origin server answers a request, before a browser even begins downloading images, stylesheets, scripts, or rendering the page.
The test starts a high-resolution timer, requests the page through a CORS-enabled relay, and stops the timer the moment the response arrives, reporting the elapsed time in milliseconds along with the size of the HTML received and the HTTP status code. This is genuinely useful as a server response-time indicator, but it is deliberately transparent about its limits: it does not simulate a full page load with all sub-resources, does not measure JavaScript execution or rendering time, and reflects conditions from your current network and location rather than a fixed reference data center the way lab tools like Lighthouse or GTmetrix do.
Server response time is the foundation every other performance metric builds on — if the base document itself takes seconds to arrive, no amount of front-end optimization elsewhere can compensate. Google's Core Web Vitals and general UX research consistently show that response delays beyond roughly one second measurably increase bounce rates, and slow first-byte times are a common early symptom of undersized hosting, unoptimized database queries, or missing server-side caching.
Use this tool as a quick, repeatable pulse-check on server responsiveness, especially useful for comparing before/after a hosting change or caching fix. For a full performance audit including image weight, render-blocking scripts, Core Web Vitals scoring, and multi-location testing, pair this with a dedicated lab tool that measures the entire page load lifecycle.
PageSpeed Insights measures full page load including every resource and computes Core Web Vitals from real or simulated device performance; this tool measures only the base document's response time from your current connection.
As a rough guide, under roughly 500-900ms is considered good server responsiveness, over about 2 seconds signals a real bottleneck worth investigating.
Network conditions, server load, CDN cache state (cold vs warm) and even the relay's own path can all shift results slightly between runs — run it a few times for a representative average.
Not necessarily — a fast server response can still be followed by a slow-loading page if it references large uncompressed images, blocking scripts, or excessive third-party trackers.
Any publicly accessible URL can be tested, including individual blog posts, product pages, or API endpoints that return HTML.
Idiot Website Tools