Title: Dequeue Unnecessary Scripts Option
Last modified: June 26, 2024

---

# Dequeue Unnecessary Scripts Option

 *  Resolved [ofmarconi](https://wordpress.org/support/users/ofmarconi/)
 * (@ofmarconi)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/)
 * I hope this message finds you well. I am reaching out to suggest an enhancement
   for the Admin and Site Enhancements (ASE) plugin that could significantly streamline
   site performance for users not needing backward compatibility with older browsers
   like Internet Explorer (IE).
 * As the web continues to evolve, modern technologies are increasingly embraced
   by developers and users alike. In this context, scripts like the IE Polyfill,
   which ensures compatibility with outdated browsers, become less relevant for 
   many users. These scripts not only consume resources but also potentially slow
   down the site for a majority who use modern browsers.
 * Given this, it would be extremely beneficial to include an option within the 
   ASE plugin to selectively dequeue such scripts. This feature would empower users
   to optimize their site’s performance by removing unnecessary load, thus enhancing
   the overall user experience for their target audience, who are unlikely to use
   IE.
 * Implementing this feature could position ASE as a forward-thinking tool that 
   adapts to the changing needs and practices in web development, aligning with 
   the preferences of developers looking to optimize for the latest browsers.
 * Thank you for considering this suggestion. I believe many in the ASE user community
   would appreciate and benefit from this enhancement.
 * Best regards,
 * _And we still have this news:[https://thehackernews.com/2024/06/over-110000-websites-affected-by.html](https://thehackernews.com/2024/06/over-110000-websites-affected-by.html)

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

 *  Plugin Author [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/#post-17852903)
 * [@ofmarconi](https://wordpress.org/support/users/ofmarconi/) thanks for the suggestion.
   [The attack](https://sansec.io/research/polyfill-supply-chain-attack) happened
   on sites that load the polyfill JS from cdn.pollyfill.io. The latest owner of
   that script / site injected malware. In WordPress, the polyfill JS is included
   in core at /wp-includes/js/dist/vendor/wp-polyfill.js (and other polyfill JS 
   in this folder). So, WordPress sites were safe. CMIIW.
 * As for removing it, I would follow what WP core does for now, as it seems needed
   for Gutenberg / the block editor.
 *  Plugin Author [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/#post-17856343)
 * [@ofmarconi](https://wordpress.org/support/users/ofmarconi/) this is from the
   WP 6.6 field guide:
   [https://make.wordpress.org/core/2024/06/25/miscellaneous-developer-changes-in-wordpress-6-6/#obsolete-polyfills-dependencies-have-been-removed](https://make.wordpress.org/core/2024/06/25/miscellaneous-developer-changes-in-wordpress-6-6/#obsolete-polyfills-dependencies-have-been-removed)
 * **Obsolete polyfills dependencies have been removedIn [[57981](https://core.trac.wordpress.org/changeset/57981)],
   now obsolete polyfills such as wp-polyfill, wp-polyfill-inert and regenerator-
   runtime were removed from the react script dependency in WordPress, as they are
   no longer needed in modern browsers supported by WordPress. Developers relying
   on wp-polyfill need to manually add it as a dependency to their scripts.
 *  Thread Starter [ofmarconi](https://wordpress.org/support/users/ofmarconi/)
 * (@ofmarconi)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/#post-17856375)
 * Thanks for sharing!
 * Has this changed in your WP?
   Because mine are on the latest version and still
   continue to call this script.
 *     ```wp-block-code
       <script src="/wp-includes/js/dist/vendor/wp-polyfill-inert.min.js?ver=3.1.2" id="wp-polyfill-inert-js"></script><script src="/wp-includes/js/dist/vendor/regenerator-runtime.min.js?ver=0.14.0" id="regenerator-runtime-js"></script><script src="/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=3.15.0" id="wp-polyfill-js"></script>
       ```
   
 *  Plugin Author [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/#post-17856383)
 * That’s for WP 6.6 as stated in my previous reply.
 *  Thread Starter [ofmarconi](https://wordpress.org/support/users/ofmarconi/)
 * (@ofmarconi)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/#post-17856389)
 * Sorry, I thought we were already at 6.6, what great news!
   (or not, let’s see 
   how many plugins will break, starting with Elementor)
 * Thx so much per support us

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

The topic ‘Dequeue Unnecessary Scripts Option’ is closed to new replies.

 * ![](https://ps.w.org/admin-site-enhancements/assets/icon-256x256.png?rev=3099794)
 * [Admin and Site Enhancements (ASE)](https://wordpress.org/plugins/admin-site-enhancements/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/admin-site-enhancements/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/admin-site-enhancements/)
 * [Active Topics](https://wordpress.org/support/plugin/admin-site-enhancements/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/admin-site-enhancements/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/admin-site-enhancements/reviews/)

## Tags

 * [polyfill](https://wordpress.org/support/topic-tag/polyfill/)

 * 5 replies
 * 2 participants
 * Last reply from: [ofmarconi](https://wordpress.org/support/users/ofmarconi/)
 * Last activity: [1 year, 11 months ago](https://wordpress.org/support/topic/dequeue-unnecessary-scripts-option/#post-17856389)
 * Status: resolved