cdnperf.com shows the performance/reliability of several popular WordPress CDNs.
But it doesn’t list StackPath (used on RocketCDN and CloudwaysCDN), QUIC.cloud (used on LiteSpeed), FlyingCDN (used on FlyingPress), WPX’s XDN, and many other WordPress CDNs.
It also doesn’t take into account features like Cloudflare’s APO, BunnyCDN’s Optimizer, or QUIC.cloud features. That said, I’ve done my best to rank the top WordPress CDNs based on cdnperf.com, features, PoPs, popularity in Facebook groups/polls, and even TrustPilot ratings. I’ve also used most CDNs in this list (Cloudflare, BunnyCDN, StackPath, FlyingCDN, KeyCDN).
The “best” CDN can also depend on other factors. Some CDNs can only be used on certain hosting providers. The location of PoPs can make sense if visitors are in specific locations. And of course, your budget. Without further ado, let’s take a look at the best CDNs for WordPress.
Tip #1: The best CDN is somtimes the one with the closest PoPs to your visitors. Be sure to check each CDN’s data center page to see if they make sense for your location.
Tip #3: Regardless of your CDN, I recommend Cloudflare or DNS Made Easy for DNS.
It’s hard to beat Cloudflare, especially with all the new features.
Aside from their consistently performant CDN with 250+ data centers, it has a vast number of features to improve speed/security. Whether you want to use a faster DNS, improve TTFB with APO, or lower CPU usage by blocking unwanted bots/requests, Cloudflare seems to have it all.
While the free version is fine for most websites, I definitely recommend configuring the Cloudflare dashboard and testing their APO. And if you want to get serious with Cloudflare, check out rocket.net hosting which has Cloudflare enterprise features built-in to their plans.
Notable Cloudflare Features
- DNS – one of the fastest and most reliable DNS providers on dnsperf.com.
- CDN – go to DNS settings and change your website from DNS only to proxied.
- TLS 1.3 – fastest TLS protocol (I recommend setting min. TLS version to 1.2).
- Bot Fight Mode – block spam bots which are logged into your firewall events.
- Early Hints – early preload/preconnect hints which improves server wait time.
- Crawler Hints – tells crawlers if content is updated to prevent wasteful crawls.
- Page Rules – here’s a screenshot of 3 common page rules for WordPress sites.
- Firewall Rules – another screenshot of 4 common firewall rules for WordPress.
- HTTP/3 With QUIC – delivers website from faster HTTP/3 (use a HTTP/3 test).
- Hotlink Protection – stops websites from copying images and using bandwidth.
- Zaraz – offloads third-party scripts to Cloudflare (Google Analytics, Ads, others).
- SXGs – prefetches content so it loads faster when your site is clicked in Google.
- WAF (Paid) – powerful firewall to block attacks and prevent unwanted requests.
- TCP Turbo (Paid) – automatic TCP settings and optimizations to reduce latency.
- APO (Paid) – caches HTML and can give you a fast TTFB worldwide (view guide).
- Argo (Paid) – avoids traffic congestion by routing through fastest network paths.
- Load Balancing (Paid) – traffic is re-routed to healthier and faster origin servers.
Highly recommended in Facebook Groups (also used by FlyingCDN from FlyingPress).
Cheaper compared to most paid CDNs and is pay-per-region (each region is a different price). Unlike Cloudflare which proxies traffic, BunnyCDN requires creating a pull zone. Afterwards, they will assign you a CDN URL (which you’ll paste in your cache plugin) and a pull zone name (which you’ll paste in the BunnyCDN plugin). They have several features to speed up your site.
Notable BunnyCDN Features
- Bunny Optimizer – minify CSS/JS and optimize images (compression, resizing, WebP). But costs $9.50/mo and is cheaper when you get it through FlyingCDN.
- Perma-cache – stores uncached content to up to 5 geo-replicated storage locations which also results in less requests to the origins servers (learn more).
- Safehop – if an origin request fails, BunnyCDN will retry which reduces errors.
- Security Settings – several security settings which can block unwanted requests.
BunnyCDN has setup instructions but it’s very easy:
QUIC.cloud’s CDN is built specifically to work on LiteSpeed servers.
In other words, you will need to choose a host that uses LiteSpeed (i.e. A2 Hosting or NameHero), install the LiteSpeed Cache plugin, then use it to setup QUIC.cloud CDN. NameHero does a solid job in showing you how to setup QUIC.cloud in this video at 6:41.
QUIC.cloud and LiteSpeed are still relatively new and lack documentation. But since LiteSpeed has blown up and is faster than Apache servers, moving to a LiteSpeed host and using LiteSpeed Cache and QUIC.cloud has quickly become one of the most popular setups in Facebook Groups.
To use Google Cloud CDN, you need to use a host that supports it.
To my knowledge, Closte is one of the only popular hosts that use Google Cloud CDN. Otherwise, this probably won’t be an option for you and you’ll need to use a different CDN.
Amazon’s CloudFront is one of the fastest CDNs ranked by CDNPerf.
But they’re not as easy to setup as other CDNs (so use the video tutorial below or see written instructions). You would create an S3 bucket, then create a CloudFront distribution. They also have their AWS for WordPress plugin and 310+ POPs which is about 60 more than Cloudflare.
KeyCDN is another consistently performant CDN with great reviews on TrustPilot, but it’s more expensive with less data centers than BunnyCDN.
KeyCDN’s performance test is a great tool that measures TTFB in 10 global locations. This is a better way of measuring your TTFB than the single location in other testing tools like GTmetrix.
StackPath is a CDN also used by RocketCDN (from WP Rocket) and CloudwaysCDN.
Even though they make it easy to setup, I wouldn’t lean towards StackPath. WP Johnny and others have reported StackPath can be slower than other CDNs (you can check their TrustPilot reviews). Ever since they took over MaxCDN, there has been increased complaints about them.
If you do decide to test StackPath, you might be better off purchasing it through RocketCDN which has a different pricing structure (it’s much cheaper) than found on StackPath’s website.
8. Your Hosting CDN (WPX, GoDaddy, etc.)
If using WPX, I recommend using LiteSpeed Cache + QUIC.cloud CDN since WPX uses LiteSpeed. And if using GoDaddy, I would use another CDN because GoDaddy isn’t great at much. Most hosts use third-party CDNs in this list, so be sure to check who they actually use.
Statically is a free CDN you can setup using their plugin.
10. Sucuri CDN
Sucuri is a security service at heart so I would personally lean towards a company that specializes in the CDN field, or at least speed optimization. Plus, they only have 14 locations which is unattractive. I haven’t had a chance to try their CDN, just know it’s not widely used.
JetPack’s CDN is another option, but I never recommend using JetPack.
Do You Agree?
Do you agree with these CDN rankings? I’d love to hear your own experience in the comments. And of course, any suggestions you would like to see me add to this guide are always welcome.