Skip to content

PerformanceFree tool

TTFB Checker

Measure how long one page’s server takes to start sending its HTML.

  • One page
  • mobile
  • run by Google Lighthouse
  • no account

Result

Resultnothing checked yet

Paste a page address above

Google PageSpeed Insights loads the page once in Lighthouse, on an emulated phone with a throttled network.

  • Server response time for the page’s HTML
  • Lighthouse’s 600 ms check
  • The top fixes from Lighthouse

What it checks

What this check covers, and what it doesn’t.

A quick look at one page. For a whole site, see below.

It checks

  • Server response time for the page’s HTMLYes
  • Lighthouse’s 600 ms checkYes
  • The top fixes from LighthouseYes

It doesn’t

  • Tests from several locationsNo
  • TTFB for real visitorsNo
  • Images, scripts and other filesNo
  • DNS and connection time on their ownNo
Why it matters

Nothing starts until the server answers.

CSS, images and scripts all wait for the first byte of the HTML. A slow server adds the same delay to every page.

How to use it

  1. Paste a page address

    Any public page. No account needed.

  2. Select Check TTFB

    Google PageSpeed Insights loads the page once in Lighthouse, on an emulated phone with a throttled network.

  3. Find the slow part

    Caching pages on the server or a CDN usually helps most. On CMS sites, slow database queries and plugins are common causes.

Every plan

Test your key pages on a schedule

Performance Boost runs Lighthouse on mobile and desktop, shows Core Web Vitals field data and alerts you when a page drops below its own average.

  • This free toolOne page · mobile, on demand
  • Performance BoostUp to 10 pages per monitor, on a schedule
FAQ

TTFB Checker, answered.

Anything else? Talk to us.

Is the TTFB Checker free?

Yes. You can run it without an account. The result shows the first 2 fixes; enter your email to see up to 8.

What is a good TTFB?

Lighthouse flags a server response time over 600 ms. For real visitors, Google’s guidance calls 0.8 seconds or less good.

Why is it different from my own test?

The test runs on Google’s servers, at a different distance from your server than you are. Caches may also be warm or cold.

Why is the result different from my last test?

Each run is one Lighthouse test on Google’s servers, on an emulated phone with a throttled network. Results move a little between runs. Test again before you act on a small change.

How often can I run it?

Up to 5 tests an hour. All the speed tools share that limit. When you reach the limit, the page tells you how long to wait.