Title: Avoid serving legacy JavaScript code in modern browsers
Last modified: June 5, 2025

---

# Avoid serving legacy JavaScript code in modern browsers

 *  Resolved [Luca Spinelli](https://wordpress.org/support/users/lucaspinelli94/)
 * (@lucaspinelli94)
 * [1 year ago](https://wordpress.org/support/topic/avoid-serving-legacy-javascript-code-in-modern-browsers/)
 * Is it possible to fix this problem reported by Google?
 * Google Insights => Avoid serving legacy JavaScript code in modern browsers
 * Here more infos:
 * […js/dark-mode.js?ver=174…](https://consulente-finanziario.org/wp-content/cache/min/1/wp-content/plugins/wp-dark-mode/assets/js/dark-mode.js?ver=1749127080)
 * (consulente-finanziario.org)
 * 0,7 KiB
 * […js/dark-mode.js?ver=174…:1:1241](https://consulente-finanziario.org/wp-content/cache/min/1/wp-content/plugins/wp-dark-mode/assets/js/dark-mode.js?ver=1749127080)
 * (consulente-finanziario.org)@babel/plugin-transform-classes
 * […js/dark-mode.js?ver=174…:4:2374](https://consulente-finanziario.org/wp-content/cache/min/1/wp-content/plugins/wp-dark-mode/assets/js/dark-mode.js?ver=1749127080)
 * (consulente-finanziario.org)@babel/plugin-transform-regenerator
 * […js/dark-mode.js?ver=174…:2:307](https://consulente-finanziario.org/wp-content/cache/min/1/wp-content/plugins/wp-dark-mode/assets/js/dark-mode.js?ver=1749127080)
 * (consulente-finanziario.org)@babel/plugin-transform-spread

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

 *  Plugin Support [Md. Ibrahim Khalil](https://wordpress.org/support/users/mdibrahimk48/)
 * (@mdibrahimk48)
 * [11 months, 4 weeks ago](https://wordpress.org/support/topic/avoid-serving-legacy-javascript-code-in-modern-browsers/#post-18513198)
 * We are looking at this issue.
   We will back to you soon!
 *  Plugin Support [Md. Ibrahim Khalil](https://wordpress.org/support/users/mdibrahimk48/)
 * (@mdibrahimk48)
 * [11 months, 3 weeks ago](https://wordpress.org/support/topic/avoid-serving-legacy-javascript-code-in-modern-browsers/#post-18517189)
 * We didn’t find any specific issue on our end.
 * Using legacy code is acceptable, especially when maintaining backward compatibility
   is necessary. Since not all of our users operate in the same environment. The
   issue you mentioned appears to be triggered by third-party plugins, even within
   build assets, which are outside our control.
 * **Addressing compatibility with every possible external asset would lead to over-
   engineering and isn’t feasible in practice.**
 * We always aim for a balance between stability and flexibility. Please let us 
   know if there’s anything else we can assist you with.

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

The topic ‘Avoid serving legacy JavaScript code in modern browsers’ is closed to
new replies.

 * ![](https://ps.w.org/wp-dark-mode/assets/icon-256x256.gif?rev=2872214)
 * [WP Dark Mode - Improve Accessibility with AI Powered Dark Theme](https://wordpress.org/plugins/wp-dark-mode/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-dark-mode/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-dark-mode/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-dark-mode/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-dark-mode/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-dark-mode/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Md. Ibrahim Khalil](https://wordpress.org/support/users/mdibrahimk48/)
 * Last activity: [11 months, 3 weeks ago](https://wordpress.org/support/topic/avoid-serving-legacy-javascript-code-in-modern-browsers/#post-18517189)
 * Status: resolved