Irrelevant URLs in CCSS queue




Wordpress LScache Plugin: Irrelevant URLs in CCSS queue

Last Updated on: Wed, 15 Apr 2026 00:00:02
Hello, I see the unused links that are not on my site in the CCSS list and their number is very high. CCSS is not generated for my originally existing pages as these are not complete. The same goes for UCSS. There, I see pages that dont actually exist on my site, waiting in line. How can I solve this problem. Ive added it to the exclusion list for UCSS, but I cant for CCSS. Can you help me solve this problem? I have also attached screenshots to the report. Report number: DFAORTXQ Hi, if a page doesnt really existed in your site , but someone accessed such URL , it will trigger into the queue but if it ends up in 404 , then it will drop also please check how many files there is in your /wp-content/litespeed/ccss directory The folder you mentioned is empty because I purged them all and turned off guest optimization. As you can see from the screenshots, who can access these urls? So unreasonable. There is no one other than me on the site for now. Unfortunately, they do not give 404 because they redirect to the /wishlist page. https://prnt.sc/26bc1xb Other than that, I think something went wrong. My site is faster without LSCache, despite the settings I have enabled using many sources on the internet and doing hundreds of tests. I guess Im doing something wrong. My website is hosted on Amazon. Its my first time using LiteSpeed, I had such high hopes, can you please help me? What am I doing wrong? Is my site really slow from your point of view? Also, Instant Click doesnt work. When I activate it, my site slows down even more. I submitted a new report: COZNHYMF Thank you so much. from the URL , it looks like the URI when someone manipulates the wishlist , by add or remove something they are some options may slow down the loading when cache is miss for example , you have enabled add missing size , this option will run getimagesize() to all images in page , this action could be slow if your disk IO is not great so is webp replacement , it will check over disk to see if webp version exists or not object cache could also be a case where PHP needs to store the object, and if you dont have redis/memcached set up correctly , it may wait until times out , which makes thing even slower its just not exactly a good practice to just enable a lot of options without knowing what it does or how it will affect the site.



LiteCache Rush: Speed comes from using less, not from doing it faster



Reference