Google Lighthouse 3 Warnings after update

We checked your issue. In your website we didn’t find any service workers.
Screenshot: https://prnt.sc/r3wq9w
Can you please tell me are you using any cache plugins? If you are using any cache plugins,can you please clear the clear the plugin cache.

Stop automatically working after latest update. I never use any cache plugin.

Screenshot> https://prnt.sc/r48a8c

• This reply was modified 4 years, 9 months ago by mariushosting.

I have never used jQuery on my website and have never had a problem with this plugin in the past. I think the problem is related to this “Remove jQuery dependency from Front-end #330”
I think this plugin now have a dependency on jQuery because if I activate again jQuery on my WordPress blog PWA plugin start magically to work again.

If this can help you I have this code on my functions.php

/** * deregister jQuery home theme */
add_action('wp_enqueue_scripts', 'no_more_jquery');
function no_more_jquery(){
    wp_deregister_script('jquery');
}

/** * deregister jQuery */
function my_init() {
    if (!is_admin()) {
        wp_deregister_script('jquery');
        wp_register_script('jquery', false);
    }
}
add_action('init', 'my_init');

So, If i remove this code from my functions.php, PWA plugin start to work again.
The error appears with the latest update 1.7.8
No problem with version 1.7.7
So the problem is related to this: “Remove jQuery dependency from Front-end #330”

We checked your issue. On your website you are using Autoptimize plugin. Can you please clear the cache of that plugin. And also update the latest version of our plugin.

Screenshot: https://prnt.sc/r4jjy5

• This reply was modified 4 years, 9 months ago by Magazine3.

pro-tip; you can disable Autoptimize on a per-request basis by adding ?ao_noptimize=1 to the URL.

if the problem is not there at that point, some autoptimize (re-)configuration might be needed to fix this. there are troubleshooting tips and info on how to exclude in the AO FAQ.

hope this helps debugging,
frank (ao dev)

@magazine3 @optimizingmatters
the problem was automatically solved after I have installed version 1.7.8.1
Thanks for support!