The LiteSpeed Cache plugin’s page optimization usage is at 93% again this month. We will optimize older articles next month so that newer articles will not be unable to optimize their pages.

LiteSpeed Cache page just barely optimized

As expected, the LiteSpeed Cache plugin is just barely optimizing the page. Usage has reached 93%.121 remaining.

With daily updates and three languages, the original usage is just barely enough. Generating UCSS for past articles cannot be done all at once, so we will proceed gradually.

We were able to generate UCSS for March until after February 11, so how far can we go in April? We will keep an eye on the situation and gradually expand the scope of UCSS.

How to suppress UCSS generation in LiteSpeed Cache

The method we have been trying since this month to suppress pages that generate UCSS is working well. List the pages that do not generate UCSS in the “UCSS URI Excludes” section.

The Chrome Developer Tools shows “bypassed by setting” as follows.

We will maintain this status and gradually generate UCSS in past articles.

For sites with many published articles, it would be a good idea to prioritize the generation of UCSS from the most recent articles and gradually apply it to older articles.

Musubi

The page optimization usage of the LiteSpeed Cache plugin is now just about at the end of the day.

If you apply the LiteSpeed Cache plugin to a site that publishes some articles, the UCSS generation will quickly reach the page optimization usage limit.

We believe that a better approach would be to narrow down the scope of UCSS to generate only recent articles, and then gradually expand the scope of application.