Why Enqueue JQuery on the Frontend for a Plugin Like This?

Resolved David Cameron Law
(@seo-dave)

4 years, 2 months ago

I was happily using your plugin until an hour ago when after the latest update my Google Lighthouse results were impacted by jQuery loading on the frontend.

I regularly check Lighthouse, so adding jQuery to the frontend is new for this plugin, I’m curious why you’ve added jQuery at the last update?

I don’t use plugins which add jQuery, it’s bloated and is pretty much vulnerable most of the time (even the latest release will end up being vulnerable). Run any site using this plugin through Lighthouse and it will report security vulnerabilities due to jQuery. The WordPress core version of jQuery is out of date and reported as vulnerable.

For example https://googlechrome.github.io/lighthouse/viewer/?psiurl=http%3A%2F%2Fmagazine3.company%2F&strategy=mobile&category=performance&category=accessibility&category=best-practices&category=seo&category=pwa&utm_source=lh-chrome-ext has jQuery and it has 2 vulnerabilities. That version of jQuery is from May 2016 https://snyk.io/vuln/npm:jquery?lh=1.12.4&utm_source=lighthouse&utm_medium=ref&utm_campaign=audit. There’s been 11 updates, but WordPress can’t update fully (I believe they did a partial custom update May 2019) due to backwards compatibility with old themes/plugins.

If the plugin doesn’t NEED jQuery on the frontend to function you should remove it.

I’ve had to go back to the previous plugin I was using, no jQuery, but I get a console error. Your plugin gave no errors.

Viewing 6 replies - 1 through 6 (of 6 total)

Plugin Author Magazine3
(@magazine3)

4 years, 2 months ago

We checked your issue. This is a small bug from our side. We have created a ticket in GitHub about this issue. It will be fixing in our next updates.
Reference: https://github.com/ahmedkaludi/pwa-for-wp/issues/330

Thread Starter David Cameron Law
(@seo-dave)

4 years, 2 months ago

I’ll look out for the update.

I’ve marked as resolved based on you plan to fix it.

Plugin Author Magazine3
(@magazine3)

4 years, 2 months ago

This issue is fixed in our latest version of plugin(1.7.8). Can you please update the plugin and check whether the issue is having or not.

Thread Starter David Cameron Law
(@seo-dave)

4 years, 2 months ago

Updated and tested and sadly jQuery is still loading on the front end. I’m 100% certain it’s this plugin.

When this plugin is activated and I view the minified/cached js file (created by W3 Total Cache) I get this at the top.

/*! jQuery v1.12.4 | (c) jQuery Foundation | jquery.org/license | WordPress 2019-05-16 */

When I run Google Lighthouse I see the two usual vulnerability warnings:

jQuery@1.12.4 2 Medium

when IQuery is loaded at the front end, so it’s definitely still loading it.

I’ve deactivated the plugin.

You can see the home pages Lighthouse report at https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Fseo-gold.com%2F&strategy=mobile&category=performance&category=accessibility&category=best-practices&category=seo&category=pwa&utm_source=lh-chrome-ext with your plugin disabled.

No jQuery loaded at the front end.

I’ve reactivated the alternative progressive web app plugin, but it throws out a Browser error

TypeError: Failed to update a ServiceWorker for scope ('https://seo-gold.com/') with script ('https://seo-gold.com/superpwa-sw.js'): An unknown error occurred when fetching the script.

Which I haven’t been able to fix.

Your plugin doesn’t give any errors, (and you are in active development) so if you can fix jQuery loading on the front end I’ll be a happy user again.

Thanks for trying, appreciated.

Plugin Author Magazine3
(@magazine3)

4 years, 2 months ago

Can you please update the plugin latest version(1.7.8.1) and check once whether having the same issue or not.

Thread Starter David Cameron Law
(@seo-dave)

4 years, 2 months ago

Awesome soup, you got it.

That deserves a 5 star review when I have some spare time, always good to see a plugin developer actively supporting their plugin for free users.

Your plugin is working perfectly again.

Appreciated.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Why Enqueue JQuery on the Frontend for a Plugin Like This?’ is closed to new replies.