{"id":8324,"date":"2017-10-11T06:00:31","date_gmt":"2017-10-11T10:00:31","guid":{"rendered":"https:\/\/blog.litespeedtech.com\/?p=8324"},"modified":"2017-10-11T06:00:31","modified_gmt":"2017-10-11T10:00:31","slug":"wpw-content-delivery-network-support","status":"publish","type":"post","link":"https:\/\/lswp.store\/index.php\/2017\/10\/11\/wpw-content-delivery-network-support\/","title":{"rendered":"WpW: Content Delivery Network Support"},"content":{"rendered":"

\"\"<\/p>\n

Welcome to another installment of WordPress Wednesday<\/a>!<\/p>\n

If you use a content delivery network (or CDN) along with LiteSpeed Cache for WordPress, this week\u2019s topic should appeal to you. You\u2019ve always been able to use LSCWP and a CDN together, but you needed an additional plugin to do so. Now, as of LSCWP v.1.2.3, we\u2019re officially supporting the use of CDNs, no additional plugin required!<\/strong><\/p>\n

Please note<\/strong>: This article does not apply to Cloudflare. Cloudflare is not a typical CDN, in that it is a distributed proxy server, as opposed to a reverse-proxy. This article applies to reverse-proxy CDNs only.<\/em><\/p>\n

What is a CDN?<\/h2>\n

Content delivery networks store static website content remotely in servers all around the world. The content may then be served to a site\u2019s visitor from the server that is physically closest to that visitor\u2019s location. The closer the server, the less time the data takes in transit. A CDN is a great complement to the page-caching functionality of LSCWP. LiteSpeed speeds up the serving of all of the dynamically-generated content, while the CDN speeds up the delivery of the static content (images, CSS, JavaScript, etc).<\/p>\n

How does LSCWP support CDN use?<\/h2>\n

\"\"<\/p>\n

When you start using a CDN for static content, those files stop being served from your site\u2019s file system, and instead are pulled directly from the CDN. WordPress requires a plugin to change all of the appropriate links to be CDN links. Without a plugin, you would have to manually change all of your static file links to point to the CDN\u2019s URL. Not only is that a nuisance, but it\u2019s not always possible to do.<\/p>\n

For all practical purposes, a plugin is required if you are going to use a CDN with WordPress.<\/p>\n

If you\u2019re already using a CDN alongside LSCWP, you\u2019ll know that they complement each other well. It\u2019s a nice bonus, then, that you can now configure both in a single plugin!<\/p>\n

If you\u2019re new to CDNs, you\u2019ll appreciate the ability to get yours up and running in a familiar plugin environment.<\/p>\n

Setting it up<\/h2>\n

These settings link LSCWP to your existing CDN. If you don\u2019t currently use a CDN service, you\u2019ll have to obtain one before these settings will be of any use to you.<\/p>\n

\"\"<\/p>\n

LSCWP\u2019s CDN support works by substituting the CDN URL for your site\u2019s URL on the relevant static files. The settings below allow you to define the parameters for these substitutions. First specify the two URLs, and then choose the static files to be included or excluded.<\/p>\n

Enable CDN<\/h3>\n

This is the button that enables the functionality. If this is not turned ON<\/code> then none of the other options matter. CDN support is turned OFF<\/code> by default.<\/p>\n

Original URL and CDN URL<\/h3>\n

Original URL<\/strong> defaults to your site’s root URI. It shouldn’t be necessary to change this. If you do change it, be sure that the URI begins with \/\/<\/code> as in \/\/yoursite.com<\/code>.<\/p>\n

CDN URL<\/strong> is the root URL for content that is served from the CDN. It should be a full URL beginning with http<\/code>.<\/p>\n

When LSCWP generates the cached static version of a dynamic page, these two settings work together to allow the CDN URL to be substituted for the Original URL where appropriate.<\/p>\n

Includes<\/h3>\n

These settings allow you to specify which types of static content are being handled by your CDN. They are all turned off by default, but you may turn on whichever file types are appropriate for your application. The Include Images<\/strong> setting refers to images that are accessed via img<\/code> tags and CSS url()<\/code> attributes. Images accessed in any other manner can be included through the Include File Types<\/strong> setting.<\/p>\n

Include File Types<\/h3>\n

This setting is for files that are accessed via src<\/code>, data-src<\/code>, and href<\/code> tags.<\/p>\n

Exclude Path<\/h3>\n

If there are sections of your site that are not served from the CDN, specify the paths here (one per line) so that LiteSpeed will not go to the CDN for those. You may enter partial paths here, no wildcards required.<\/p>\n

\"\"<\/p>\n

If you\u2019ve been running a site for any length of time, you know that WordPress offers many opportunities for optimization. (This is just a more positive way of saying \u201cWordPress can be really slow.\u201d) Page caching<\/a>, browser caching<\/a>, database optimization<\/a>, minification, combination, HTTP\/2 Push<\/a>, and Content Delivery Networks are all excellent ways to speed up your site, and they are all supported in the LiteSpeed Cache for WordPress plugin<\/strong>!<\/p>\n

We hope you\u2019ll try some of these new features soon, if you haven\u2019t already, and let us know what you think. We love getting your feedback!<\/p>\n

—<\/p>\n

Have some of your own ideas for future WordPress Wednesday<\/a> topics? Leave us a comment!<\/p>\n

Don\u2019t forget to meet us back here next week for the next installment. In the meantime, here are a few other things you can do:<\/p>\n