What Is TTFB (Time to First Byte)?
A plain-English guide to how TTFB works, what a good score looks like, why it matters for SEO and user experience, and which UK hosts deliver the fastest server response times.
TTFB in One Sentence
TTFB (Time to First Byte) is how long it takes for your web server to send back the very first piece of data after someone requests your page — think of it as how quickly a waiter acknowledges your order, before the food actually arrives.
When you click a link, your browser sends a request to a server. TTFB measures the gap between that request leaving your browser and the first byte of the response arriving back. It includes DNS lookup, the network round trip, and server processing time. A fast TTFB means your server is responsive and well-located; a slow one means visitors are waiting before they see anything at all. Google considers TTFB a key performance metric — and it directly impacts your Core Web Vitals scores.
How Does TTFB Work?
Step 1
Your browser sends a request
When someone types your URL or clicks a link, their browser sends an HTTP request across the internet to your web server. This request first has to find your server via DNS lookup — like looking up a phone number before making a call.
Step 2
The request travels to your server
The request travels through cables, routers, and data centres to reach your hosting server. The physical distance between the visitor and the server adds milliseconds — a London visitor reaches a London server faster than one in Virginia.
Step 3
Your server processes the request
Your server receives the request and builds the response: running PHP or Node.js code, querying the database, applying caching, and assembling the HTML. This is typically the biggest chunk of TTFB — and the part your hosting provider most affects.
Step 4
The first byte arrives back
The server sends the response back across the internet. The moment your browser receives the very first byte of data, the TTFB clock stops. Everything after this — downloading CSS, images, JavaScript — is separate. TTFB measures only how quickly that first byte arrives.
What Is a Good TTFB?
Google classifies TTFB under 800ms as “good” for Core Web Vitals, but faster is always better. Here's how different ranges translate to real-world performance:
Fast enough for Google's "good" threshold. Typically achieved with CDNs, edge caching, or premium managed hosts with UK data centres.
Perfectly acceptable for most websites. Most quality shared and VPS hosts with UK servers fall in this range. Visitors won't notice any delay.
Noticeable to users and flagged by Google's Core Web Vitals as needing work. Common with overseas servers or heavily loaded shared hosting.
Visitors feel the delay. Search rankings may suffer. Usually caused by distant servers, no caching, or resource-starved shared hosting.
Unacceptable for any production site. Visitors will leave before the page even starts rendering. Immediate action needed — switch hosts or add a CDN.
🎯 UK benchmark: For a WordPress site hosted in the UK with caching enabled, aim for 150–300ms TTFB when tested from a UK location. Anything under 500ms is acceptable; above 800ms needs attention.
What Affects Your TTFB?
Server Hardware
High ImpactFaster CPUs, NVMe SSDs, and more RAM mean your server can process requests quicker. Budget shared hosting on older hardware will always be slower than a modern VPS or cloud instance.
Server Location
High ImpactPhysical distance matters. A UK visitor hitting a London server gets ~20ms network latency. The same visitor hitting a US server adds 80–120ms before processing even starts. Always choose a host with UK data centres.
Caching
High ImpactServer-side caching (page cache, object cache, opcode cache) can turn a 500ms database-heavy response into a 50ms cached response. This is often the single biggest TTFB improvement you can make.
CMS & Application Code
High ImpactA bloated WordPress install with 30 plugins makes more database queries and runs more PHP than a lean site. Poorly written themes and heavy page builders (Elementor, Divi) add significant server processing time.
CDN (Content Delivery Network)
High ImpactA CDN caches your pages on edge servers worldwide, so the response comes from a server near the visitor rather than your origin. Cloudflare's free tier alone can cut TTFB by 50%+ for cached pages.
PHP Version
Medium ImpactPHP 8.3 is significantly faster than PHP 7.4 for the same WordPress site. Some hosts still default to older PHP versions. Always use the latest stable version your CMS supports.
SSL/TLS Handshake
Medium ImpactHTTPS adds a TLS handshake before data transfer. Modern TLS 1.3 is fast (~0-RTT), but older TLS 1.2 setups add 50–100ms. Most good hosts now use TLS 1.3 by default.
DNS Resolution
Medium ImpactBefore the request even reaches your server, the browser must resolve your domain name to an IP address. Slow DNS providers can add 50–200ms. Premium DNS (Cloudflare, Route 53) resolves in under 20ms.
Why TTFB Matters (and What to Keep in Perspective)
Why a Fast TTFB Matters
Better Google Rankings
Google uses server response time as a ranking signal through Core Web Vitals. Sites with TTFB under 800ms score "good" on the Largest Contentful Paint metric, which directly influences search rankings.
Lower Bounce Rates
Visitors start seeing content faster, which keeps them engaged. Research by Google shows that as page load time goes from 1s to 3s, the probability of bounce increases by 32%.
Faster Page Rendering
TTFB is the starting gun for everything else. Until the first byte arrives, the browser can't begin parsing HTML, loading CSS, or rendering content. A slow TTFB delays the entire rendering pipeline.
Better Mobile Experience
Mobile connections add latency. A site with 200ms TTFB on desktop might show 400ms on 4G and 800ms on 3G. Starting from a low baseline means mobile users still get an acceptable experience.
Higher Conversion Rates
For e-commerce, every 100ms of improvement in load time can increase conversions by up to 1% (Deloitte study). TTFB is the foundational metric that affects all subsequent load stages.
Competitive Advantage
Most small business sites in the UK have TTFB of 500ms+. Achieving sub-200ms puts you ahead of the vast majority of competitors — visitors notice the speed difference even if they can't articulate it.
The Realities to Keep in Mind
TTFB Isn't Everything
A fast TTFB with slow JavaScript, unoptimised images, and render-blocking CSS still gives a poor user experience. TTFB is one piece of the performance puzzle — not the whole picture.
Cached vs Uncached Varies Wildly
The same site can show 80ms TTFB for cached pages and 1.2s for uncached ones. Single-test results are misleading — you need to measure both scenarios and test over time.
Location Skews Results
Testing from London against a London server will always show better TTFB than testing from Sydney. Always specify where you're measuring from, and test from locations your actual visitors use.
Diminishing Returns Below 100ms
Going from 800ms to 200ms is transformative. Going from 200ms to 50ms is barely perceptible to users. Don't spend money chasing ultra-low TTFB if your site is already in the "good" range.
Dynamic Sites Are Always Slower
A static HTML file will always have a faster TTFB than a WordPress page querying a database. Comparing TTFB across different site types isn't apples-to-apples.
CDN Masks Origin Problems
A CDN can deliver cached pages fast, but if your origin server is slow, any uncached request (admin pages, form submissions, first-time visitors) will still be sluggish. Fix the origin, then add a CDN.
How to Measure Your TTFB
Don't guess — measure. Use these free tools to check your actual TTFB from real locations:
| Tool | Price | Best For |
|---|---|---|
| Google PageSpeed Insights | Free | Best for checking Google's own view of your TTFB |
| WebPageTest | Free | Best for detailed waterfall analysis and multi-location testing |
| GTmetrix | Free (basic) | Best for beginner-friendly performance reports |
| Chrome DevTools | Free (built-in) | Best for real-time debugging from your own browser |
| KeyCDN Tools | Free | Best for quick multi-location TTFB comparison |
💡 Pro tip: Always test from a UK location (London or Manchester) if your audience is in the UK. Test at least 3 times and average the results — single tests can be misleading due to network variability.
6 Steps to Improve Your TTFB
Choose a host with UK servers
If your audience is in the UK, your server should be too. Switch to a host with London or UK data centres. This alone can cut 80–120ms off your TTFB.
Enable server-side caching
Use page caching (WP Super Cache, W3 Total Cache, or your host's built-in cache). This serves pre-built HTML instead of regenerating each page from the database on every request.
Use a CDN
Set up Cloudflare (free tier is excellent) or your host's built-in CDN. This caches your pages on edge servers closer to your visitors, dramatically reducing TTFB for repeat/global visitors.
Update PHP to the latest version
Log into your hosting control panel and switch to PHP 8.2 or 8.3. This is a free, instant performance boost — PHP 8.x is 2–3x faster than PHP 7.x for WordPress.
Reduce plugins and database queries
Audit your WordPress plugins — deactivate and delete anything unnecessary. Use Query Monitor to identify slow database queries. Fewer queries = faster server response.
Upgrade your hosting plan
If you've optimised everything and TTFB is still slow, your server is the bottleneck. Move from shared hosting to a VPS or managed cloud host for dedicated resources.
Who Needs to Care About TTFB?
TTFB is critical if you…
- E-commerce stores where slow TTFB directly reduces conversions and revenue
- Content-heavy sites competing for Google rankings in saturated niches
- SaaS applications where perceived speed affects user satisfaction and retention
- Sites targeting mobile users on slower connections where every millisecond counts
- International businesses serving visitors from multiple geographic regions
Standard TTFB is fine if you…
- Personal blogs with minimal traffic where speed has no business impact
- Internal tools or intranets accessed only by your own team on fast networks
- Staging or development sites not serving real users
- Sites already scoring under 300ms with no performance complaints
UK Hosting Provider TTFB Comparison
Average TTFB measured from London for a standard WordPress site with caching enabled:
| Provider | Avg TTFB |
|---|---|
| Kinsta | ~150ms |
| SiteGround | ~180ms |
| Cloudways | ~190ms |
| 20i | ~220ms |
| Krystal | ~240ms |
| IONOS | ~280ms |
| HostArmada | ~300ms |
| Fasthosts | ~350ms |
| A2 Hosting | ~380ms |
| Bluehost | ~450ms |
| DreamHost | ~480ms |
| HostPapa | ~520ms |
💡 Note: These figures represent averages from testing with caching enabled on a standard WordPress install. Your actual TTFB will vary based on your site's complexity, plugins, caching setup, and the specific plan you choose. Always verify with your own tests after signing up.
Related Guides
TTFB — Frequently Asked Questions
What does TTFB stand for?
What is a good TTFB for a website?
Does TTFB affect SEO?
How do I check my website's TTFB?
Why is my TTFB so slow?
Does shared hosting have worse TTFB than VPS?
Can a CDN improve my TTFB?
What is the difference between TTFB and page load time?
Is TTFB the same as server response time?
Does WordPress have worse TTFB than static sites?
Want the Fastest UK Hosting?
Our comparison tool tests and ranks 23 UK-accessible hosts on speed, uptime, support, and value — helping you find a provider that delivers the TTFB your site deserves.
Last updated April 2026 · Based on testing of 23 UK hosting providers · Written for beginners · Affiliate disclosure