How To Reduce Server Response Time (TTFB) In WordPress To <100ms Globally

Hosting/CDN are the easiest ways to reduce server response times.

To measure your globally TTFB, use SpeedVitals or KeyCDN’s Performance Test. Most other testing tools like GTmetrix and PageSpeed Insights only measure TTFB in 1 single location.

Hosting is tricky because there’s so much bad information out there, but I’ve written several reviews explaining why most mainstream hosts don’t live up to the hype (SiteGround, Kinsta, WP Engine, Hostinger, and WPX aren’t good). Better options are cloud hosting on Rocket.net (what I use), Vultr High Frequency, and DigitalOcean. Make sure to check whether your hosting plan is shared vs. cloud, uses SATA SSDs vs. faster NVMe SSDs, and has enough cores/RAM. Test your site in WordPress Hosting Benchmarks and use a data center geographically close to users.

When users are far from your origin server, TTFB gets slower (shown here). CDNs help by mirroring files to their edge network, but they usually don’t cache dynamic content/HTML by default. This is what full page caching does (like Cloudflare APO or FlyingProxy). You could also use the Super Page Cache plugin, or if you’re on LiteSpeed, QUIC.cloud also does HTML caching.

The final touch lies in other CDN features like Cloudflare’s Argo and DNS which performs well on dnsperf.com (reducing latency), load balancing, and security features like WAF to block unwanted requests from hitting your server. The more unwanted requests you block (and the more files you cache), the less work the origin has to do. Cloudflare Enterprise is excellent for improving TTFB with  270+ locations, full paging caching, Argo, among other features. I’ll also show you why Rocket.net’s Cloudflare Enterprise is faster than Cloudways/Kinsta’s. Avoid WP Rocket’s RocketCDN and SiteGround’s CDN which don’t have many locations or speed features.

What Is A Good TTFB?

Google flags your TTFB if it’s over 600ms but they used to recommend just 200ms. You can aim for 600ms on shared hosting and 200ms on VPS/cloud. TTFB also depends on where you test it.

0-200ms	Google Recommended
0-600ms	Passes Core Web Vitals
600ms+	Fails Core Web Vitals

How To Test TTFB Globally

KeyCDN and speedvitals.com measure TTFB in multiple global locations while PageSpeed Insights and GTmetrix only measure TTFB in 1 location per test. Latency and TLS also impact TTFB which KeyCDN measures (for the record, TTFB affects LCP too). On a normal site without a CDN or HTML caching, TTFB gets slower when your site is tested far away from the origin server. With the right optimizations and edge network, you can have a fast TTFB anywhere in the world.

 

1. Cache HTML

Most CDNs don’t cache HTML.

When caching HTML with Cloudflare’s APO, this improved TTFB by 72%. However, APO is just one way to do it. There are many  tools you can use depending on your hosting and CDN setup.

APO – serves HTML from Cloudflare’s edge network. The main difference between APO and a cache everything rule is the use of Workers KV storage and purging. It’s $5/mo and they have setup instructions. First make sure traffic is proxied through Cloudflare by using the orange cloud in the DNS settings. Once you purchase APO, you’ll create a token, install the Cloudflare plugin, enter your Cloudflare email + token, then activate APO. Visit uptrends.com, test your website using the www version, and make sure the headers match with the screenshot below.

Super Page Cache For Cloudflare Plugin – plugin is similar to a cache everything page rule only it gives you more control by excluding pages from the cache, sessions for logged in users, ajax requests, etc. Here’s a thread from the plugin developer on how this is different than APO.

FlyingProxy – Gijo’s product from WP Speed Matters. It caches HTML and also includes Cloudflare Enterprise features like priority routing, WAF, DDoS protection, image optimization, and other speed/security optimizations. It’s $10/month and can be used on any website/host.

QUIC.cloud HTML Caching – if you’re on a LiteSpeed server, use the LiteSpeed Cache plugin to setup QUIC.cloud CDN which has HTML caching. You should ideally use the paid (standard) plan since the free plan only uses 6 PoPs, while the standard plan uses all 70 PoPs + DDoS protection.

SiteGround Optimizer’s Full Page Caching – SiteGround’s version of Cloudflare’s full page caching which can be setup using the SiteGround Optimizer plugin, although I don’t suggest using this plugin for much else beyond caching since it does a poor job addressing core web vitals and is unstable. Your website is also forced to use the WWW version in the domain name.

 

2. Use A Host With Cloudflare Enterprise

