Server Response Time Tester
Test how fast a server responds and measure real TTFB from our edge network.
Test any website or enter a specific hosting provider domain
What Is Server Response Time?
Server response time, often called Time to First Byte (TTFB), is the time it takes for your web server to send the first byte of data back to a visitor’s browser after receiving a request. It measures how quickly your server starts delivering your page, before any images, stylesheets, or scripts begin loading.
A fast TTFB means your server is processing requests efficiently. A slow TTFB means something is holding it up, whether that is an overloaded server, slow database queries, unoptimised PHP code, a missing caching layer, or simply a server that is too far away from your visitor.
Google includes TTFB as part of its performance metrics. While it is not a direct ranking factor on its own, it affects Largest Contentful Paint (LCP) and overall page speed, both of which Google does measure as part of Core Web Vitals.
How to Use This Tool
Enter any URL and click Test. The tool sends a request to the URL and measures the time it takes for the server to begin responding. You will see the total response time in milliseconds, the HTTP status code, and response headers.
A good TTFB for a shared hosting server is under 600 milliseconds. For a VPS or dedicated server, aim for under 200 milliseconds. Anything over one second suggests a problem worth investigating.
Keep in mind that the result reflects the response time from our testing server’s location, not from your visitor’s location. If your server is in Frankfurt and the test runs from a different region, network distance will add latency. For a more complete picture, test from multiple locations using tools like GTmetrix or KeyCDN’s performance test alongside this tool.
Common Causes of Slow Response Times
No server side caching. Every time a visitor loads a WordPress page without caching, the server has to execute PHP, query the database, assemble the HTML, and send it back. This can take hundreds of milliseconds per request. A caching plugin (LiteSpeed Cache, WP Rocket, or W3 Total Cache) stores a pre-built version of each page and serves it instantly.
Overcrowded shared hosting. If you are on a cheap shared hosting plan, your site shares CPU, RAM, and disk I/O with hundreds or thousands of other sites. When neighbours use heavy resources, your response time suffers. This is the most common cause of inconsistent TTFB that is fast one hour and slow the next.
Slow database queries. As your WordPress site grows, plugins and themes can add slow or redundant database queries. Query monitor plugins can identify which queries are taking the longest. Cleaning up post revisions, transient data, and unused plugin tables also helps.
No CDN. Without a content delivery network, every request travels all the way back to your origin server regardless of where the visitor is located. A CDN caches your content at edge locations worldwide, reducing TTFB significantly for international visitors. Read our CDN guide for more detail.
PHP version. Running an older PHP version (7.x or below) is measurably slower than PHP 8.x. Each major PHP release brings meaningful performance improvements. Check your hosting control panel and upgrade to the latest supported version.
Too many plugins. Each active WordPress plugin adds code that executes on every page load. Some plugins are well optimised and add negligible overhead. Others run heavy operations on every request. If your TTFB is slow, deactivating plugins one by one while testing response time can identify the culprit.
What to Do With Your Results
If your TTFB is consistently under 200 milliseconds, your server is performing well. Focus on frontend optimisation instead, compressing images, minifying CSS and JavaScript, and lazy loading below the fold content.
If your TTFB is between 200 and 600 milliseconds, there is room to improve. Start with server side caching and a CDN. These two changes alone often cut TTFB in half.
If your TTFB is over one second, you likely have a hosting problem. Either your server is overcrowded, under-resourced, or misconfigured. Consider upgrading to a better hosting plan or switching providers. See our hosting comparison to find providers with strong performance records.