The month has changed and LiteSpeed Cache page optimization usage has been restored.Since the amount of usage will soon be used up, we have set it to apply only to the top page of the blog.

Coexistence of LiteSpeed Cache and Cloudflare CDN

We have started using Cloudflare CDN.

We are also reviewing the LiteSpeed Cache plugin settings accordingly.

Among the page optimizations, we are planning to check CSS and JavaScript settings from scratch.

Narrow down the URI to generate UCSS

I am sure that many times you will do a full UCSS erasure, so you will be wasting page optimization usage if you leave it as it is.

Therefore, we decided to narrow down the URI to generate UCSS.

Pages not to be generated are listed in the “UCSS URI Excludes” section.

First, we excluded fixed pages, pages in other languages, each article page, and category and tag pages so that only the top of the blog for Japanese pages would be generated.Besides that, we also excluded pages that were listed to generate CSS.

I don’t think this will generate anything but the top of the blog, so the strategy is to gradually increase the number of targets after checking the PC and smartphone pages for display disruptions.

JavaScript does not malfunction

JavaScript is optimized without consuming page optimization usage.There are no malfunctions in the current state.

Lazy loading of JS has been changed from “Delayed” to “Deffered” so that it is less likely to malfunction.

The conditions are designed to be less prone to malfunction in anticipation of being cached by the Cloudflare CDN.

Musubi

We have started using Cloudflare CDN and will review the LiteSpeed Cache plugin settings.As a preliminary step, we have configured it so that it does not generate UCSS except for the blog top.

Soon today’s usage will be back; VPI (View Port Image) optimization will be finished today and then I will adjust UCSS.