StackPath CDN (opens in new tab) (the service formerly known as MaxCDN) is a powerful content delivery network (CDN (opens in new tab)), relatively easy for novices to set up, yet with some very capable enterprise-level features on offer if you need them.
The service network (opens in new tab) has 50+ PoPs worldwide. It's a reasonable total, but most are in North America, South America and Europe, with only four locations in Asia and two in Oceania. We can't complain about capacity, though, with StackPath's 65 Tbps total throughput outperforming providers like CDN77 (opens in new tab) and Gcore Labs (opens in new tab) (both claim 50Tbps.)
- Want to try StackPath CDN? Check out the website here (opens in new tab)
Getting started can be as simple as specifying an origin server, maybe tweaking DNS records and integrating the CDN with your site. Free private SSL certificates are available if you need them, HTTP/2 support ramps up performance and there's fine-grained control over caching.
StackPath's EdgeRules extend the service by allowing you to customize your content delivery, adding or modifying headers, redirecting a request, adding a new cache rule or even protecting your content with URL signing.
A capable Web Application Firewall (WAF) gives you substantial protection out of the box. Built-in rules block common areas of attack: SQL injection, XSS, remote file inclusion, response header injections, common WordPress exploits, and many, many more. Many dangerous bots are blocked by the default settings, while behavior monitoring looks out for users acting in a dubious way, and suspicious visitors can be challenged with captchas to prove they're legitimate. And if all that's not enough, you can create custom WAF rules to block even more threats.
The Support site (opens in new tab) documents all this to a reasonable degree. It doesn't have the detail you'll get with Microsoft or Google, but it's also far more readable, and there's enough content to be useful. But if it doesn't help, 24/7 support is available via live chat, ticket, email and phone.
If you're tired of CDN pricing so complex that you need a custom calculator to figure out your bill, StackPath CDN will feel refreshingly different.
A simple starter plan (opens in new tab) gives you 1TB of traffic and unlimited requests for only $10 a month ($0.01 per GB.)
Need more bandwidth? No variable pricing per region, no scrolling through 25 price tiers, you just pay $0.04 per GB up to 100TB and $0.03 up to 1PB (after that, the company asks you to call and talk about it.)
Individual services - web application firewall (WAF), DNS and service monitoring - are an extra $10 a month each.
If you're looking for power, then you can also combine these, and maybe save a little cash. The Edge Delivery 20 (opens in new tab) package gets you 1TB of traffic, the Web Application Firewall with 5 million requests and five custom rules, two million DNS requests and monitoring of one service for just $20 a month.
What you don't get is a trial, or any initial credit to help you get started. But with a full month's service available for $10, it hardly seems reasonable to complain.
Overall, this is a nicely balanced pricing scheme which competes with budget providers like Bunny (opens in new tab) at the bottom end, while also supporting some more advanced features you'll need for more heavy-duty projects. Whatever you're doing, the chances are you'll find something to like here.
After a simple signup process, the StackPath site redirects customers to its web dashboard. Charts provide an overview of CDN traffic and WAF performance (once you're up and running, anyway), and a left-hand sidebar point you to the dashboard's various functions.
Head off to the Sites area, create a new Site with the domain you'd like to customize, and you're able to tweak it with StackPath's various settings and options.
You can add free private SSL certificates (opens in new tab) using StackPath's certificate manager, for instance. Default cache expiration time can be set to anything from 30 seconds to 30 days. Query String Control defines what happens with URLs including questions (mydomain.com/action?time=now.) There's Gzip and HTTP/2 support, you can control access to your site via CORS support, and a Content Persistence feature enables serving CDN content which has expired (handy if your origin server is down.)
There are some unusual but welcome touches. You can specify both backup and origin servers, for instance (also useful if your server is down.) Support for origin authentication allows the CDN to connect to resources which need a username and password. Gzip support isn't just an on/ off switch, you can also set a compression level to balance file size and compression time. And HTTP/2 server push can send content to the browser before it's requested, cutting load times.
There are some issues and limits. No direct Brotli compression support (you can still serve it with a workaround (opens in new tab)); no wildcards allowed when purging the cache (though you can delete everything); little support for applying settings to particular file types (turning on Gzip compresses txt, js, html, and css files, and the text/* mime type, for instance, but you can't specify anything else.)
CDNPerf (opens in new tab) measures CDN response times based on data taken from hundreds of millions of users every day, making the site a useful way to compare the top providers.
StackPath CDN worldwide response times are a little disappointing at 14th out of 20, with an average query time of 37ms. But keep in mind that the margins are tiny, and if your visitors aren't evenly spread around the world, you might get a better idea of speeds from the regional figures.
StackPath ranks 10th place in North America, for instance. Doesn't sound great, but its average query time was 34ms, and even the top-placed Google Cloud CDN (opens in new tab) was only fractionally ahead at 30ms.
But on the down side, StackPath's 17th place in Asia was based on an average response time of 116ms (no great surprise with a minimal four Asia PoPs), and the top seven CDNs all had responses under half the time.
The precise results you'll see might vary significantly depending on where your visitors are located, then, but keep in mind that these raw speeds are only part of the story. They don't take account of what you might do with features like StackPath's smart edge rules, and how they can make your content delivery even more efficient. CDNPerf's rankings are a good starting point, but it's just as important to look at a CDN's features and what they might do for you.
It's not the fastest or most powerful service we've seen, but StackPath is easy to set up, with low starter prices, some worthwhile bonus features and an excellent Web Application Firewall. A must-try for small and medium-sized projects.
- We’ve also highlighted the best CDN (opens in new tab)