Response Time Test

Measure a URL's server response time and redirect overhead.

Response Time Test reports how long, in milliseconds (ms), a server takes to answer a GET request to the URL you enter. Our server makes a real HTTP request to the address and measures the time to the first response, so you can see at a glance whether the site responds snappily.

The result is graded as fast under 300ms, average from 300 to 800ms, and slow above 800ms. The status code and redirect count shown alongside help you tell whether a slow response comes from server processing delay or from unnecessary redirects.

URLe.g. https://example.com (include the protocol)

What TTFB and server response time are

TTFB (Time To First Byte) is the time between sending a request and receiving the first byte of the response. It includes DNS lookup, TCP/TLS connection, and the time the server spends processing the request and producing a response. A high TTFB makes users wait before anything renders, affecting both perceived speed and search rankings.

Server processing: dynamic page generation, database queries, slow external API calls
Connection cost: DNS resolution, the TLS handshake, and round-trip time (RTT) to a distant data center
Redirects: each extra 301/302 adds another round trip

How to read the measurement

This tool reports a single measurement for one GET request. Even for the same site, results can fluctuate with server location, cache hits, and momentary traffic, so measure a few times to see the overall trend. If responses are slow, start by checking CDN caching, removing unnecessary redirects, and optimizing server-side rendering. To cut transfer size itself, check whether gzip/brotli is on with the compression check, and whether the page is heavy with the page weight analyzer.

Frequently asked questions

I get a different number every time.

A single measurement is affected by network conditions, server caches, and momentary load. For an accurate trend, measure a few times and look at the average. Results for the same URL are cached for 30 seconds.

Where is the measurement taken from?

From the data center where the OneWebDesk server runs. The time depends on the physical distance between our location and the target server, so it may differ from what your own users experience.

What does the redirect count mean?

It is the number of 301/302 redirects followed before reaching the final URL. More redirects mean more round trips and a slower response, so unnecessary redirects are best removed.

Is my input sent anywhere?

The server only requests the URL you enter, for the measurement. It runs safety checks to block requests to internal networks or disallowed hosts, and it does not store data beyond the measurement result.

Related tools

Image Format Recommender

Recommend the right image format (WebP, AVIF, PNG, JPEG) for your use case.

Cache-Control Builder

Build a Cache-Control header for your resource type.

Resource Hints Generator

Generate preload, preconnect and dns-prefetch link tags.

Compression (gzip/brotli) Check

Check whether the server applies gzip/brotli compression and the savings.

Page Weight Analyzer

Analyze a page's HTML size and the count/type of referenced resources.

CIDR Calculator

Calculate IP range, subnet mask and host count from CIDR notation.