Enter a URL to see how long your server takes to answer one request and where exactly the time goes. A slow time to first byte usually means the server spends too long generating the page: no cache, slow database queries or an overloaded host.
Free and without registration. The check is made from our server, so the timings include the network distance to it.
Google recommends a time to first byte of 800 ms or less. Under 200 ms is excellent and usually means the page is served from a cache. Note that our measurement includes the network distance between our server and yours.
The first request often warms up caches on your side: PHP opcode cache, page cache, database buffers or a CDN edge. If the result changes a lot between checks, your cache is probably not configured for this page.
Not necessarily. A single request shows the best case. To see how the response time changes when many visitors come at once, run a load test - it is free in Siteload after registration.
One request shows the best case. Run a free load test with up to 1,000 concurrent connections, compare the results after every change and get an email when your site goes down.
Run a free load test