Home›Support›English Support›[Resolved] Very High Number of Requests from WPML – Causing Server Overload
[Resolved] Very High Number of Requests from WPML – Causing Server Overload
This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing severe performance issues on your site, particularly on product listing and detail pages, due to a high number of requests. This is causing server overload, timeouts, and database connection issues. Solution: The performance problems are linked to errors from two specific plugins: the Health Check & Troubleshooting plugin and the WooCommerce Cart Abandonment Recovery plugin. These errors are not caused by WPML. We recommend deactivating the Health Check & Troubleshooting plugin as it is no longer maintained. You should also consider replacing the WooCommerce Cart Abandonment Recovery plugin since it is not officially compatible with WPML. For more details on the error related to these plugins, please visit this link.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am experiencing serious performance issues on my site related to WPML. On the product listing (archive) page, there are around 640 requests, and on the product detail (single) page, there are around 70 requests. This is creating a heavy server load and contributing to timeouts and database connection issues.
Symptoms:
Very high number of requests from WPML causing server overload, leading to timeouts and database connection issues.
Thank you for reaching out to WPML support. While one of my colleagues picks up this ticket, I’d like to provide some initial debugging steps and see if I can assist you right away.
Thank you for your reply.
We were able to make some adjustments and installed the Index WP MySQL For Speed plugin, as suggested in the link you provided.
Unfortunately, the issue remains the same — we are still experiencing a very high number of queries and server overload, especially on listing and product pages.
As requested, please find attached aQuery Monitor screenshots from the back-end for your review.
The attached screenshot is a capture from the backend using Query Monitor.
Please note that the screenshots we shared in our first message were from the frontend, and the number of queries there is actually even higher.
At this stage, we are planning to set up a staging site where we can safely test things further by disabling plugins one by one, as recommended.
Let us know if there’s anything else we can do to further optimize WPML’s performance or reduce unnecessary queries.
If you require additional assistance with this, please share the access details to your site with me. Please let us know where and how to view this performance issue. In other words, where should we go to see the slow queries? Additionally, if necessary, please allow us to modify the theme and deactivate or install plugins. If you have a staging site where we can view this issue, please share access with us. I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
We are currently having some difficulty creating a demo site. In the past, we were able to easily create one through the cPanel of our hosting provider, but unfortunately, that service is not working at the moment. If you could help us with this issue or suggest an alternative method to set up a demo site, we would greatly appreciate it.
Regarding the performance issue, it is mainly occurring on the listing page, the detail page, and the homepage. If you could guide us on where to check the slow queries for these specific pages, it would be very helpful.
Please let us know if you need any further information from our side.
To enable it, open your wp-config.php file and look for
define('WP_DEBUG', false);
Change it to:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
After this, repeat the action that causes the problem on your site--visit the product listing (archive) page and the product detail (single) page. The errors, if there are any, will be saved to a debug.log log file inside the /wp-content/ directory. Then please share the errors with us. Please only share the errors from the time you proceeded with this check.
I’ve just enabled WordPress debugging as instructed by modifying the `wp-config.php` file. I’ve also visited both the product listing (archive) page and the product detail (single) page to replicate the issue.
The errors come from two plugins you are using: the Health Check & Troubleshooting plugin and the WooCommerce Cart Abandonment Recovery plugin. The Health Check & Troubleshooting plugin is not maintained, so I suggest you stop using it. The WooCommerce Cart Abandonment Recovery is not officially compatible with WPML. So it might cause problems.
Thank you very much for your detailed response and for checking the debug log.
You were right — the issue was indeed coming from those two plugins. We've now deactivated the Health Check & Troubleshooting plugin, and we're evaluating alternatives to the WooCommerce Cart Abandonment Recovery plugin due to the compatibility concerns.
Really appreciate your help and the useful link you shared!
