use of standards WP hooks rather than output buffering about autoptimize HOT 5 CLOSED

for the simple reason that using the OB every little bit if JS/ CSS will be captured, extracted and optimized, even if it was not enqueued properly (which happens all too often) :-)

from autoptimize.

Thank you for making the initial assumption clear (modules/themes authors do not write good code).
Don't you think that the far cleaner WP-integration of autoptimize in case of processing only properly declared assets would be worth the change?
Do you know of any module similar to autoptimze (in quality) that applies in a less intrusive way (more WP-compliant)?

Personally, I think that there should be no intent in processing assets of "bad" module/themes that would rather need fixing, but that's just my opinion.

from autoptimize.

Do you know of any module similar to autoptimze (in quality) that applies in a less intrusive way (more WP-compliant)?

bwp-minify maybe?

from autoptimize.

For properly enqueued assets minification, you should consider https://github.com/kasparsd/minit + various https://github.com/kasparsd/minit/wiki/Minit-Extensions

from autoptimize.

closing time ;-)

from autoptimize.