# Website Speed Test

> Check your response time and time to first byte in seconds.

The website speed checker measures how long a site takes to respond to a real request from a Postman server, reports the total response time and an estimated time to first byte, and grades the result as Fast or Slow.

Also: website speed checker, website speed test, response time checker, time to first byte, ttfb checker, page load time test, how fast is my website, check website response time.

## What it does

Enter a URL and Postman issues one request from a server and times the round trip. It reports total response time and an estimated time to first byte. Because the measurement comes from a Postman server rather than your own machine, it is a consistent synthetic figure — useful for comparisons and trends, not the exact latency a visitor on a particular network would see. One check is a single sample.

## When to use it

- A page feels slow and you want a number before you start investigating.
- You changed hosting, a CDN or a caching layer and want a quick before-and-after.
- You want to compare your response time against a competitor on an equal footing.
- You need to know whether slowness is the server responding late or the page rendering late.

## What you give it

| Input | Meaning |
| --- | --- |
| URL | Any public http or https address. The scheme is added automatically if you leave it off. |

## What you get back

| Output | Meaning |
| --- | --- |
| Response time | Total milliseconds for the round trip, measured from a Postman server. |
| Time to first byte | Milliseconds until the first byte arrives, estimated from the total response time. |
| Verdict | Fast below 500ms, Slow at or above it. |

## How it works

- A single request is issued from a Postman server and the round trip is timed.
- The Fast or Slow verdict is a threshold at 500ms of total response time — below is Fast, at or above is Slow.
- Time to first byte is estimated at 40% of total response time and labelled as an estimate.
- The measurement is taken from a Postman server region, so it is consistent between runs rather than reflecting your own network.

## Key terms

- **Time to first byte (TTFB)** — how long from making a request until the first byte of the response arrives. It isolates server think-time and network latency from the time spent downloading and rendering the page.
- **Response time** — the full round trip to receive the response. Always at least as large as time to first byte.
- **Estimated TTFB** — this check reports the total round trip and estimates time to first byte from it (40%) rather than measuring it separately, so treat the TTFB figure as an indication rather than an exact reading.
- **Single sample** — one measurement at one moment from one location. Cold caches, a noisy network or a busy origin all move it. Trends need repeated measurement on a schedule.

## Questions

### This tool gives you

This free website speed test checks response time and estimated TTFB for any URL, with a fast-or-slow verdict graded against Google's thresholds. No signup, no benchmark history.

### Postman Monitors gives you

Postman Monitors turns that single check into response-time trends over time, so you can tie a regression to the deploy that caused it, continuous scheduled monitoring with alerts when response time crosses a threshold you set, multi-region measurement from Postman's global regions, and a Postman CLI check that fails your build on a regression.

### Why did my score change when I didn't touch anything?

Response time and TTFB fluctuate with network conditions, server load, and CDN caching — a small swing between checks is normal, not a regression.

### Is my TTFB or speed score actually good or bad?

The verdict is graded against Google's published thresholds, so "fast" or "slow" reflects the same bar Core Web Vitals uses.

### What is TTFB and why does it matter for site speed?

Time to first byte measures how long the server takes to start responding — it isolates backend and network delay from rendering time.

### Can I track my website's performance over time, not just check it once?

Yes — Postman Monitors runs this same check on a schedule and keeps a history of response time so you can catch regressions early.

### Can I fail my CI build if my site's response time regresses?

The Postman CLI can run this check in your pipeline and fail the build when response time crosses a threshold you set.

### Is there a quick website health check I can run before a launch?

This speed test plus the uptime and API health checkers cover a fast pre-launch pass without any setup.

### Can I check API response time too, not just websites?

Yes — this tool measures response time and TTFB for any URL, including an API endpoint, not just a webpage. This is actually where Postman's monitoring goes further: Postman Monitors can assert on the real response body of an API — not just confirm it responded fast — across every endpoint you care about.


## Privacy

The URL you enter is sent to Postman so the request can be made from a server. It is not stored, and no account is needed.

## Links

- [Use the tool](https://www.postman.com/tools/website-speed-test) — the interactive version of this page.
- [Postman Tools](https://www.postman.com/tools) — every free tool in this set.
- [Monitors docs](https://learning.postman.com/docs/monitoring-your-api/intro-monitors/) — Postman documentation.