{"id":9436,"date":"2018-03-28T06:00:30","date_gmt":"2018-03-28T10:00:30","guid":{"rendered":"https:\/\/blog.litespeedtech.com\/?p=9436"},"modified":"2018-03-28T06:00:30","modified_gmt":"2018-03-28T10:00:30","slug":"jetpack-photon-cdn-and-litespeed-cache","status":"publish","type":"post","link":"https:\/\/lswp.store\/index.php\/2018\/03\/28\/jetpack-photon-cdn-and-litespeed-cache\/","title":{"rendered":"WpW: Using Jetpack’s Photon CDN With LSCache"},"content":{"rendered":"

 <\/p>\n

 <\/p>\n

\"WordPress<\/a><\/p>\n

Welcome to another installment of WordPress Wednesday<\/a>!
\nToday\u2019s topic is: Jetpack Photon CDN and LiteSpeed Cache<\/strong><\/p>\n

Disclaimer<\/strong>: The information contained in this post is accurate for LSCWP v2.1.1.1 [release log<\/a>]. If you are using a newer version of the plugin, some details may have changed. Please refer to our wiki<\/a> for the latest!<\/em><\/p>\n

What is Photon?<\/h2>\n

Automattic\u2019s Jetpack plugin<\/a> allows self-hosted WordPress blogs to use some of the functionality that is natively available to WordPress.com blogs. One of the available functions is a content delivery network (CDN) for images. Originally, this service went by the name \u201cPhoton,\u201d but now it they simply call it \u201cJetpack Image CDN<\/a>.\u201d (Many people still refer to it as Photon, which is why I mention it.)<\/p>\n

Use of the image CDN is contingent upon your site being Jetpack-connected. If you disconnect Jetpack from your site, you are no longer allowed to use the image CDN.<\/p>\n

Using Jetpack Image CDN with LSCWP<\/h2>\n

Jetpack\u2019s Image CDN and LiteSpeed Cache for WordPress are 100% compatible and may be used together right out of the box.<\/strong><\/p>\n

Normally we recommend enabling CDN support in the LiteSpeed plugin, and then uninstalling any CDN-specific plugin you may have had. That is not the case here<\/em>.<\/p>\n

Because of Jetpack\u2019s rule that Jetpack must remain connected to your site, you are not allowed to uninstall their plugin if you want to continue to use their image CDN.<\/p>\n

 <\/p>\n

\"Jetpack\u2019s<\/a><\/p>\n

So, how do you make all of this work when you have both Jetpack and LiteSpeed plugins installed? It\u2019s simple. You let Jetpack do its thing, and set up LiteSpeed to stay out of the way:<\/p>\n

    \n
  1. Turn on the image CDN feature in Jetpack.<\/li>\n
  2. Leave Enable CDN<\/strong> set to OFF<\/code> in LiteSpeed Cache > Settings > CDN<\/strong>.<\/li>\n<\/ol>\n

    LSCache for WordPress respects the settings of other CDN plugins, when LiteSpeed\u2019s CDN support is turned off.<\/p>\n

    A Note about Image Optimization<\/h2>\n

    LiteSpeed Cache has an Image Optimization service, but we don\u2019t recommend you use it, if you have Jetpack\u2019s Image CDN enabled. Jetpack\u2019s CDN automatically does its own optimization, and will ignore the LiteSpeed-optimized images.<\/p>\n

    Additionally, Jetpack has its own WebP replacement functionality, so do not<\/em> enable LiteSpeed\u2019s Image WebP Replacement<\/strong> setting in the Media<\/strong> tab.<\/p>\n

    To Summarize<\/h2>\n

    If you want to use Photon, then LiteSpeed will respect that, as long as you leave LiteSpeed\u2019s CDN and Image Optimization features turned off.<\/p>\n

    One exception: if you have multiple CDNs in use (i.e., Jetpack for the images and, say, MaxCDN for other static content), you may enable LiteSpeed\u2019s CDN support, but be sure to configure it only for the file types not served by Jetpack<\/em>.<\/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