You don't need a paid tool or a plugin to measure how fast a website responds — you already have a powerful, precise performance analyzer built right into your browser. The Developer Tools that ship with Chrome, Edge, Firefox, and Safari can break down exactly where a page's loading time goes, from the first network request to the last byte. Here's how to test any website's response time from your browser, for free, and how to read what it tells you.

What "response time" actually means

"Response time" usually refers to how quickly a server starts replying to a request — closely related to Time To First Byte (TTFB). But your browser can show you much more than that single number: it reveals the full timeline of a page load, phase by phase, so you can see precisely which step is slow. If you want the benchmarks for what counts as a good server response, our guide on what a good TTFB is has the numbers; this guide focuses on measuring it yourself in the browser.

The tool you already have: DevTools Network tab

Every modern browser includes Developer Tools, and its Network tab records every request a page makes along with detailed timing for each. It's the same tool professional developers use to diagnose slow sites — and it's completely free and already installed.

How to test response time in your browser, step by step

  1. Open Developer Tools. Press F12, or right-click the page and choose Inspect.
  2. Go to the Network tab. This is where all requests and their timings appear.
  3. Reload the page with the Network tab open, so it records the full load from the start. (Tick the "Disable cache" box first for a true, uncached measurement.)
  4. Click the main document request — usually the first entry, named after the page or domain.
  5. Open the Timing tab for that request. This shows the complete breakdown of where the time went.

That's it — in a few seconds you have a precise, phase-by-phase measurement of the site's response.

Reading the timing breakdown

The Timing view splits the load into stages. Here's what each means:

  • Queued / Stalled — time spent waiting before the request could start (connection limits, proxy negotiation).
  • DNS Lookup — time to translate the domain into an IP address. Our guide on what a DNS lookup is explains this step; a slow one here points to DNS.
  • Initial connection — establishing the TCP connection to the server.
  • SSL / TLS — the secure handshake for HTTPS sites.
  • Request sent — the moment your request is fired off.
  • Waiting (TTFB) — the key one: the gap until the first byte of the response arrives. This is your server response time, and it's where slow backends show up.
  • Content Download — time to receive the actual response data.

At the bottom of the Network panel, you'll also see overall figures like Finish, DOMContentLoaded, and Load times — the totals for the whole page. Together, these tell you not just that a page is slow, but which stage is responsible.

Tips for an accurate measurement

  • Tick "Disable cache" so you measure a real load, not a cached copy.
  • Test a few times and look at the pattern — a single load can be an outlier.
  • Use an incognito/private window to rule out browser extensions skewing the result.
  • Try network throttling. The Network tab's throttling dropdown (Fast 3G, Slow 3G) lets you simulate slower connections to see how the site performs for mobile or distant users.

Browser test vs a server-side test

One important thing to understand: a browser test measures response time from your own location and connection. That's exactly what you want for seeing what you experience — but it's influenced by your distance from the server and your network. To measure the server's performance on its own, independent of your location, use a neutral server-side test like our free Site Speed (TTFB) tool, which checks the site from our infrastructure. Using both together gives you the full picture: how the server performs, and how it feels from where you are.

When the response time is slow

If your measurements show a high Waiting (TTFB) time, the server is the bottleneck — caching, a CDN, and better hosting are the usual fixes. If the slowness is in content download or lots of requests, the page itself may be too heavy — our guide on why a website loads slowly breaks down all the causes. And if a site won't respond at all rather than just slowly, run it through our live website down checker to see whether it's actually down.

The bottom line

Testing a website's response time from your browser takes seconds and costs nothing: open DevTools, go to the Network tab, reload the page, click the main request, and read the Timing breakdown. The Waiting (TTFB) figure is your server response time, while the surrounding phases (DNS, connection, TLS, download) show exactly where any delay lives. Pair a browser test with a neutral server-side speed test for the complete picture — and you'll know not just how fast a site responds, but precisely why.