you *could* leave it like that, that warning is kind of arbitrary at 0.5gb, but there are other reasons why you should look into why this is happening @gwkopy (as in; finding out which JS or CSS is busting the cache and excluding that from optimization)
hope this clarifies,
frank
Thread Starter
gwkopy
(@gwkopy)
So, what would be the best method to identify the defiant script? 🙂
well, first of all compare the number of files in wp-content/cache/autoptimize/css
and wp-content/cache/autoptimize/js
. the one with most files will be the you’ll have to focus on.
next take two similar pages (or posts) and in HTML source check if they have a different AO JS-file (or CSS). If so download the contents of the files, un-minify (using e.g. http://jsbeautifier.org/) and then use e.g. notepad++ to compare the un-minified code.
(just to make sure; you do have “also aggregate inline JS” and -“CSS” off already? if not try that first, it’s the easier solution 🙂
frank
Thread Starter
gwkopy
(@gwkopy)
CSS was off but “also aggregate inline JS” was still on.
Thanks. Will see how this works.