This information is not accurate.
The test will also include:
NinjaFirewall (WP edition). If you aren’t familiar with it, this is how it works:
Attacker => HTTP server => PHP => NinjaFirewall => WordPress => PluginsAnd this is how the above-mentioned plugins and, more generally, all WordPress plugins work:
Attacker => HTTP server => PHP => WordPress => PluginsNinjaFirewall sits between the attacker and WordPress. It can filter requests before they reach the blog. That makes it very suitable for detecting and, most important, for blocking brute-force attacks.
.htaccess files are server configuration files (distributed configuration files). The reason .htaccess files are the optimum method of filtering requests is because .htaccess files are processed before PHP code.
Attacker => HTTP server => .htaccess files (BPS & BPS Pro) => PHP => NinjaFirewall => WordPress
Conclusion:
NinjaFirewall (WP edition) was able to block both attacks because it sits between the attacker and the victim. A security plugin that sits behind the application that it is supposed to protect is of no use.On average, WordPress performs better alone than with the 5 security plugins that were tested. Most of them do not bring any improvement, the others may even increase server resources to a critical level during a large attack.
The conclusion is negated because it is not accurate. The limited testing that was done (if actual testing occurred) is negated as well for numerous obvious reasons. Frankly the entire post/article is ridiculous from beginning to end.