CSS compiling; only thing to keep in mind is that CSS that is unique to a page ideally is not aggregated in AO (as that would result in a different autoptimized CSS-file for each page). for this reason AO excludes wp-content/uploads from CSS optimization by default.
regarding “Load Media-Queries Files Asynchronously”; interesting option, why not give it a go and see what happens? 🙂
Just thought i’d mention, Load Media-Queries Files Asynchronously has been available since mid 2018 and CSS Compiling method since about 2015!
In my experience if your using other caching and compiling methods then these options dont need to be used.
Thread Starter
Henry
(@henrybaum)
OK, thanks – new to me, at least! They have this in their most recent changelog, which threw me.
“Fusion Core’s minified styles are now also added to compiled styles if database mode is chosen”
Would “Database” mode be a problem?
Would “Database” mode be a problem?
I suppose that this means the fusion CSS is inlined in the HTML in that case, which could inflate the cache size, so you might want to untick the “also aggregate inline CSS”-option.
Thread Starter
Henry
(@henrybaum)
This may have turned into a support request.
I’ve completely disabled all of Avada’s compiling options and have everything handled by AO. It seems enabling CSS compiling just adds another request for the same CSS – I think…
However, when I update Avada now, I have to clear the AO cache or formatting is messed up for the site.
I’d rather limit the number of requests, if possible. Is this a problem with AO or Avada?
I’d rather limit the number of requests, if possible.
not sure I understand what you mean, can you elaborate?
Thread Starter
Henry
(@henrybaum)
In pingdom it says that it’s loading the Avada upload/css file along with the AO cache, which takes extra time that I’d rather cut out. Isn’t it just loading the CSS that AO already has saved?
by default AO excludes CSS in wp-content/uploads to avoid cache issues. you can try removing that exclusion and keep an eye on your cache size maybe (do take into account that a fast growing cache is a tell of bigger issues).
