A CDN is a collection of servers located all around the world. When a browser loads static content, the request is automatically routed to the server geographically closest to the browser. This helps the content load much more quickly. In addition, because your content is loaded from many servers in separate locations, bursts of traffic are less likely to cause issues, because the burst is spread out over hundreds of servers, rather than just one.
Force WP offers the ability to put all of your static content on a CDN with little to no configuration required. We manage distributing the content and rewriting URLs in the code. We give you control over enabling or disabling the CDN as needed. In short, you just write your blog as usual and we transparently make your blog faster and more scalable. Clients can add CDN service for a small monthly fee.
What CDN provider do you use?
Our CDN services are provided via our partner MaxCDN.
Where are your CDN servers located?
MaxCDN’s network is comprised of servers located all over the world, including North America, Europe, and Asia. You can find more information about their data center locations on their page here.
Why are my CDN URL’s different than my domain name?
Normally your URL paths would be something similar to:
With a CDN enabled, they become:
This is because those static assets are now loading from a third party server, rather than the same server where your WordPress site is hosted. If you’d like, the “cdnzonename.forcewp.netdna-cdn.com” part of the URL can be changed to a custom CDN URL such as cdn.domain.com. To do so, you’ll just need to setup a CNAME in your DNS Zone that points your custom subdomain to the default CDN URL, then contact support to let us know. We’ll then make the required updates on our end. If you’ve activated CDN from your user portal, you will see your default CDN URL there. Setting up a custom CDN URL is optional; you can leave your CDN URL as its default if you wish.
What content is served by the CDN?
By default, we serve all the static assets located in your wp-content folder from CDN. We also serve assets which appear like dynamic PHP content but are in fact static files like CSS, JS, and images. This includes thumbnailing systems, minification plugins, and similar. Core files are also served from CDN. If you have static assets you’d like served from the CDN that are stored outside the wp-content folder, please contact support with the path to the directory or file and we will include it for you.
Content not being found and delivered by CDN
Our script automatically rewrites your site’s assets to use the CDN URL once activated. Though there are some circumstances when our script will not catch the URL. These can include:
1. A direct URL inside a CSS file. This is a link that uses a full URL For example, http://yourdomain.com/… as opposed to a path only i.e. /image.gif” or “image.gif”. For our rewrite to work properly, paths in your CSS code need to be relative and not use full URLs, because we don’t search/replace inside CSS. You can edit the CSS code to use the CDN domain, but it’s best to structure your CSS code so all URLs are relative. This will help ensure compatibility overall, rather than just with CDN.
How do I enable the CDN for my site?
To enable the CDN on your site, you’ll first log into the User Portal. Select the WordPress install that you wish to enable, and click on the CDN link on the left hand side. Then check the box for the domain that you wish to enable. The list for domains on which CDN can be enabled is generated from the list of domains that have been attached to your install. This list is found inside the Domains link just above the ‘CDN’ link in your user portal.
Note: The CDN can take up to 10 minutes to configure and everything to clear through the cache, so don’t be alarmed if you don’t see the change right away. If after 10 minutes you’re still seeing issues, just let us know.