How do I check my website speed?

Enter your page URL and run the test. Look at time to first byte first (under 800 ms is good), then HTML size, compression, redirects, and render-blocking scripts. Fix the items marked Poor, then re-test.

What is a good time to first byte (TTFB)?

Google considers a TTFB of 800 ms or less good and over 1.8 seconds poor. TTFB includes redirects, DNS, connection, TLS, and server processing time.

Is this the same as an internet speed test?

No. An internet speed test measures your own connection's download and upload bandwidth. A website speed test measures how quickly a specific site's server responds and how heavy the page is.

Why is my result different from PageSpeed Insights?

This test measures server response and HTML delivery from the SiteIndex server. PageSpeed Insights loads the page in an emulated browser and reports rendering metrics like LCP, INP, and CLS. Use both together.

Website & DomainReady to use

Website Speed Test

Test how fast a website loads: time to first byte, DNS, connection, TLS, download time, page size, compression, and render-blocking resources.

Documentation

Interactive workspace

No account required

Test website speed

Measures how fast a page's server responds and how heavy its HTML is: DNS, connection, TLS, time to first byte, download, redirects, compression, and render-blocking resources.

Enter a public URL to measure its server response time, page weight, and loading bottlenecks.

What is Website Speed Test?

Test how fast a website loads: time to first byte, DNS, connection, TLS, download time, page size, compression, and render-blocking resources.

How it works

SiteIndex requests the page from its server with a fresh connection and times each phase: DNS lookup, TCP connect, TLS handshake, server wait, and download. It follows redirects, decompresses the HTML, and checks compression, page weight, render-blocking scripts in the head, script and stylesheet counts, image dimensions, and third-party script hosts. The Advanced panel runs three uncached samples to show min, average, and max TTFB.

Where a network request is required, SiteIndex validates public HTTP/HTTPS targets before making the request.

Common uses

Check whether a slow site is caused by the server (high TTFB) or by page weight.
Verify that Brotli or gzip compression and caching are enabled after a deploy.
Find redirect hops and render-blocking scripts that delay the first paint.

Limitations

Results depend on the browser, network, input, and external service involved.
This tool is informational and does not replace specialist diagnostics or professional advice.

FAQ

How do I check my website speed?: Enter your page URL and run the test. Look at time to first byte first (under 800 ms is good), then HTML size, compression, redirects, and render-blocking scripts. Fix the items marked Poor, then re-test.
What is a good time to first byte (TTFB)?: Google considers a TTFB of 800 ms or less good and over 1.8 seconds poor. TTFB includes redirects, DNS, connection, TLS, and server processing time.
Is this the same as an internet speed test?: No. An internet speed test measures your own connection's download and upload bandwidth. A website speed test measures how quickly a specific site's server responds and how heavy the page is.
Why is my result different from PageSpeed Insights?: This test measures server response and HTML delivery from the SiteIndex server. PageSpeed Insights loads the page in an emulated browser and reports rendering metrics like LCP, INP, and CLS. Use both together.

Related tools