It would be great if people can check the previous tickets before posting the same issues that were already handled. For instance, the issue that you are reporting was already explained here [1] and the solution is also described there.
I fixed that problem like four weeks ago with this commit [2] and the patch was merged with version “1.7.10” which was released last week. Unfortunately the modification broke a feature that all our premium clients were using (specifically the CloudProxy users), so we obviously had to revert the modification with this commit [3] and that is why version “1.7.11” is slow again.
I will offer you two solutions, one is to read the explanation and solution that I posted here [1]; or you can install version “1.7.10” using this link [4]. I am working on a definitive solution for both premium and regular users but it will take some days before I can finish writing that code.
[1] https://ww.wp.xz.cn/support/topic/sucuri-security-plugin-using-cloudflare-slows-sites
[2] https://plugins.trac.ww.wp.xz.cn/changeset/1165714
[3] https://plugins.trac.ww.wp.xz.cn/changeset/1183868
[4] https://downloads.wp.xz.cn/plugin/sucuri-scanner.1.7.10.zip
While I appreciate the time you took to answer my post I must say your attitude is uncalled for.
Thanks for your “solutions” I think I’ll just uninstall it instead.
Have a great day!
Okay, uninstallation works too.
It is worth to mention (for anyone else facing the same issue) that the slowness caused by the plugin is not strictly tied to its code, but to a misconfiguration of the DNS resolver installed in the server where your (or anyone’s) website is being hosted.
So to be more precise, this issue MUST be fixed by your hosting provider not us, I only offer these “solutions” as a workaround because most hosting providers are slow in their response time or do not care at all about individual websites. Also DNS issues are not a trivial thing so it is understandable that they take their time to fix those errors.
@positivemostofthetime it is unfortunate that none of my “solutions” work for you, at least the installation of the previous version “1.7.10” was a good one. Have a nice weekend too.
As it was suggested here [1] I added a new condition in the code [2] that can be used to force the plugin to not use the DNS lookup functions in slow servers. Setting the constant “NOT_USING_CLOUDPROXY” will help people that are not using a reverse proxy to speedup their websites once again.
Note that this does not resolves the issue that I explained in previous comments, the issue is in the DNS resolver and only the hosting providers can fix this definitely. This modification only fixes the issues with the plugin nothing more.
[1] https://ww.wp.xz.cn/support/topic/page-load-time-1
[2] https://plugins.trac.ww.wp.xz.cn/changeset/1194834
