Vulnerabilities, Outdated Bootstrap, & Performance Hits
-
Hi,
First off, I really like the plugin. This message is just to direct your attention to some important issues that currently exist with RestoPress.Issues:
- [email protected] has 5 vulnerabilities (dangerous & reduces best practices from 100 to 92 in Google Lighthouse
- Something in your code prevents your RestoPress styles & scripts from being dequeued for non RestoPress pages. (can’t be done manually & can’t be done using plugins like Asset Clean Up Pro.
- The way you have implemented your “data-item-quantity” button as uncrawlable reduces SEO of pages from 100 to 93.
- Google Lighthouse Performance drops from 94 to 85 just due to RestoPress (wouldn’t be a problem if your plugin would allow dequeuing of files on pages that it don’t use RestoPress.
Screen captures Before & After:
- Non RestoPress Page with RestoPress styles & scripts Loaded:
- Non RestoPress Page without RestoPress styles & scripts Loaded:
- Best Practices Hit due to outdated [email protected] file:
https://imgur.com/a/Qljt7jQ - Best Practices without RestoPress outdated Bootstrap:
https://imgur.com/a/HjdPckV - SEO Hit due to uncrawlable ‘data-item-quantity’ link:
https://imgur.com/a/Y4h6RGR - SEO without RestoPress’s uncrawlable link:
https://imgur.com/a/oyus1d5 - Wave.webaim.org accessibility 2 errors with RestoPress:
https://imgur.com/a/J0tCYSO - Wave.webaim.org accessibility 0 errors without RestoPress:
https://imgur.com/a/8m7pkeQ - Wave.webaim.org accessibility Error #1:
https://imgur.com/a/uYq6YtQ - ave.webaim.org accessibility Error #2:
https://imgur.com/a/y3ov7kv
Each of these negative impacts on Performance & Accessibility are felt on every page that RestoPress scripts & styles are loaded on. This is why it would be super beneficial to allow for RestoPress to be dequeued except for on pages where it is needed (this is the fast fix and should be allowable by all plugins – I think it’s just due to the way in which RestoPress enqueues it’s files.)
The second task item and equally necessary yet more labor intensive is to address all of these little ‘bugs’ in the plugin source code.
Can we ask that these things be addressed?
Thank you.
The topic ‘Vulnerabilities, Outdated Bootstrap, & Performance Hits’ is closed to new replies.
