How to Reduce Server Response Time (TTFB)

Introduction

TTFB (Time To First Byte), or time to first byte, measures how long your server takes to start sending data when a visitor enters your website. It’s the metric that best reflects hosting response speed.

A high TTFB means your server is slow. And no matter how much you optimize your website, if the server takes time to respond, the whole thing will be slow. In this article you’ll see what a good TTFB is and how to reduce it.

What TTFB is and how it’s measured

TTFB is the time that elapses from when the browser requests a page until the server starts sending the first byte of response.

It has three components:

1. Network time: the time for the browser’s request to reach the server.
2. Server processing time: how long the server takes to generate the page.
3. Response time: the time to start sending data.

[Imagen sugerida: diagram of TTFB components]

Reference values

TTFB	Rating
Less than 200 ms	Excellent
200-500 ms	Good
500-800 ms	Needs improvement
800-1500 ms	Slow
More than 1500 ms	Very slow

Google recommends a TTFB below 600 ms for mobile. Hosts with LiteSpeed and NVMe are usually below 200 ms.

How to measure your TTFB

With GTmetrix

1. Analyze your website on gtmetrix.com.
2. In the summary you’ll see the Time to First Byte.

With PageSpeed Insights

1. Analyze your website on pagespeed.web.dev.
2. In the diagnostics, look for Reduce initial server response time.

With online tools

There are free tools like KeyCDN Performance Test or Uptrends that measure TTFB from different countries.

Measure TTFB without being logged in to your website. If you enter as a WordPress administrator, the TTFB will be higher because the cached version isn’t served.

Causes of high TTFB

1. Slow hosting

The number one cause. Hosting with HDD disks, without LiteSpeed or overloaded has high TTFB.

2. No page cache

If each visit forces the server to generate the page from scratch (query database, execute PHP), TTFB goes up.

3. Many plugins

In WordPress, each plugin adds processing time to the server.

4. Slow database

Inefficient queries or a very large database slow down page generation.

5. Outdated PHP

Older PHP versions are slower.

6. Distance to server

If your hosting is in Spain and the visitor is in Mexico, there’s latency due to distance.

How to reduce TTFB

1. Use good hosting (most important)

Hosting is the factor that most influences TTFB. If your host uses:

• NVMe SSD disks (not HDD): much faster reading.
• LiteSpeed or Nginx as web server (not pure Apache): more efficient.
• PHP 8.x: faster than PHP 7.x.

At miHosting we use LiteSpeed and NVMe SSD on many plans, so our TTFB is typically below 200 ms. If your TTFB is high and you’re not with us, consider switching.

2. Enable page cache

Cache serves already-generated pages instead of generating them each time. It’s the improvement that most reduces TTFB in WordPress.

• LiteSpeed Cache if your host uses LiteSpeed.
• WP Rocket if not.
• W3 Total Cache or WP Super Cache as free alternatives.

With page cache, TTFB can drop from 800 ms to 100 ms. It’s huge.

3. Use a CDN

A CDN like Cloudflare serves your website from the server closest to the visitor, reducing network time.

4. Reduce the number of plugins

Each WordPress plugin adds processing time. Review and disable the ones you don’t need.

5. Update PHP

Use the most recent PHP version available on your host. In cPanel or DirectAdmin, you can change the version in Software → Select PHP Version.

PHP 8.3 is up to 30% faster than PHP 7.4. Switching versions can notably improve TTFB.

6. Optimize the database

In WordPress, plugins like WP-Optimize clean the database of unnecessary data (revisions, junk, transients).

7. Use HTTP/2 or HTTP/3

These modern protocols allow sending several files in parallel. Hosts with LiteSpeed already support them.

When high TTFB isn’t the host’s fault

Sometimes a high TTFB is not the host’s fault:

• You’re logged in to WordPress. The admin panel isn’t cached. Measure without logging in.
• You have a conflicting plugin. A poorly programmed plugin can slow everything down.
• The page is very heavy to generate. An online store with thousands of products requires more resources.
• Your website is under attack or has traffic spikes.

If in doubt, measure TTFB from different tools and at different times before concluding.

Useful tips

• Measure without being logged in. Cached pages load much faster.
• Measure from different countries. If your audience is international, measure from where they are.
• Switch from PHP 7.x to 8.x if you can. It’s one of the easiest improvements.
• Enable cache before measuring. Without cache, TTFB in WordPress will always be high.
• Don’t chase a perfect number. Going from 1200 ms to 300 ms is a huge achievement; from 300 ms to 100 ms is barely noticeable.

Common problems

My TTFB is high but I’ve enabled cache

Check that cache is actually working. Log in without being authenticated and measure. If you use a plugin that excludes certain pages, make sure the homepage is cached.

My TTFB differs by tool

It’s normal. Each tool measures from a different place and with different conditions. Look at the trend, not an isolated number.

I switched to a host with LiteSpeed and the TTFB barely dropped

It may be that your website isn’t taking advantage of LiteSpeed Cache. Install the plugin and enable it. Without the plugin, LiteSpeed doesn’t apply page cache to WordPress.

TTFB is good but my website is still slow

TTFB measures only the start of the response. If your website loads heavy files (unoptimized images, lots of JavaScript), the page may take time to finish loading even though TTFB is low.

I don’t know if my host has LiteSpeed or NVMe

Ask us. At miHosting, most professional plans use LiteSpeed and NVMe SSD. If your plan is older, consider an upgrade.

Frequently asked questions

What’s a good TTFB?

Under 500 ms is good. Under 200 ms is excellent. Over 1 second is slow.

Does my host affect TTFB?

It’s the most important factor. A host with LiteSpeed, NVMe and PHP 8.x has a much lower TTFB than a basic one.

Does CDN reduce TTFB?

Yes, because it serves the website from a server closer to the visitor. It reduces network time.

Can I reduce TTFB without changing hosts?

Yes, by enabling cache, updating PHP and reducing plugins. But there’s a limit: if the host is slow, the base TTFB will be high.

Does TTFB affect SEO?

Indirectally yes. A high TTFB hurts LCP (one of the Core Web Vitals), which is an SEO factor.

Good hosting, the foundation of a good TTFB

TTFB reflects your server’s health. If it’s high, no matter how much you optimize your website, you’ll be going with the handbrake on. The most effective improvement is using a host with LiteSpeed, NVMe SSD and PHP 8.x.

At miHosting we use LiteSpeed and NVMe SSD that offer TTFB below 200 ms. If your website has slow server response and you want a real improvement, open a ticket from your client panel and we’ll advise you.