FYI, critical css is disabled on the site now since it creates an ugly flash if enabled.
Plugin Support
qtwrk
(@qtwrk)
Hi,
Please check in your HTML source , see if CCSS rule is there ?
if not , please enable advanced debug log
then purge all , purge CSS, access your page.
after that check the log, it should state why CCSS didn’t generate.
Best regards,
-
This reply was modified 6 years, 2 months ago by
qtwrk.
The css is generated. Please read I write: “The css is generated as it should and I can see the css in the litespeed-optm-css-rules tag”
That is not the problem, the problem is that the page renders very ugly with the generated css. See the screenshot for how it looks when rendered with the generated critical css.
Plugin Support
qtwrk
(@qtwrk)
Hi,
Could you please try “Separate CCSS Cache URIs” ? just try on your home page or the page where you see the error, then purge all , purge CCSS (purge all doesn’t purge CCSS, you need to purge it separately)
then check again ?
I have seen in some rare case that one page’s CCSS overlapped other page when they are same type of post but built with different CSS.
Best regards,
Interestingly that seems to fix it for some pages but not others. The top menu is the same on all pages so that should be the same right?
An advice on how to debug this further?
Plugin Support
qtwrk
(@qtwrk)
Hi,
Please try “Separate CCSS Cache Post Types” option.
Best regards,