3 popular hosts with Cloudflare Enterprise are Rocket.net, Cloudways, and Kinsta.

Rocket.net is the one you want. They’re the only host using Cloudflare Enterprise + full page caching which is also free. Cloudways/Kinsta don’t include full page caching and Ben Gabler (Rocket.net CEO) built the entire company and data centers around Cloudflare. You get 32 CPU cores + 128GB RAM + NVMe + Redis on all plans which is more resources than Kinsta and nearly any host. Because only about 10% of traffic actually hits your origin, they don’t need to limit PHP workers while allowing up to 25x monthly visits than Kinsta. This is why their customers average a <100ms global TTFB. Also a top performer in Kevin Ohashi’s WP Hosting Benchmarks.

With Cloudflare Enterprise, you get features that improve both TTFB and security: prioritized routing, WAF, Argo + tiered cache, load balancing, Mirage/Polish, as well as full page caching.

	Kinsta	Rocket.net
CPU Cores	12 Cores	32 Cores
RAM	8GB	128GB
Staging CPU Cores	1 Core	32 Cores
Staging RAM	8GB	128GB
PHP Worker Limits	Yes	No
Monthly Visits ($30-$35/mo plan)	25,000	250,000
Redis	$100/mo	Free
Storage	Network SSDs	NVMe
TrustPilot Rating	4.3/5	4.9/5

LiteSpeed is also a solid choice. It’s faster than Apache/NGINX and handles more requests with less chance of CPU spikes. Plus, you get LiteSpeed Cache + QUIC.cloud. Here’s a list of LiteSpeed hosts I recommend with NameHero, ChemiCloud, RunCloud, and GridPane being four top picks. LiteSpeed’s server-level caching and QUIC’s HTML caching are great features for reducing TTFB.

 

3. Choose A Plan With Enough Memory (RAM)

Some hosts don’t list how many CPU cores + RAM you get which is usually a red flag.

Here are 4 hosts that do. For example, when you compare NameHero’s specs with Hostinger’s specs, NameHero gives you more CPU/RAM than Hostinger, which is why Hostinger is cheaper.

When you compare Rocket.net to Kinsta, Rocket.net gives you 32 cores + 128GB RAM while Kinsta only gives you 12 cores + 8GB RAM. Both these are listed in each host’s inner pages/blog.

 

4. Choose A Plan With NVMe Storage

NVMe performs better than SSD hard drives, especially when it comes to disk I/O.

Here’s a test by Rocket.net using the WordPress Hosting Benchmark Tool plugin which was done after Kevin Ohashi’s WP Hosting Benchmarks to see if they could improve in 2022’s test.

Rocket.net isn’t the only WordPress host using NVMe. So does Vultr High Frequency, NameHero’s Turbo Cloud plan, A2 Hosting’s Turbo Boost plan, and several others. Check their specs page! SiteGround, Kinsta, Hostinger, and many other mainstream hosts don’t use NVMe.

 

5. Select A Data Center Close To Your Visitors

If visitors are from a specific location, choosing a close data center is still important.

Let’s say 90% of traffic is served from Cloudflare, but 10% is hitting your origin because certain files aren’t cached or you’re getting cache misses. You still want a close data center for that 10%.

 

6. Use Cloudflare Argo For Better Traffic Routing

Argo improves TTFB by avoiding traffic congestion and delivering content from faster, more reliable network paths. It also has tiered caching + TCP optimizations, but only makes sense if visitors aren’t local. It’s a paid service and worth testing if you have slow server response times.

If you use Argo, be sure to request beta access to cache reserve.

 

7. Use Load Balancing To Route Traffic From Unhealthy Origins

Load balancing steers traffic away from unhealthy origins and distributes traffic to the most available server pools (improving latency which is part of TTFB, as well as uptimes). However, this can get expensive and you’ll probably just want to use Cloudflare Enterprise somewhere else which usually includes load balancing. Cloudflare has a video on setting it up in Cloudflare.

 

8. Reduce Latency With A Fast DNS

TTFB includes latency, so your DNS matters too.

Check dnsperf.com to see the fastest, most reliable DNS providers. Cloudflare is consistently one of the top performers and is free. GoDaddy’s doesn’t perform well, Amazon Route 53 is alright (used by Kinsta), and even Google Cloud isn’t the fastest. SiteGround’s DNS was also blocked by Googlebot for 4 days, so I wouldn’t use their DNS either. Try to stick with Cloudflare.

How To Move Your DNS To Cloudflare

