Knowledge Mark G
Hire Me

Free SEO tool

Website Speed Test

Measure a page's server response time, page weight, compression, caching and render-blocking files - real timings, not estimates.

  • No sign-up
  • Instant results
  • Only the address is sent

Test a page

One real request from our server: DNS, connection, server response and download are measured, then the HTML is checked for what slows rendering.

Enter an address to measure how fast the server answers and what the page asks the browser to load.

What is measured - and what is not

The test makes one real request from our server and times each part of it: the DNS lookup, the TCP connection, the TLS handshake plus the server’s own processing, and the download. That gives the time to first byte (TTFB) - the point before which nothing on the page can appear. It then reads the HTML for what slows rendering: scripts and stylesheets that block it, images without dimensions, missing compression, oversized pages and third-party domains.

It does not report Core Web Vitals (LCP, INP, CLS). Those come from a real browser rendering the page, ideally real visitors on real phones, and any number computed from HTML alone would be a guess. The report links straight to Google’s PageSpeed Insights for those.

What good looks like

Google’s guidance is a TTFB of 0.8 seconds or less; over 1.8 seconds is poor. The fastest sites serve cached HTML from a CDN close to the visitor. If your TTFB is slow, the usual fixes are page caching (so the server does not rebuild the page on every request), a CDN, and a faster database query or host. Remember that one test from one location is a sample - run it a few times.

Quick wins

  • Turn on Brotli or gzip compression for HTML, CSS and JavaScript.
  • Add defer to scripts in the head.
  • Set width and height on every image, and lazy-load those below the fold.
  • Serve images as WebP or AVIF - the image compressor converts them.
  • Use HTTP/2 or HTTP/3 - usually a single setting on the host or CDN.

Checking on-page SEO as well? Run the SEO checker, and the security headers checker for the server side.

Questions people ask

What is TTFB?+

Time to first byte: how long from starting the request until the first byte of the response arrives. It includes DNS, connection, TLS and the server's processing time, and nothing on the page can render before it.

What is a good TTFB?+

0.8 seconds or less, by Google's guidance. Between 0.8 and 1.8 seconds needs improvement; over 1.8 seconds is poor.

Why is this different from PageSpeed Insights?+

PageSpeed Insights renders the page in a browser and reports Core Web Vitals. This test measures the server and the HTML directly, with real timings, and points out the causes - the two complement each other.

Where is the test run from?+

From our server, with one request and no cached connection, so it reflects a first visit. Results vary with distance to your server - a CDN reduces that.

Why are render-blocking scripts bad?+

A script in the head without async or defer stops the browser building the page until the script has downloaded and run. Adding defer lets the page render while it loads.

Is there a limit?+

About ten tests every five minutes from one address, so the tester cannot be used to flood a site.