Many simple sites do just fine with public cache. When Sally visits the page, she sees exactly the same content as Linus, Charlie, and Lucy do when they visit. PRO: Very little storage space is required.ĬON: There’s no opportunity for personalization – everyone gets the exact same page.Īny page that has no personalized content whatsoever is a good candidate for public cache.Ī blog archive page, for instance, could work, if it has no Admin Bar at the top, and there are no areas on the page that say “Welcome, Sally” or anything of that kind. All four visitors to your site’s page are shown that exact same piece of paper. This piece of paper represents the page of your site as stored in public cache. Public Cacheįor the sake of simplicity, let’s say that you have a site with just one page on it, and that your site has four visitors. (ESI = Edge Side Includes, which can essentially result in a public/private hybrid.) Today we’re going to visualize these three types of caching, and help you to figure out which one is best for your particular application. LiteSpeed Cache can store pages in a public cache, in private caches, and via ESI. If you are using a newer version of the plugin, some details may have changed. Today’s Topic: When to Use Public Cache, Private Cache, or ESIĭisclaimer: The information contained in this post is accurate for LSCWP v1.6.6. Welcome to another installment of WordPress Wednesday!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |