The timing breakdown
| Phase | What it measures | How to improve |
|---|---|---|
| DNS lookup | Finding the server IP | Use a fast DNS provider |
| TCP connect | Distance to the server | Use a CDN close to visitors |
| TLS handshake | Setting up HTTPS | Enable TLS 1.3 and session resumption |
| Server processing | Building the page | Page caching, faster hosting, fewer database queries |
| Download | Transferring the HTML | Compression and smaller HTML |
What is a good TTFB?
Under 200 ms is excellent, under 500 ms is good and Google's Core Web Vitals guidance treats up to 800 ms as acceptable. The checker runs three requests and reports the median to smooth out network noise.
Times are measured from our server in Europe; visitors far away will see longer connect times. For real-user and full page-load metrics use the Website Speed Test.
Frequently asked questions
Why is my TTFB slow?
Usually slow server-side processing: no page caching, heavy plugins or a slow database. A distant server or slow DNS also adds time.
Does TTFB affect SEO?
It affects Largest Contentful Paint and overall user experience, which are part of Google's page experience signals.
Why do results vary between runs?
Network conditions and server load change constantly, so the tool uses the median of three runs.