Sign up for Cloudflare through their website, add your website, and they will scan records. Cloudflare will eventually provide you with 2 nameservers. Login to your domain registrar (i.e GoDaddy/Namecheap) and find the option to change nameservers (usually in the DNS settings). Replace the nameservers with Cloudflare’s, then in Cloudflare, click ‘Done, check nameservers.’

 

9. Reduce Server Load

I recommend skimming through my tutorial on reducing CPU usage since eliminating unnecessary requests reduces the load on your server, whether it’s on the frontend or backend.

A lot of this is disabling/blocking things you don’t need: aggressive bots, XML-RPC, plugin modules, etc. Some things can be limited too (changing how preloading/purging works in your cache plugin is a big one, limiting the WordPress Heartbeat API, autosaves, post revisions, etc).

Quick Tips To Reduce CPU Usage:

• Control preloading in cache plugins
• Control cache clearing in cache plugins
• Replace wp-cron with a real cron job
• Limit heartbeat, autosaves, post revisions
• Remove plugins causing high CPU usage
• Disable unused features in module-based plugins
• Protect the wp-login page and limit login attempts
• Avoid plugins that run scans or add database bloat
• Block AhrefsBot + SemrushBot if you don’t use them
• Don’t cache logged-in users if you don’t need to
• Decrease the batch size when removing unused CSS
• Don’t create a separate mobile cache if you don’t need to
• Check if certain cache plugin settings increase CPU usage
• Use a firewall to block unwanted requests to your server (important!)
• Enable hotlink protection to prevent websites from stealing bandwidth
• Use Cloudflare bot fight mode, crawler hints, rate limiting, firewall rules

 

10. Use PHP 8.0

Higher PHP versions handle more requests/second.

Login to your hosting account and update to the latest stable PHP version. It’s a good idea to keep other technologies updated as well (MySQL version, WordPress core, themes, plugins, etc).

 

11. Enable OPcache

OPcache reduces CPU usage by optimizing scripts and stores compiled PHP scripts in memory. It can be enabled in cPanel’s PHP Extensions, Cloudways has a guide, or Google it for your host.

 

12. Enable Object Cache

Object cache stores database query results so they can be accessed quickly which can reduce loads and server response times.

I generally recommend Redis over memcached which is known for having more efficient memory usage. Cache plugins like LiteSpeed Cache, W3 Total Cache, and SG Optimizer have object cache settings where you can set it to Redis or memcached. You also need to enable it in your hosting account (i.e. cPanel PHP Extensions or SiteGround Site Tools). Enabling the Redis add-on in Cloudways installs Object Cache Pro as a drop-in plugin. Some hosts like Rocket.net require a specific Redis plugin so make sure to go through their documentation or ask support.

 

13. Test With And Without Gzip/Brotli

Compressing pages with Gzip or Brotli can sometimes increase TTFB, so make sure you test this. Check if your host supports Gzip/Brotli compression (Brotli is generally faster than Gzip).

 

14. Enable HTTP/3

Cloudflare’s test showed TTFB was 12.4% faster when using HTTP/3.

If you’re on LiteSpeed, you can enable HTTP/3 using QUIC.cloud in LiteSpeed Cache. As Ryan from NameHero explains, Cloudflare’s HTTP/3 setting pulls from HTTP/2 and delivers from HTTP/3 (which is not full HTTP/3 support). For best results, follow his video to enable HTTP/3.

 

15. Reduce TLS/SSL Latency

These settings are found in Cloudflare’s SSL/TLS settings. Optimizing these can reduce latency and TTFB (TLS can be measured in KeyCDN).

• Full (Or Full Strict) SSL – this is what Cloudflare recommends anyway.
• Always Use HTTPS – safe to use if all connections are served from HTTPS.
• TCP Turbo (Pro Feature) – reduces latency by automatically choosing TCP settings.
• Minimum TLS Version – set to 1.2 (same with TLS settings in your hosting account).
• Custom SSL (Pro Feature) – upload SSL to Cloudflare to terminate SSL/TLS at the edge.

 

16. Invest In A Better Cache Plugin

Cache plugins reduce TTFB by improving server processing times and serving files directly (reducing PHP/MySQL queries). 4 key things to consider when choosing a cache plugin are:

• How well it addresses core web vitals.
• The actual caching and how fast it is (server-side vs. file-based).
• Whether it optimizes mostly for scores or real-world browsing as well.
• Whether you’re forced to use a specific CDN and how good that CDN is.

	SG Optimizer	WP Rocket	FlyingPress
