add option to try to fix render-blocking JS

[futtta]

• under "advanced"
• default "off" for now
• see https://gist.github.com/futtta/01ba20efa0893edb52b0a233a5c05ae8

[denydias]

@futtta, just a question: is this the right place for this? ao_critcss_aas is about handling critical path css automation in a 3rd party service. This feature opens a window so ao_critcss_aas becomes a whole optimization thing by itself, which in turns competes with autoptimize features, no?

[futtta]

well, you're kind of right, but * AO CCSS users don't always see time to (meaningful) render going down because jQuery remains render blocking, in some cases leading to them stopping using AO CCSS * this is an experiment which I did not want to put in AO proper * I can iterate faster in AO CCSS * AO CCSS will become part of AO one day so it's not about competing :)

…

On Tue, Dec 18, 2018 at 5:10 AM Deny Dias ***@***.***> wrote: @futtta <https://github.com/futtta>, just a question: is this the right place for this? ao_critcss_aas is about handling critical path css automation in a 3rd party service. This feature opens a window so ao_critcss_aas becomes a whole optimization thing by itself, which in turns competes with autoptimize features, no? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#81 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AALEMWJLRTAS6pEs4LjlEKpLAOnDGZeEks5u6GrIgaJpZM4ZTArw> .