Inicio›Soporte›Soporte en español›[A la espera de la opinión de los usuarios] Severe performance issues caused by WPML String Translation
[A la espera de la opinión de los usuarios] Severe performance issues caused by WPML String Translation
Este es el foro de soporte técnico de WPML, el plugin multilingüe de WordPress.
Todas las personas pueden leerlo pero solo los clientes de WPML pueden ingresar comentarios. El equipo de WPML responde en los foros 6 días a la semana, 22 horas por día.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-
-
9:00 – 18:00
9:00 – 18:00
9:00 – 18:00
9:00 – 18:00
9:00 – 18:00
-
-
-
-
-
-
-
Zona horaria del soporte: America/Lima (GMT-05:00)
It's slow because you are running in staging site without server resources, is obvious is for wpml strings, there are a lot of information, review all the conversation please.
I tested your staging site:
- With only WooCommerce active, the shop page loads in 1–2 seconds
- With WooCommerce + WPML active, the shop page also loads in 1–2 seconds
- When all plugins are enabled, the site performs with a load time of between 3-5 seconds
- As noted earlier, the shop page took yesterday ~13 seconds to load even without WPML, which indicates the slowdown is not caused by WPML itself. Now, after I had disabled all plugins and enabled them again, I can no longer confirm this. The load time is now in a similar setup between 3-5 seconds.
---
Further steps:
Regarding WPML > String Translation, please try the following optimizations:
1) Generate custom language files
Go to WPML > Support > Troubleshooting and click Show custom MO files pre-generation dialog box.
Then run the dialog in WPML > Theme & Plugin Localization. This will create custom language files and improve String Translation performance.
2) Clean up string tables
In WPML > Support > Troubleshooting, click Cleanup and optimize string tables.
Currently, there are 13,505 registered strings. Under WPML > String Translation > Utilities > Delete strings by domain, you’ll see many domains with few or no translations. Consider deleting unused strings to reduce overhead.
As WPML String Translation renders strings in real time, it does use more CPU resources than other plugins. However, this only impacts performance if the server CPU is near 100% utilization.
This is acceptable, but increasing the PHP memory limit to at least 384M (or higher) would provide more headroom and may improve overall performance. At the moment, I am running into random 500 errors when enabling plugins like Elementor or WPML, which usually each need 128M of memory.
4) Make sure that all plugins are updated and avoid using plugins that share similar functionalities. For example, the plugin "String Locator" was installed on the site, which is not needed, as it might lead to performance issues with WPML String Translation while sharing the same resources.
5) Delete any inactive plugins that are no longer in use on the site.