Server-side caching	✓	x	x
Delay JavaScript	x	✓	✓
Remove unused CSS	x	Inline	Separate file
Critical CSS	x	✓	✓
Preload critical images	x	x	By number
Exclude above the fold images	By class	By URL	By number
Lazy load background images	x	Inline	Helper class
Fetchpriority resource hint	x	x	✓
Lazy render HTML elements	x	x	✓
Add missing image dimensions	x	✓	✓
YouTube iframe preview image	x	✓	✓
Self-host YouTube placeholder	x	x	✓
Host fonts locally	x	x	✓
Font-display: swap	x	✓	✓
Preload links	x	✓	✓
CDN (beyond Cloudflare)	SiteGround CDN	StackPath	BunnyCDN
CDN PoPs	14	60	93
CDN Tbps	N/A	65	80
Dynamic caching	✓	x	x
CDN geo-replication	x	x	✓
CDN image optimization	✓	x	✓
CDN image resizing for mobile	x	x	✓
Documented APO compatibility	x	x	✓

 
FlyingPress – excellent job addressing both core web vitals and real-world browsing, settings are easy to configure, and it can be used with any host. FlyingCDN is powered by BunnyCDN which is a solid CDN choice especially since it includes Bunny Optimizer’s image optimization as well as geo-replication. The cons are that it costs money and doesn’t have server-side caching.

LiteSpeed Cache – faster server-side caching and also does an excellent job addressing core web vitals and real-world browsing. It’s free, has great ratings on WordPress, and QUIC.cloud is a solid CDN with HTML caching, image optimization, and security features. Main cons are you have to use a LiteSpeed host and there are a lot of settings which can be difficult to configure.

WP Rocket – doesn’t address core web vitals as much as FlyingPress or LSC. Also doesn’t do a great job optimizing for real-world browsing. RocketCDN (StackPath) performs poorly and was removed from cdnperf.com. Settings are easy(ish) but also costs about the same as FlyingPress.

SiteGround Optimizer – only use it for caching, not for core web vitals. It also has a history of compatibility issues where Hristo constantly blames third-party themes/plugins. I’d only use it for dynamic caching and memcached (and maybe Cloudflare’s full page caching), then disable everything else and use a different plugin. It’s free and the settings are easy, but bad otherwise.

Free Cache Plugins – most free cache plugins do a poor job addressing core web vitals. W3 Total Cache and Swift Performance are alright, but I suggest leaning towards something else.

NitroPack – cheats PageSpeed scores by moving things off the main-thread which gives you false scores in speed testing tools. Doesn’t actually improve real-world browsing or page load times as much as other cache plugins. Never recommended NitroPack and probably never will.

 

17. Limit Preloading And Disable Automatic Cache Clearing

Preloading can cause high CPU usage and stress out your server. It’s used in WP Rocket, LiteSpeed Cache’s crawler, SiteGround Optimizer’s preheat cache, and other cache plugins.

The problem is that by default, your entire website is preloaded using your sitemap. Another problem is the entire cache is cleared when specific actions are taken (something as simple as updating a widget). And finally, the preload interval may be too high for your server to handle. A few easy tweaks can significantly reduce the amount of server resources preloading consumes.

• Only preload important sitemap URLs (i.e. pages/posts), not the entire sitemap.
• Increase the interval pages are preloaded (WP Rocket has a helper plugin for this).
• Disable automatic cache clearing (WP Rocket has another helper plugin). Any time you do a specific action, the entire cache is cleared (here are the actions for WP Rocket). This can cause a lot of stress on the server especially if you’re working on your website outside of writing content. A better alternative is to disable automatic cache clearing and use a cron job to control what happens when the cache is cleared and when (i.e. middle of the night).

 

18. Increase TTL

A longer TTL (time to live) is better for performance since the cache doesn’t have to rebuild as frequently. It also leads to a better cache hit ratio. As I mentioned before, the more cache hits you can get, the faster your TTFB will be. Google recommends caching static resources for an entire year which fixes serve static assets with an efficient cache policy in PageSpeed Insights. This is usually done in your hosting account or CDN, depending on where your cache is stored.

 

19. Clean Your Database Thoroughly

Do a thorough database cleanup with WP-Optimize.

This lets you go through your plugin tables, view how much overhead they add, and remove tables left behind by old plugins. And who knows, maybe you’ll see specific plugins/modules add lots of database bloat. I did, so disabled several features in Rank Math like their Analytics.

 

20. Identify Slow Plugins, Queries, Bottlenecks

Here’s how: