Hi Alex,
in response to this threat:
https://siteorigin.com/thread/create-many-css-files-inside-wp-content-uploads-siteorigin-widgets/
There is a great issue when using Autoptimize or other minifiers:
Autoptimize DOES minify the additional css files in /wp-content/uploads/siteorigin-widgets, but this results in a own LARGE css file for each webpage which has a separate css file stored in /wp-content/uploads/siteorigin-widgets.
So in the end I only have the choice between (in my case with Autoptimize):
a) one minified css request per page, but on each page another combined css file has to be loaded and it is in most cases as large as 300-600kB, depends on site theme. This does break any idea of minifying.
b) when excluding /wp-content/uploads/siteorigin-widgets in Autoptimize css settings, then, depending on the amount of SO css files per page in /wp-content/uploads/siteorigin-widgets, I get x additional requests per page, e.g. 10 instead of 1.
Solution would be: All styles in /wp-content/uploads/siteorigin-widgets should be put inline on the corresponding page. I do not see any advantage in making one or even SEVERAL css files for each page, which have to be loaded – in particular as these css files are only some 100 bytes in size.
Could you implement a switch to set, if separate css files are generated or inline css is used? Would help a lot in optimizing. Thanks!
Hi Soowide,
I’ve marked this thread as a feature request. We often look through these threads to get ideas for what to add in our future updates. Hopefully, we’ll be able to add this in a future update.
Thank you. I think this is very important, as it does not make any sense to add several additional files (and server-requests) per page (!) to a website, which only slows down loading, rendering and stresses the webservers.
Thanks.