Table of contents of the article:
Varghese confirmed that he was testing the free version of WP-Optimize, which is used on over a million WordPress sites. UpdraftPlus acquired WP-Optimize in 2016 and states that the instrument "has everything you need to keep your website fast and fully optimized". A commercial version is also promoted via the free plugin hosted on WordPress.org.
"Tell me, UpdraftPlus, how should I continue to trust your business with my customer backups when you use these deceptive and fraudulent practices?Said customer Adam Lowe in response to Varghese's discovery of the plug-in not loading JS for performance tools.
"Wow, all I can say is total disappointment“Said the owner and developer of the WordPress agency Brian Jackson.
This kind of alleged deception is eerily similar to a scam reported by someone who hired a performance freelancer on Upwork who artificially manipulated Google Pagespeed results. Other participants in the discussion on Twitter likened it to Volkswagen's emissions scandal, in which the automaker was found activating its emissions controls only during laboratory tests to meet EPA requirements after a breach. Vehicles on the road emitted up to 40 times more nitrogen oxides while driving, compared to how they performed in rigged lab tests.
Wp Optimize does not reflect the actual user experience
Varghese and several other participants in the conversation concluded that this is why site owners should focus on what real-world users are experiencing, rather than performance tool test scores.
Even when focusing on real user experiences, site owners often rely on tests to diagnose problems and see how they can improve a site's performance. They don't expect a plug-in to hide JS files from performance tools. Cheating on testing has eroded WP-Optimize's credibility.
"Oh. If true, this is as shortsighted as it is unforgivable“Said Johnathon William, UpdraftPlus client. "And I wonder if I can trust their other product, UpdraftPlus, which I use to back up several customer sites".
I contacted UpdraftPlus and lead developer David Anderson said the company was unaware of the problem with the code, but reported some of the background. UpdraftPlus has been briefly in talks with the author of the Fast Velocity Minify plugin about joining forces, in which it would keep the minification module within WP-Optimize and gain more users. They ultimately failed to reach an agreement, but during that time the developers of WP-Optimize forked and adapted Fast Velocity Minify under the GPL. The developers who worked on that adaptation are no longer with the company.
“In the commit in our source repository, 2,5 years ago (January 2020), the commit was labeled 'Resolve' Add CSS and JS Minification GPL code from 'Fast Velocity Minify' - Part 6 ′,” Anderson said. “Part of a series of initial code merges that have been refactored to be cleaner and use our coding style preferences (but not change any functionality). So the apparent intention of merging those lines was to bring the refactored code back without making any changes at that stage.
“According to the commit history (ie the 'git fault' function) there have been no changes to that code since then, ie it is as imported. (WP Optimize history is also public in WordPress SVN). "
After a cursory review of the code, Anderson concluded that his team may need to review it, as they were unaware of what was added two years ago.
As I try to trace that function through the code within the plugins, the intention at first sight it appears to be that if the website visitor is a 'bot', code that is useless to bots will not be executed
“However, with that said, 1) the bot names seem to be heavily obfuscated / redacted, which is weird (why?) And 2) there are a lot of more obvious bots that aren't listed there, like the Googlebot itself. If that feature had been submitted to me for review today, I would definitely wonder why this is the case. I don't mind rereading 32 months ago, but I remember it was a long series of great patches, so it wasn't going through closely line by line. We knew we had identified FVM as a good plug-in and our main goal was to adapt it to our structure and style, and these were the things I was personally looking at as a final reviewer. "
In summary, UpdraftPlus's development team was unaware of this code until the Twitter thread was posted over the weekend.
Meanwhile, UpdraftPlus has posted a notice in the plugin's support forum to inform users that the code is currently under investigation.
To be clear and to reassure users: the code in question is not dangerous, a virus, an infection, useful for hackers or something like that, ”Anderson said. “The charge is that its only purpose in existence is actually to cheat the speed tests. That code, in this case, does not belong to WP Optimize and we will remove it with a new version. The integrity of our products and the trust of our customers are essential to us (and deliberately putting things in compromising open source code which is, frankly, a stupid thing to do).
The code in question is not ours is Wp Optimize's answer
WP-Optimize lead developer David Anderson gave WPTavern an interesting explanation. According to Anderson, the code disabling JS files when he detects the benchmarking tools dates back 2,5 years, when the company was considering joining forces with the Fast Velocity Minify plugin.
In the decision period, the developers of WP-Optimize forked and adapted Fast Velocity Minify . In the end, they couldn't agree. This is when Anderson thinks the code is mixed into the WP-Optimize codes. Those codes haven't been touched for 2,5 years, and the developers weren't aware of those lines.
“The code in question is not dangerous, a virus, an infection, useful for hackers, or something like that. The charge is that its only purpose in existence is to actually cheat the speed tests. That code, in this case, does not belong to WP Optimize and we will remove it with a new version. The integrity of our products and the trust of our customers are essential to us (and deliberately coding things open source which compromises which is, frankly, a stupid thing to do). "
Our advice on optimizing the Core Web Vitals
For our part we dismiss the interesting when sterile conversation and issues raised, reminding our readers that the data of type Labs, indicate but do not prove. What matters are the real user experience data (CRUX data) and the related core web vitals scores that will determine rewards or penalties by Google.
Field data is determined by monitoring all users who visit a page and measuring a certain set of performance metrics for each of those users' individual experiences. Since the field data is based on visits from real users, it reflects the actual devices, network conditions, and geographic locations of your users.
We therefore refer you to this reading: Core Web Vitals and CRUX data to understand how to cheat and deceive speed and performance tests such as Google Pagespeed Insight are of no use in real life and that you can exceed the requirements of Core Web Vitals even with scores in the orange area and not necessarily in the green area (above 90) as you can see for example from the following image of one of our customers who with a score of 78, it still surpasses Google's Essential Web Signals rating.
If you have a website developed on populated CMS such as WordPress for example and you are evaluating a performance optimization service that can bring real added value and a real improvement in the speed of your site and values Core Web Vitals, feel free to contact us.