Performance

Problem:
El cliente experimenta lentitud en su sitio web al activar el plugin WPML. El sitio está en PHP 8.2 y todos los plugins y temas están actualizados.
Solution:
Para abordar este problema sin riesgo para el sitio actual, hemos creado un servidor de prueba en Cloudways. Recomendamos migrar el contenido del sitio a este servidor de prueba para depurar el problema. Los pasos para la migración incluyen:
1. Instalar el plugin Cloudways WordPress Migrator.
2. Completar el formulario de migración con los detalles proporcionados por nosotros.
3. Iniciar la migración y esperar las notificaciones por correo sobre el progreso.
Para más detalles sobre la migración, visita: https://support.cloudways.com/how-to-migrate-wordpress-to-cloudways/
Si esta solución no resuelve el problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/ y asegurarte de que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, por favor visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.

Problem:
The client is experiencing significant slowdowns on their website when WPML plugins are activated.
Solution:
If you're experiencing similar issues, we recommend you try the following steps:
1. Create a full backup of your site.
2. Ensure all plugins and themes are up to date.
3. Flush any existing cache memory.
4. Deactivate all plugins, including WPML ones.
5. Activate a default WordPress theme, such as Twenty Twenty.
6. Reactivate the WPML plugins.
7. If the performance improves, reactivate your original theme and then other plugins one by one to identify the problematic plugin.
Additionally, please provide the debug information by following the guide at https://wpml.org/faq/provide-debug-information-faster-support/.
If these steps do not resolve the issue, update WPML and other plugins to their latest versions and flush any cache again.

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.

Problem:
The client is experiencing poor PageSpeed results for the English version of their multilingual website, while the Hebrew version shows good performance.
Solution:
We noticed that the Chat VS widget, which loads on the Hebrew site, does not appear on the English site. This could potentially cause loading issues. Additionally, the client might need a separate license for each domain to ensure optimal caching with WP Rocket, as per their support comment from 2019. WP Rocket's compatibility with WPML
Here are further steps to improve performance:
1. Disable "display as translated" in WPML > Settings.
2. Turn off "Adjust IDs for multilingual functionality" at WPML > Languages.
3. Disable “Track where strings appear on the site” in String Translation.
4. On the WPML->Support-> troubleshooting page, run:

Cleanup and optimize string tables

Clear invalid strings

Remove ghost entries from WPML tables

If these steps do not resolve the issue, or if the solution seems outdated or irrelevant, we 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
You are experiencing slow performance on your site, and PHP x-ray reports indicate that WPML is significantly impacting performance. The issue might be related to the database collation settings for the wp_postmeta table.
Solution:
We recommend altering the collation of your wp_postmeta table to utf8mb4_general_ci to potentially resolve the performance issues. You can do this by executing the following SQL commands in your database:

ALTER TABLE `wp_postmeta`<br />CHANGE `meta_key` `meta_key` varchar(255) COLLATE 'utf8mb4_general_ci' NULL AFTER `post_id`,<br />CHANGE `meta_value` `meta_value` longtext COLLATE 'utf8mb4_general_ci' NULL AFTER `meta_key`,<br />COLLATE 'utf8mb4_general_ci';

If this solution does not apply to your case, or if it is 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
If you're experiencing slow site performance when the Advanced Custom Fields Multilingual plugin is activated, it might be due to the high number of ACF field calls. In a case we investigated, activating WPML increased the load time significantly because it hooked into each ACF field call for translation, executing over 8000 times.
Solution:
To address this, we recommend two strategies:
1. Reduce the number of ACF field calls by modifying the theme to minimize usage of

acf_get_field

, especially for fields that don't require translation. Replace these with direct

get_post_meta

calls to bypass both WPML and ACF retrieval logic.
2. Use a filter introduced in ACFML 2.1.4 to bypass translation logic. Add the following code to your theme's

functions.php

or as a drop-in plugin:

add_filter( 'acfml_should_translate_acf_entity', function( $should, $field, $context ) {<br />    $should = false;<br />    static $customfield_settings;<br />    if ( ! is_array( $customfield_settings ) ) {<br />        $icl_sitepress_settings = get_option( 'icl_sitepress_settings' );<br />        $customfield_settings = $icl_sitepress_settings['translation-management']['custom_fields_translation'];<br />    }<br />    if ( $context === 'field' ) {<br />        $field_name = $field['name'];<br />        if ( isset( $customfield_settings[$field_name] ) && $customfield_settings[$field_name] === WPML_TRANSLATE_CUSTOM_FIELD ) {<br />            $should = true;<br />        }<br />    }<br />    return $should;<br />}, 10, 3 );

This code ensures that only fields marked for translation are processed, significantly improving performance.

If these solutions do not resolve your issue or seem 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 the problem persists, please open a new support ticket.