you do have a huge amount of inline CSS, is this an option somewhere? if you have less inline CSS, unchecking “also aggregate inline CSS” will not be frowned upon by GPSI?
#execphp-xx is ok I know these id, they are fixed.
so are the same execphp-xx’s used in every page? and does it always have the same CSS applied?
I test again without preload this time I will see tomorrow waking up
well, it will be a lot smaller, but ultimately it will grow and grow as well. preload as such is not the reason, it only makes the problem visible faster.
Unfortunately the file number has increased overnight, up to about 1000
Yes the same execphp-xx are used every page, it is the ID of my widgets.
and it is the same css for all execphp
I use Avada as a template that uses online Css for each “block”
If I disable this option I lose a big profit in the Google Pagespeed
If I disable this option I lose a big profit in the Google Pagespeed
well, in general GPSI does not like it when there’s a lot of CSS inlined (it will complain about round-trip times to render the content). moreover that option is of no importance when using AO CSS optimization if you have “aggregate inline CSS” active anyhow.
so if I were you I would;
* make sure all original css that _can_ be linked instead of inlined is moved out of your HTML
* disable AO’s “also aggregate inline CSS” (to fix your cache-size problem)
* optionally (once all works) experiment with “inline & defer CSS”
frank
Thank you for trying to help me 🙂
I just tested but that does not solve the problem.
I also just compare the css files and there is a css file for the mobile and another for the desktop. I think for the plugin, it creates indefinitely files because it thinks the source code changes?
I think for the plugin, it creates indefinitely files because it thinks the source code changes?
almost there, this is correct though;
the plugin creates indefinitely files because the source code changes
-> if the (aggregated) source-code is identical, it does not create a new cached file. if the source-code is different (even just a space or comment), it does create a new file.
frank
Hello Franck 🙂
I hope you are well.
I found the solution to the problem. In fact I use the Avada theme which dynamically generates a bit of css.
In theme options, there is a page : Dynamic CSS & JS
CSS Compiling method
Select “File” mode to compile the dynamic CSS to files (a separate file will be created for each of your pages & posts inside of the uploads/fusion-styles folder), “Database” mode to cache the CSS in your database, or select “Disabled” to disable.
This option was disabled. I activated “file” and then everything came back in order.
A big thank you for your help and for this super plugin !
that’s interesting information @espacemusculation, thanks for the feedback, sure others will find this useful as well!
bon weekend (beaucoup de pluie ici, mais soit 😉 )!
frank
with pleasure
thanks again
(le temps n’est pas super ici non plus 😉 )
Jimmy
