WP Tavern › Forums › Create Topic
Raul Hi there, I am the author of the FVM plugin referred on the article here. A few years ago, developers of the WP Optimize plugin decided to copy portions of FVM to their code (no problem for me as the plugin is GPL) and I can confirm that equivalent code was part of our plugin. However, the purpose of such code on FVM was completely different than the one on WP Optimize and furthermore it required for the users to manually enable this option via wp-admin (it was disabled by default). The purpose of that code was to selectively test the impact of new scripts or plugins in performance, and help developers decide if they should refactor, remove or replace heavy plugins or scripts. This existed on FVM to answer questions like these: “I have a production site and my performance is low. What would be the performance if this plugin was simply not here, but without actually removing it from the site for regular users yet?” “What would the performance be if I could defer all scripts, or specific scripts that are not currently compatible with defer, before actually doing that change for everyone?” An official explanation regarding it’s use on FVM exists here, https://wordpress.org/support/topic/why-are-some-scripts-not-loaded-for-speed-testing-sites/ I suppose that the developers hired by WP Optimize did not understand what this was doing on FVM or under what settings, or perhaps, they may have felt tempted to use it as a hack. We should also carefully remember that at that time, there were still no web vitals metrics publicly available, so using something like this would have yield better “measurable” results, thus offering a product advantage. Whatever was the case, WP Optimize and FVM are unrelated, so their choice to copy and refactor that code to do what it does is theirs alone.
Raul
Hi there,
I am the author of the FVM plugin referred on the article here.
A few years ago, developers of the WP Optimize plugin decided to copy portions of FVM to their code (no problem for me as the plugin is GPL) and I can confirm that equivalent code was part of our plugin.
However, the purpose of such code on FVM was completely different than the one on WP Optimize and furthermore it required for the users to manually enable this option via wp-admin (it was disabled by default).
The purpose of that code was to selectively test the impact of new scripts or plugins in performance, and help developers decide if they should refactor, remove or replace heavy plugins or scripts.
This existed on FVM to answer questions like these: “I have a production site and my performance is low. What would be the performance if this plugin was simply not here, but without actually removing it from the site for regular users yet?” “What would the performance be if I could defer all scripts, or specific scripts that are not currently compatible with defer, before actually doing that change for everyone?”
An official explanation regarding it’s use on FVM exists here, https://wordpress.org/support/topic/why-are-some-scripts-not-loaded-for-speed-testing-sites/
I suppose that the developers hired by WP Optimize did not understand what this was doing on FVM or under what settings, or perhaps, they may have felt tempted to use it as a hack.
We should also carefully remember that at that time, there were still no web vitals metrics publicly available, so using something like this would have yield better “measurable” results, thus offering a product advantage.
Whatever was the case, WP Optimize and FVM are unrelated, so their choice to copy and refactor that code to do what it does is theirs alone.
Name *
Email *
Website:
Topic Title (Maximum Length: 80):
Forum: — No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Email Address
Submit
Enter the destination URL
Or link to existing content
