A few weeks ago I released WP Scanner – a tool for monitoring WordPress load time, performance, and security. In this article I want to share with you my journey over the last few months, along with some of the lessons I’ve learned. Why was WP Scanner Born? There are already plenty of tools for monitoring site performance and security plugins for securing your site, so why build WP Scanner? It’s a good question and one I pondered myself for many months before finally knuckling down and building it. Firstly, the vast majority of performance tools are dated and some of the recommendations are no longer relevant today, especially with HTTP/2 gaining widespread adoption. In addition, they don’t check for WordPress specific nuances, such as object caching, which can have a big effect on performance. Secondly, security plugins can be process intensive, especially those that perform active monitoring, such as Wordfence. This can have a negative affect on your site’s performance, which is why some hosts disallow such plugins. Offloading security monitoring to a third party service can massively reduce CPU and memory usage locally. The majority of security plugins
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.