Critical css breaking site

Well, you wrote you created a manual rule earlier, if you click the “edit” button next to it you can change the critical CSS and changing paths as I described there _could_ be what is needed to have your server (or rather, the web application firewall) behave.

@optimizingmatters Anything on this?

@karkidennis I’m actually waiting on you to test if editing a rule to remove the “one directory up”-indicators /.. fixes anything? ??

@optimizingmatters Actually that was not the issue If I add manual CSS it is working whatever the directory link is. The issue is occurring when I switched on the critical CSS and there is no critical CSS while crawling. The pages which have no critical CSS crawled is not displaying. Even If I put random CSS in manual edit the page is working. I think you got it now ??

well normally if no matching rule exists, all CSS is inlined by default. if you prefer not to have all CSS inlined (can get big) you can create a “default” rule then that will be used instead, so maybe try that?

I also having similar issues. Plugin generating only one criticalcss file as is_front_page. No other css file are listed.