Performance

Problem:
After installing WPML to translate their website, the client's site became very slow. The client wants to know why and how to resolve the performance issue.
Solution:
1. Increase the WP Memory Limit to at least 128MB, ideally to 256MB for optimal performance. Open the

wp-config.php

file and add the following line just before the comment that says '// That's all, stop editing! Happy blogging.':

define('WP_MEMORY_LIMIT', '256M');

2. After updating the memory limit, clear any caches (plugin, browser, and server-side if available), then check your site speed again.
3. If the site remains slow, deactivate all plugins except WPML and its add-ons to check for plugin conflicts. Reactivate them one by one to identify any specific plugin causing slowdowns.
4. Enable object caching and configure a caching plugin like W3 Total Cache for improved performance.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, 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 the problem persists, please open a new support ticket for further assistance.

Problem:
After migrating to a new hosting, a WooCommerce store operating in three languages experienced significant slowdowns when WPML String Translation was enabled. The site's admin pages often timed out, and there were heavy database queries on icl_strings and icl_translations tables. Additionally, the Advanced Translation Editor (ATE) failed to authenticate, showing repeated auth_error logs.

Solution:
To address these issues, we recommend the following steps:
1. In your WordPress dashboard, navigate to WPML → Settings and check the Translation Editor section for any prompts about reconnecting.
2. Disable string tracking and adjust IDs for multilingual functionality.
3. Use WPML's troubleshooting tools to optimize and clean up string tables, clear invalid and unused strings, and remove ghost entries.
4. Consider using caching plugins and database/object caching where possible.
5. If these steps do not resolve the performance issues, we suggest creating a backup and sharing access credentials with our support team for further investigation.

Please note that this solution might be outdated or not applicable to your specific case. 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.

Problema:
Al intentar activar y configurar WPML en un sitio de prueba, que es una copia del sitio de producción con un gran volumen de publicaciones y adjuntos, se generan consultas SQL intensivas que provocan un uso excesivo de recursos y errores de tiempo de espera (error 524).
Solución:
Si estás experimentando un consumo excesivo de recursos durante la activación de WPML en entornos con alto contenido, te recomendamos contactar con tu proveedor de hosting para aumentar los recursos del servidor. Además, desactiva todos los plugins y activa un tema por defecto de WordPress durante la instalación para minimizar el consumo de recursos. Si el problema persiste o la solución proporcionada no es relevante porque está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.

Para asistencia adicional, no dudes en contactar nuestro foro de soporte en WPML support forum.