Version 1.7.12 update affecting site performance

I just added another option in the general settings to disable the XHR (XML HTTP Request) monitor [1] the option will be disabled by default. Among the changes submitted so far to address this issue with the slowness of the site this one along with the DNS lookups may be one worth to test, I explained some of the details of this modification here [2].

[1] https://plugins.trac.www.ads-software.com/changeset/1209886
[2] https://www.ads-software.com/support/topic/sucuri-is-blocking-wordfence?replies=6#post-7242463

With all three – DNS lookups, comment monitor and XHR – disabled, site performance seems to be back to normal.

Tested all three individually (enabled/disabled): DNS lookups didn’t seem to slow the site; comment monitor did, though not by as much as XHR, which seems to be the main culprit.

Thank you @purbeckpixels for confirming that the XHR monitor was indeed the culprit and that the option to disable this feature fixed the issue. Thank you @i-mmmk-i for your help confirming that the DNS lookups where not really the problem. And thanks to @ljmac, @damiafaw, and @shazahm1 for your feedback.

We will release version “1.7.13” publicly today so you all (and the rest of Sucuri plugin users) can get the updated version of the code with the applied patches.

Tested the new update. Working all good now!

Thank you @yorman for being so fast on this issue, Great work!

Regards

Yes, thanks @yorman.

While I’m here, is it possible for the ‘Hardening’ section to monitor for Apache 2.4 syntax? I like to use the updated syntax e.g. in wp-content

<Files *.php>
Require all denied
</Files>

Currently, the plugin is telling me that wp-content etc aren’t hardened when they are – my guess is the plugin is looking for the old Apache 2.2 syntax. I know the old syntax is still compatible with 2.4, but I like to be consistent and at some point in the future Apache is sure to stop supporting the old syntax.

@purbeckpixels I just released version “1.7.13” which includes this changeset [1] this new code is executed when one of the three directory hardening options is clicked. If the plugin detects the old version of the denial rules then it deletes them and injects the new syntax which should be compatible between Apache 2.2 and 2.4+.

Here is a thread related with your suggestion [2].

[1] https://plugins.trac.www.ads-software.com/changeset/1209852
[2] https://www.ads-software.com/support/topic/after-update-to-1712-hardening-wp-content-breaks-images