Performance issues

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing performance issues in the admin area due to frequent calls to the ate.wpml API. These calls were made on every admin page and were significantly slowing down the site. The client noted that all translations were done manually and did not require these API interactions.
Solution:
We analyzed the client's database and discovered that the sync requests to the ATE server were triggered by leftover entries from translation jobs that were never completed. These entries were related to original pages that had been deleted, causing the API to repeatedly check for updates that never occurred. We resolved the issue by removing these obsolete database entries, which stopped the unnecessary API calls and improved the site's performance. We also informed our developers about this issue to prevent similar problems in the future.

If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues 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.

Tagged: Performance

This topic contains 5 replies, has 0 voices.

Last updated by George Botsev 4 months, 4 weeks ago.

Assisted by: Itamar.

Author	Posts
November 5, 2025 at 12:49 pm
Dylan	Background of the issue: I am trying to address performance issues caused by calls to the ate.wpml API, which are slowing down the admin area. These calls occur on every admin page, such as: hidden link. All translations on the site are done manually, so I don't see the need for these API calls. Additionally, there are less frequent calls to: hidden link. Symptoms: The API calls take between 0.5 and 2 seconds, significantly degrading performance. Disabling WPML noticeably speeds up the site. The server has been upgraded recently, and there are plenty of resources available, so these aren't an issue. Questions: Is there a way to configure the site to not need these API calls?
November 5, 2025 at 2:14 pm #17550680
Itamar WPML Supporter since 02/2016 Languages: Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, While I was creating a copy of your site, I noticed you deactivated the Log HTTP Requests plugin. If needed, may I activate it again? Regards, Itamar.
November 5, 2025 at 2:34 pm #17550788
Itamar WPML Supporter since 02/2016 Languages: Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, Our second-tier supporter wants to inspect the DB of your site. For this, we need your permission to install a plugin like WP phpMyAdmin. Do you allow us to proceed with installing this plugin? Regards, Itamar.
November 8, 2025 at 9:10 am #17558995
Dylan	Sorry, I have not been receiving notifications on this ticket. Yes, please proceed with installing and activating the required plugins.
November 10, 2025 at 12:34 pm #17562292
Itamar WPML Supporter since 02/2016 Languages: Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+03:00)	Thanks. I've installed and activated the required plugins (the Log HTTP Requests plugin was already installed). Our second-tier supporter will look into this issue, and I will update you here once I have his reply. I appreciate your patience. Regards, Itamar.
November 11, 2025 at 12:08 pm #17566058
George Botsev	Hello! I am George from the second tier support team. Your ticket is my responsibility for handling it and I figured out the problem. It appears that you have some jobs that were sent to translation to ATE and analysing the database, I've seen that the sync request is happening because of that. These specific jobs left an entry in the database and the sync request was trying to check their status with ATE server. However for those jobs, the original pages were deleted and no progress was made on translating the job since its creation, which resulted in the process being stuck and happening and checking for changed status over and over. I've fixed the problem on your site and also I have notified our developers of this case.