TTFB checker: server response time
Measure time to first byte: how long a server takes to start sending a page. The check also reports HTML size, compression, caching headers, redirects and the number of files the page asks for, without needing a Google key.
How to use the Page Speed Checker
- 1Enter the page address and choose Mobile or Desktop.
- 2Read the Core Web Vitals from real Chrome users (when Google has enough visits) and whether the page passes.
- 3Check the Lighthouse lab score and metrics, then work through the top things to fix, biggest saving first.
- 4Look at the basic check for server response time, page size, compression and caching headers.
Frequently asked questions
What is a good TTFB?
Under about 800 ms for real users is good by Google's guide; for a server check like this one, under 600 ms is a healthy target. Above 1.5 s usually means slow hosting or no page caching.
How do I reduce time to first byte?
Cache whole pages (a caching plugin or a CDN), upgrade slow shared hosting, cut slow database queries and remove redirects in front of the page.
Why does TTFB change between tests?
Caches warm up, servers get busy and our test runs from the Cloudflare data centre nearest you. Run it a few times and look at the typical value.
Related free tools
All tools- Page Speed CheckerCore Web Vitals from real Chrome users, a lab test and fixes.
- Core Web Vitals checkerCore Web Vitals checker
- Image SEO CheckerAlt text, sizes and formats of a page's images.
- Website Technology CheckerThe CMS, analytics and tools a site is built with.
- Image CompressorShrink JPG, PNG and WebP files, or hit an exact size like 100 KB.
Then schedule it with Join Postly
Plan, publish and track your posts on every network from one calendar. Free plan, no credit card.