- A performance enthusiast and developer named Gijo Varghese has found some evidence of WP-Optimize cheating in benchmarks.
- WP-Optimize lead developer David Anderson has stated that the code in question does not belong to them and will be removed if it is not serving any legitimate purpose.
Does not reflect real user experience
🚨 How "WP Optimize" is cheating PageSpeed and other testing tools 👇
No JS = high scores. But for real users, these JS files are loaded! pic.twitter.com/uuOiAOgvoo
— Gijo Varghese (@GijoVarghese_) August 26, 2022
“The code in question is not ours”
The lead developer of WP-Optimize, David Anderson, has brought WPTavern an interesting explanation. According to Anderson, the codes that disable JS files when it detects benchmarking tools go back to 2.5 years ago, when the company was thinking about combining forces with the Fast Velocity Minify plugin.
In the decision period, WP-Optimize developers have forked and adapted Fast Velocity Minify. In the end, they could not agree. This is when Anderson thinks the code is mixed in WP-Optimize codes. Those codes were not touched for 2.5 years and developers were not aware of those lines.
« The code in question is not dangerous, a virus, an infection, useful to hackers, or anything of that kind. The allegation is that its only purpose in existing is effectively to cheat on speed tests. Such code, if so, does not belong in WP Optimize and we will remove it with a new release. Our products’ integrity, and our customers’ trust, are essential for us (and deliberately putting things in open source code that compromises that is, frankly, a stupid thing to do). »