Speed & performance · Guide
How to Reduce TTFB in WordPress
Short answer
To reduce TTFB in WordPress, serve cached pages instead of building each page from scratch, put a CDN in front of your site, and remove plugins and theme features that slow down PHP and database work. Measure TTFB in PageSpeed Insights first, then fix the slowest part of the request. A good result is 0.8 seconds or less at the 75th percentile of real visits, as of November 2026.
Key takeaways
- TTFB measures the time from the start of a navigation until the first byte of the response arrives.
- A good TTFB is 0.8 seconds or less at the 75th percentile of real visits; over 1.8 seconds is poor.
- PageSpeed Insights reports TTFB from real Chrome users over the previous 28 days.
- Full-page caching is usually the biggest single cut to WordPress TTFB, because the server serves a stored page.
- Lighthouse fails its server response audit when the browser waits more than 600 ms for the main document.
- TTFB is not a Core Web Vital, but it adds time to First Contentful Paint and Largest Contentful Paint.
What is TTFB in WordPress?
TTFB, or Time to First Byte, is the time from when a visitor starts to load a page until the first byte of the page response arrives.
TTFB is the sum of 5 parts: redirect time, service worker startup, DNS lookup, connection and TLS setup, and the request itself. web.dev's TTFB page lists each part and notes that cutting connection setup time and backend time lowers the total.
On WordPress, the request part is often the largest. Each uncached visit makes PHP run and the database answer queries before any HTML can leave the server.
| Part of TTFB | What happens | What slows it down |
|---|---|---|
| Redirect | The browser follows one URL to another | Long redirect chains |
| Service worker startup | The browser starts the service worker, if one is installed | A slow worker script |
| DNS lookup | The browser finds the server address | Slow DNS |
| Connection and TLS | The browser opens a secure link to the server | Extra round trips |
| Request | The server builds the page and sends the first byte | No cache, slow plugins, weak hosting |
What is a good TTFB for a WordPress site?
A good TTFB is 0.8 seconds or less at the 75th percentile of real visits, and a TTFB over 1.8 seconds is poor.
Google's web.dev guide gives those numbers as a rough guide, with values between 0.8 and 1.8 seconds needing improvement. The 75th percentile means 3 in 4 real visits were at least that fast. These numbers are current as of November 2026.
Lighthouse uses a stricter lab check. Its server response audit fails when the browser waits more than 600 ms for the main document, according to Chrome for Developers.
| Rating | TTFB at the 75th percentile | What it means |
|---|---|---|
| Good | 0.8 seconds or less | Most visitors get a fast start |
| Needs improvement | Over 0.8 up to 1.8 seconds | The start is slow enough to notice |
| Poor | Over 1.8 seconds | The start delays everything after it |
A cached page served from a nearby edge server answers far faster than an uncached page built on the origin, while a slow uncached page can pass 1.8 seconds on mobile networks. Judge your own number against the field data for your own visitors, not against a single lab run.
For the wider picture, see how fast a WordPress site should load.
How do you measure TTFB on your WordPress site?
Measure TTFB in PageSpeed Insights first, because it shows what your real visitors experienced over the last 28 days.
You need WordPress admin access, a cache plugin or host caching, and a PageSpeed Insights test, which is free and needs no account.
- Open PageSpeed Insights, enter your page URL, and run the mobile test.
- Read the “Discover what your real users are experiencing” section at the top.
- Find the TTFB value and its rating. If your page has too little data, the report falls back to origin-level data for the whole site.
- Scroll to the lab section and read the “Reduce server response times” audit for the lab view.
Google's PageSpeed Insights docs say TTFB is an experimental field metric there, reported at the 75th percentile over the previous 28 days. Field data updates daily, so a fix takes time to show up in full.
Field data is your main source, because it includes redirect time that lab tools often miss. web.dev's optimization guide makes that point and points to PageSpeed Insights for both field and lab data.
For a single load, use the Network panel in Chrome DevTools. Reload the page, click the main document request, and read the timing breakdown to see how long the browser waited for the first byte.
For the mobile test, Lighthouse simulates a mid-tier device on a mobile network, so lab numbers reflect a modest phone rather than a fast desktop. Google's PageSpeed Insights docs describe that setup.
Lab numbers change from run to run, so run the test 3 times and note the middle value. A single fast lab result does not prove your visitors see the same speed.
Why is TTFB high on WordPress sites?
TTFB is high on WordPress when the server has to build the page from scratch on every visit and the visitor is far from the server.
- No page cache, so PHP and the database run on every visit.
- Too many plugins, or one slow plugin, adding database queries.
- A heavy theme that runs extra code before the page can start.
- A distant or crowded shared server with little CPU and memory.
- Long redirect chains, such as http to https to www.
- Slow DNS or a TLS setup that adds extra round trips.
The WordPress optimization handbook lists hosting, WordPress setup, software versions, images, plugins, and theme weight as the main factors that affect performance. It also warns that without caching, requests stack up and can crash the web or database server under load.
Start with the request part, because that is the part WordPress controls. Check the cache first, then plugins, then the server, in that order.
How do you reduce TTFB with page caching?
Turn on full-page caching so the server serves a stored copy of the page instead of building it on every visit.
The WordPress optimization handbook says caching plugins store posts and pages as static files, which cuts the processing load on the server. For fairly static pages, it says this can improve performance several hundred times over.
- In your WordPress dashboard, open your cache plugin settings and turn on page caching.
- Set the cache to clear when you publish or update a post, so visitors never see stale content.
- Turn on cache preloading if your plugin offers it, so the first visitor after a purge still gets a cached page.
- Log out, load the page twice, and check the response headers for a cache hit.
Test as a logged-out visitor, because caching usually skips logged-in users. In DevTools, open the Network panel, click the document request, and look at the response headers for a cache status such as HIT.
A full walkthrough is in how to speed up WordPress.
Allow 30 minutes to turn on caching and test it. A cache plugin change takes effect at once, but the field data in PageSpeed Insights needs days to reflect it.
What if your pages are dynamic?
Logged-in pages, carts, and checkout pages should bypass the cache. Most cache plugins exclude them by default, so check the exclusion list before you turn caching on.
How does a CDN lower TTFB?
A CDN lowers TTFB by answering requests from a server near the visitor instead of sending every request to your origin server.
Distance matters, and the WordPress optimization handbook notes that the distance between your server and your visitors affects performance. A CDN mirrors files across regions so visitors get a closer server.
Most CDNs cache images, CSS, and JavaScript by default but pass HTML through to the origin. That leaves the request part of TTFB unchanged, so you need a CDN setup that caches HTML too.
Cloudflare's Automatic Platform Optimization caches WordPress HTML at the edge, which removes round trips to the origin and improves TTFB. It updates the edge cache when you change content and skips the cache for logged-in users.
The setup details are in Cloudflare cache rules for WordPress.
After you turn on HTML caching, load the page logged out and look for a cache HIT in the response headers. A MISS on the first load is normal, because the edge server has to fetch the page once before it can store it.
What should you change on the server to lower TTFB?
On the server, update PHP, turn on OPcache and a persistent object cache, and cut the plugins and theme code that run on every page.
The WordPress optimization handbook says newer PHP versions usually bring better performance and points to OPcache, which stores precompiled PHP so the server skips parsing code on each request. Ask your host whether OPcache is on for your plan.
A persistent object cache saves trips to the database, and the handbook says those extra trips slow down TTFB and can swamp the database during traffic spikes. Your host must offer the cache server, and you then add a matching object cache plugin.
Delete plugins you do not use and test the rest one at a time. The handbook calls deactivating and deleting unneeded plugins the first and easiest step, and Lighthouse's WordPress advice adds a light theme, ideally a block theme.
Your host matters too, as explained in how hosting affects WordPress speed.
A newer PHP version can help, and how PHP version affects WordPress speed covers the versions in detail.
How do you check that TTFB went down?
Re-run the same PageSpeed Insights test on the same URL and compare the new lab number with the one you recorded before the change.
- Record the TTFB value and the date before you change anything.
- Make one change at a time, such as turning on page caching.
- Clear the cache, load the page twice as a logged-out visitor, and re-run the lab test.
- Compare the lab number with your earlier value, then wait for the field data to catch up.
Field data covers the last 28 days, so a fix takes weeks to show in full. Google's PageSpeed Insights docs say the data updates daily and falls back to origin level when a single URL has too few samples.
Judge the fix by the field number, not by one lab run. Lab data is one simulated load, while field data is what your visitors actually got.
If the server itself is the limit, how to test hosting speed before buying shows how to compare hosts.
Does TTFB affect SEO and rankings?
TTFB is not a Core Web Vital, so it is not itself a ranking metric, but a slow first byte delays every metric that follows it.
The three Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. web.dev's TTFB page calls TTFB a foundational metric that precedes First Contentful Paint and Largest Contentful Paint, so high TTFB adds time to both.
In the Web Almanac 2025, 62% of mobile pages reached a good Largest Contentful Paint, under 2.5 seconds, while 48% of mobile sites passed all 3 Core Web Vitals. The HTTP Archive report is based on July 2025 data and shows steady gains since 2023.
The same report says the share of sites with a good TTFB rose by 1% on desktop and 2% on mobile since 2024. Gains are slow, so a site that fixes its server work can still stand out.
Fix TTFB when it holds back First Contentful Paint or Largest Contentful Paint. If those two are already good, a TTFB just over 0.8 seconds may not be worth chasing.
What mistakes should you avoid?
The most common mistake is chasing a single lab number while ignoring what real visitors experience in the field data.
- Testing only while logged in, when caching is bypassed for your own account.
- Comparing a cached page with an uncached one and calling the gap a fix.
- Running 2 cache plugins that fight over the same settings.
- Turning on HTML caching for carts, checkout, and account pages that must stay private.
- Judging a fix the same day, before the 28-day field data can move.
- Ignoring redirects, such as old http links that add a round trip before the page starts.
Check the cache headers after every change, and keep a note of the date and the lab number. If TTFB rises after a change, undo that one change and test again.
Frequently asked questions
Is TTFB the same as server response time?
No. Server response time is only the last part of TTFB: the wait between sending the request and receiving the first byte. TTFB also includes redirects, DNS lookup, and connection and TLS setup. Lighthouse reports server response time, while PageSpeed Insights field data reports full TTFB.
Is TTFB a Core Web Vital?
No. The Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. TTFB is a diagnostic metric that comes before them, so a slow first byte delays First Contentful Paint and Largest Contentful Paint even when nothing else on the page is slow.
How long does a TTFB fix take to show in PageSpeed Insights?
Lab results change at once, but field data covers the previous 28 days and updates daily, so a fix takes weeks to show in full. Keep the lab number as your short-term check and watch the field number over the next 28 days before you judge the result.
Can TTFB be 0?
No. Every request needs at least the time to send the request and receive the first byte back, even from a cache next door. A very low number usually means the page came from a nearby edge cache, not that the wait vanished. Compare cached and uncached loads separately.
Why is my TTFB fast in one test and slow in another?
Test location, cache state, and logged-in status change the result. A first load after a cache purge is slow, a second load is fast, and a test from far away adds network time. Run each test 3 times, test as a logged-out visitor, and compare the same page from the same place.
Does a cache plugin fix TTFB on its own?
It often cuts the largest part, because the server serves a stored page instead of building one. It cannot fix slow DNS, long redirects, a distant server, or a host that runs out of CPU and memory. If TTFB stays high with caching on, check those parts next.
Sources
- Time to First Byte (TTFB) web.dev
- Optimize Time to First Byte web.dev
- Reduce server response times Chrome for Developers
- About PageSpeed Insights Google for Developers
- Performance | 2025 | The Web Almanac by HTTP Archive HTTP Archive
- Optimization WordPress Developer Resources
- About Automatic Platform Optimization Cloudflare Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
