When a visitor types your web address and hits Enter, a timer starts. Their browser sends a request to your server, waits, and eventually receives the first byte of data back. That waiting period - from the moment the request goes out to the moment the first byte arrives - is called Time to First Byte, or TTFB.
Everything else your browser does to load the page - downloading images, parsing CSS, executing JavaScript - cannot begin until after that first byte arrives. This makes TTFB a foundational metric. A slow TTFB delays everything else, regardless of how well-optimized your other assets are.
What Are Good and Bad TTFB Targets?
Google and web performance researchers generally use these thresholds:
- Under 200ms - Excellent. Your server is responding quickly.
- 200ms to 600ms - Acceptable. There may be room for improvement.
- Over 600ms - This is a problem. Visitors will notice sluggishness, and your Core Web Vitals scores will suffer.
You can measure your TTFB using Google PageSpeed Insights, GTmetrix, or the Network tab in Chrome DevTools (look for "Waiting (TTFB)" in the timing breakdown for your main HTML document).
What Causes a Slow TTFB?
Several factors contribute to a high TTFB, and understanding the cause helps you choose the right fix.
Slow server hardware. Shared hosting accounts on overloaded servers are a common culprit. When dozens or hundreds of websites share the same physical server resources, peak-traffic periods can cause all of them to slow down simultaneously.
No server-side caching. On a dynamic site like WordPress, every page request triggers PHP execution and database queries to assemble the page. Without caching, this happens fresh for every visitor on every request - even if the page content has not changed in weeks. Generating a page dynamically takes far longer than serving a pre-built cached copy.
Slow database queries. Your database stores all your content, settings, and user data. If your database has grown large, has inefficient queries, or is running on slow storage, every page load that requires database lookups takes longer.
Geographic distance. Your server is located somewhere specific. If a visitor in Halifax is loading a page from a server in Los Angeles, the physical distance adds latency that cannot be fully optimized away. This is where content delivery networks (CDNs) help.
Heavy PHP processing. Poorly coded plugins, themes with excessive functionality, or PHP running without optimization all extend the time it takes to generate a response.
How to Improve Your TTFB
Install a Caching Plugin
For WordPress sites, a caching plugin is the single most effective TTFB improvement. Plugins like WP Rocket, W3 Total Cache, or the free LiteSpeed Cache generate static HTML versions of your pages and serve those directly, bypassing PHP and database queries entirely. This can cut TTFB from 800ms to under 100ms on many sites.
Enable PHP OPcache
PHP OPcache stores compiled versions of your PHP scripts in memory so they do not need to be re-compiled on every request. Most quality hosting providers enable OPcache by default. In cPanel, check under Software > Select PHP Version and confirm the OPcache extension is active.
Choose Quality Hosting
Your hosting environment is the foundation of your TTFB. Overcrowded shared servers produce high TTFBs regardless of how well your site is optimized. Quality providers like dotCanada maintain their servers at appropriate capacity levels, use fast SSD storage, and run modern server software - all of which directly reduce your TTFB.
If you have exhausted optimization options on your current host and still see high TTFBs, the problem may be the hosting environment itself. Moving to a better host is sometimes the most effective fix.
Use a CDN
A Content Delivery Network like Cloudflare caches your pages at edge locations around the world. When a visitor in Vancouver requests your page, it is served from a Cloudflare server in Vancouver rather than travelling to wherever your origin server is located. This dramatically reduces the geographic latency component of TTFB.
Optimize Your Database
WordPress sites accumulate database bloat over time - post revisions, transients, spam comments, orphaned plugin data. Plugins like WP-Optimize or WP-Sweep can clean this up and improve query performance. Running these optimizations regularly keeps your database lean.
Putting It Together
TTFB improvement typically follows this sequence: add caching first (biggest impact), confirm OPcache is enabled, add a CDN for geographic distribution, and then evaluate whether your hosting environment itself is the limiting factor. Working through this sequence methodically will produce meaningful, measurable improvements in your server response time and your overall page performance scores.
