this one;
3.2 ) another thing
excluding the premium plugin’s CSS from optimization. more info on troubleshooting & excluding in AO’s FAQ.
hope this helps,
frank
thanks and how could i find which css i must add in the exception list ?
typically you would see links to CSS files pointing to the elementor-plugin (so having elementor in the name). you can also try not aggregating inline CSS, as some pagebuilders put their CSS inline.
I was looking for the css and i can not find it . Where i could find which css is crashing my site ? The plugin has about 50-60 css files 🙁 Some advices to find the guilty css 😉
well, why not simply exclude them all by adding wp-content/plugins/elementor/assets to the comma-separated CSS optimization exclusion list? 🙂
Morning ! Thank you . Right now i have a different problem . I have excluded the plugin css . I mean if i am logged in as admin the page looks fine . If i log out the page is a disaster . I have cleaned the cache , cloudflare , and i cache of different devices . Any ideas of what could be ? thanks
and if you remove the elementor exclusion all is back to normal, or not?
Solved ! it seems that , check this box to optimize the css included into the html causes all the problems. I have deactivated and now it is working fine . I have a question about you . What that option makes i mean . RIght now ( with unchecked box ) my website would be slower ? more php use ? any another side effect ? thanks
What that option makes i mean . RIght now ( with unchecked box ) my website would be slower ? more php use ? any another side effect ? thanks
aggregating inline CSS (or not) has no significant performance impact frosinone, you’re good to go that way 🙂
Great for your time and great support ! By the way , i am curious . Could be possible to add this option somehow over determined pages ? I mean my website would have lot of pages so ¨desactivating¨ this option in order to use this plugin over 2-3 pages from 300 would cause more negative impact that good impact . Could be possible to activate it only on pages using their url,id, or so ?
I mean 297 would lost this option, in order to make it work over 3 pages . which is your opinion about that ? thanks once again 🙂
Could be possible to activate it only on pages using their url,id, or so ?
are you referring to the “also aggregate inline CSS”-option tehre @frosinone?
i mean the 3rd option of CSS area .
inline the css present in the html .
well, as it doesn’t have any significant impact on the performance, I would leave as is actually if I were you. But if you’re into PHP, you could hook into Autoptimize’s API (the autoptimize_css_include_inline filter) to dynamically enable/ disable inline CSS aggregation 🙂
thank you ! You are the very best , hopefully the next version that is now in beta would even improve it 🙂 GREAT PLUGIN !
BTW , is it better for everyone to expalain it a little bit into the beta topic , it would be better to understand it ( for the normal people like me ) to see what is new ,etc.
it features a new version of the CSS minifier which is _a lot_ faster and more reliable
it allows users to minify CSS/ JS without aggregating it
excluded CSS/ JS now gets minified
it “listens” to page caches getting purge to clear its own cache as well
-
This reply was modified 8 years ago by
frosinone.
well, for normal people the explanation is; “it is even better” 😉
no seriously;
* css minifier; css minification can in some cases be slow in the current version, it will be significantly faster in 2.4
* minify without aggregating; this has less chance of stuff breaking (e.g. your elementor issue), but will in some cases be less effective (as nothing is deferred)
* excluded css/ js; if you exclude now, the files are left entirely un-optimized, in 2.4 AO will minify the non-aggregated CSS/ JS
* page caches; too technical, but the goal is for AO to purge it’s cache when appropriate 🙂
