⭐ Beginner — No coding experience needed
Slow Server Response Time TTFB? How to Fix It — Beginner's Guide
TTFB stands for Time to First Byte. It is the time between a visitor requesting your page and their browser receiving the very first piece of data back from your server. If this takes too long, your page loads slowly, visitors leave, and Google ranks you lower. This guide explains exactly what TTFB is, how to check yours, and the practical steps you can take to improve it.
What you will learn in this guide
- What TTFB is and why it matters for Google rankings and page speed
- What a good TTFB looks like and what counts as too slow
- How to measure your current TTFB using free tools
- The most common causes of a slow TTFB and how to fix each one
- How to enable caching on your server to speed up response times
- How to check whether your hosting plan is the root cause
- How to verify your TTFB has improved after making changes
Before You Start — Tools You Need
New to editing website files? You need Notepad++ and FileZilla set up before following this tutorial.
Open Setup Guide →
1 What is TTFB?
TTFB stands for Time to First Byte. Let us break that down so it makes complete sense — no technical knowledge needed.
What actually happens when someone visits your page
When someone types your website address into a browser and presses Enter, here is what happens:
- The browser sends a request to your web server asking for the page
- Your server receives the request and starts preparing the page
- Your server sends the first piece of data — the first byte — back to the browser
- The browser receives that first byte and starts building the page
TTFB is the time between step 1 and step 4. It is measured in milliseconds. A millisecond is one thousandth of a second.
Why does TTFB matter?
Nothing can load on the page until the browser receives that first byte. The page title, the text, the images, the navigation — none of it can start loading until the server responds. If TTFB is slow, everything on the page is delayed. Every millisecond of TTFB delay adds to the total time the visitor waits before seeing anything.
Google measures TTFB as part of its Core Web Vitals assessment. A slow TTFB contributes to a poor Largest Contentful Paint (LCP) score — which directly affects your Google rankings.
What counts as a good TTFB?
| TTFB | Rating | What it means |
|---|---|---|
| Under 200ms | 🟢 Excellent | Your server is fast — no action needed |
| 200ms to 500ms | 🟡 Needs improvement | Acceptable but worth optimising |
| Over 500ms | 🔴 Poor | Your server is too slow — this needs fixing |
What causes a slow TTFB?
TTFB is almost always a server-side issue — it has nothing to do with your images, your CSS or your JavaScript. The most common causes are:
| Cause | How common | What section covers this |
|---|---|---|
| No caching — server builds the page fresh every time someone visits | Very common | Section 4 |
| Cheap or overloaded shared hosting | Very common | Section 5 |
| Server located far from your visitors | Common | Section 6 |
| Too many plugins or slow database queries (WordPress) | Common | Section 7 |
| No CDN for static files | Moderate | Section 8 |
2 Measure your current TTFB
Before you try to fix anything, measure exactly what your TTFB currently is. You need a number — not a guess.
Tool 1 — Google PageSpeed Insights (recommended)
- 1 Go to Google PageSpeed Insights Open a new browser tab and go to https://pagespeed.web.dev. This is Google's own free page speed testing tool.
-
2
Enter your page address
Type the full address of your page — for example
https://yourdomain.com— and click Analyse. - 3 Wait for the results The test takes about 30 seconds. When it finishes, scroll down and look for Server response time (TTFB) in the diagnostics section. It will show you a time in milliseconds and whether it passes or fails Google's threshold.
Tool 2 — AIPageSEO audit
- 1 Go to the AIPageSEO audit tool Go to https://aipageseo.com/seo-audit-platform.html, enter your page address and run the audit. Scroll to the Performance section to see your TTFB result.
Tool 3 — GTmetrix
- 1 Go to GTmetrix Go to https://gtmetrix.com. Enter your page address and click Test your site. When the test finishes, click the Waterfall tab. The very first bar in the waterfall chart shows your TTFB — the green section of that first bar is waiting time, which is your server response time.
💡 Run the test three times and take the average.
TTFB can vary from one test to the next depending on server load at that moment. Run the test three times and use the middle result as your baseline. Write this number down — you will compare against it after making improvements.
3 Work out what is causing your slow TTFB
TTFB has several possible causes. Before you start making changes, work out which one applies to your situation. Fixing the wrong thing wastes time.
- 1 Is your TTFB slow on every page or just some pages? Test three or four different pages on your site — your homepage, a product page, a blog post. If all of them are slow, the problem is your server or hosting. If only specific pages are slow, the problem is likely something specific to those pages — such as a heavy database query or a slow plugin.
- 2 Do you use WordPress or another CMS? WordPress builds your pages dynamically — every time someone visits, WordPress queries the database, runs PHP code, and builds the page from scratch. This takes time. Without caching, every visitor triggers this process. With caching, WordPress saves a ready-made version of each page and serves that instantly instead. If you use WordPress and have no caching plugin installed, this is almost certainly the main cause of your slow TTFB.
- 3 What country are your visitors in compared to your server? Every request to your server travels physically through internet cables. The further the visitor is from your server, the longer it takes for the request to arrive and the response to come back. If your server is in the UK but most of your visitors are in Australia, TTFB will always be higher for those visitors regardless of other optimisations.
- 4 What type of hosting do you have? Shared hosting means your website shares a server with hundreds or thousands of other websites. When those other sites get busy, your server slows down — and your TTFB goes up. VPS (Virtual Private Server) and dedicated server hosting give you guaranteed resources so other websites cannot affect your speed.
4 Fix 1 — Enable server-side caching
Caching is the single most effective thing you can do to reduce TTFB. It saves a ready-made copy of your page on the server so it can be delivered instantly instead of being built fresh for every visitor.
If you use WordPress
-
1
Log in to your WordPress dashboard
Go to
https://yourdomain.com/wp-adminand log in with your WordPress username and password. - 2 Go to Plugins and click Add New In the left menu click Plugins, then click Add New Plugin at the top of the page.
- 3 Search for WP Super Cache or W3 Total Cache In the search box type WP Super Cache. When it appears click Install Now, then click Activate. This plugin creates a static cached version of each page and serves it instead of rebuilding the page for every visitor.
- 4 Enable caching in the plugin settings Go to Settings → WP Super Cache. Make sure Caching On is selected and click Update Status. That is all you need to do for a basic setup.
- 5 Re-test your TTFB Go back to Google PageSpeed Insights and re-test your page. Your TTFB should have dropped significantly — often by 50% or more on a standard shared hosting plan.
If you use Plesk hosting (non-WordPress)
-
1
Log in to your Plesk control panel
Go to
https://yourdomain.com:8443and log in. - 2 Find the caching settings Click on your domain name, then look for Apache & Nginx Settings or Speed Kit or Caching in the menu. The exact location depends on your Plesk version. Ask your hosting provider if you cannot find it — they will be able to enable it for you.
If you use cPanel hosting (non-WordPress)
- 1 Contact your hosting provider Most cPanel shared hosting plans do not expose caching controls directly. Contact your hosting provider's support and ask: "Can you enable server-side caching or Varnish cache for my account?" Many hosts will do this for free on request.
5 Fix 2 — Upgrade your hosting plan
If caching is already enabled and your TTFB is still over 500ms, your hosting plan itself may be the problem. This section explains what to look for and what to ask your host.
Signs your hosting is the problem
- TTFB is consistently over 500ms even with caching enabled
- TTFB varies wildly between tests — sometimes fast, sometimes very slow
- Your hosting plan is the cheapest tier available from your provider
- You are on shared hosting with unlimited websites at a very low monthly price
What to ask your hosting provider
- 1 Contact your hosting provider's support Reach out by live chat or support ticket and say: "My website has a TTFB of [your number]ms. Can you tell me what is causing this and what I can do to improve it on my current plan?"
- 2 Ask about upgrading to a VPS A VPS — Virtual Private Server — gives your website dedicated resources that are not shared with other websites. This almost always results in dramatically lower TTFB. Ask your host what their VPS plans cost and what TTFB improvement you can expect.
- 3 Ask about server location Ask your host which country your server is located in. If most of your visitors are in the UK but your server is in the US, ask about migrating to a UK-based server. Most hosts can do this migration for you.
6 Fix 3 — Use a Content Delivery Network (CDN)
A CDN is a network of servers located in many different countries. When you use a CDN, copies of your pages and files are stored on servers close to your visitors — so instead of a request travelling from Australia all the way to a UK server, it is served from a server in Australia instead.
What does a CDN do to TTFB?
A CDN does not reduce the time your server takes to generate a page — but it dramatically reduces the physical distance the request and response have to travel. For international audiences this can reduce TTFB by hundreds of milliseconds.
Free CDN option — Cloudflare
- 1 Go to Cloudflare Go to https://www.cloudflare.com and create a free account. Cloudflare's free plan includes CDN, basic caching and DDoS protection — all of which help reduce TTFB.
- 2 Add your website Click Add a site, enter your domain name and follow the setup wizard. Cloudflare will scan your DNS records and then ask you to update your domain's nameservers to point to Cloudflare. Your domain registrar's support team can help you do this if you are not sure how.
- 3 Re-test TTFB after Cloudflare is active Wait 24 hours after changing nameservers for Cloudflare to fully activate, then re-test your TTFB using Google PageSpeed Insights. Improvement is typically noticeable, especially for visitors who are geographically distant from your server.
7 Fix 4 — Identify and remove slow WordPress plugins
If you use WordPress, some plugins execute database queries or external API calls on every page load — even when caching is on. These can significantly increase your server response time.
- 1 Note your current TTFB Before you start, run a TTFB test and write down the result. You need a baseline to compare against as you deactivate plugins.
-
2
Go to Plugins in your WordPress dashboard
Log in to
yourdomain.com/wp-adminand click Plugins in the left menu. - 3 Deactivate all non-essential plugins temporarily Tick the box at the top to select all plugins. From the Bulk Actions dropdown choose Deactivate and click Apply. This turns off all plugins at once — your site will still be visible but some features may stop working temporarily.
- 4 Re-test TTFB immediately Run a TTFB test right now with all plugins off. If TTFB has dropped significantly, one or more of your plugins was causing the slow response time.
- 5 Reactivate plugins one at a time Go back to your plugins list. Activate one plugin. Re-test TTFB. If TTFB stays low, that plugin is not the problem — move on to the next. If TTFB jumps up after activating a specific plugin, that plugin is the culprit. Search for an alternative plugin that does the same job more efficiently, or contact the plugin developer.
8 Verify your improvement and re-run the audit
- 1 Re-run Google PageSpeed Insights Go to https://pagespeed.web.dev and test your page again. Compare the new TTFB to the number you wrote down at the start. You should see a measurable improvement.
- 2 Re-run the AIPageSEO audit Go to https://aipageseo.com/seo-audit-platform.html and run the audit on your page again. The TTFB result in the Performance section should now show green.
- 3 Check your LCP score too TTFB is the starting point for LCP — Largest Contentful Paint. Now that TTFB is improved, check your LCP score in Google PageSpeed Insights. A lower TTFB often means a lower LCP score too.
9 Common mistakes to avoid
- ⚠ Confusing TTFB with total page load time TTFB is only the server response time — the time before the browser receives the first byte. Total page load time includes TTFB plus the time to download all the page's images, CSS and JavaScript. Improving TTFB will not fix a slow page load time caused by large images — those are separate problems.
- ⚠ Only testing once TTFB varies between tests because it depends on server load at that exact moment. Always run three tests and use the middle result. Testing once gives you an unreliable snapshot.
- ⚠ Expecting instant ranking improvements Improving TTFB improves your Core Web Vitals scores, which Google uses as a ranking signal. But ranking changes take time — Google needs to re-crawl your pages and reassess them. Give it a few weeks after improving TTFB before expecting to see ranking changes.
- ⚠ Installing too many caching plugins Only install one caching plugin. Having two caching plugins active at the same time causes conflicts that can break your website or actually make performance worse. Choose one — WP Super Cache or W3 Total Cache — and stick with it.