Skip to content Skip to sidebar

Home › Support › English Support › [Waiting for user feedback] performance issue

[Waiting for user feedback] performance issue

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.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 -
- 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 -

Supporter timezone: Asia/Kathmandu (GMT+05:45)

This topic contains 1 reply, has 0 voices.

Last updated by Shekhar Bhandari 1 day, 10 hours ago.

Assisted by: Shekhar Bhandari.

Author Posts
April 23, 2026 at 8:32 am #17989592

sebastianS-157

Hello,

I'm following up regarding the recurring performance issue on mp-technik.com.pl.

**Important new context:** I cannot deactivate WPML as a workaround. The site's theme and custom code contain hardcoded conditionals that depend on WPML functions (ICL_LANGUAGE_CODE, icl_object_id, etc.). Deactivating WPML breaks content display entirely, not just translations. This is a legacy codebase situation.

This means I must keep WPML active, and I need to find the root cause of the recurring slowdown rather than working around it.

**Recap of the pattern:**
- After WPML is reactivated (after any cache clear, plugin update, or my own deactivate/reactivate cycle), the site runs fine for approximately 60 minutes
- Then it slows down severely - PHP process limit (8 concurrent) becomes saturated, pages take 10+ seconds or time out
- This cycle repeats consistently

**What's been ruled out:**
- WooCommerce database migration (completed successfully, DB version now matches plugin)
- Auto-register strings (disabled)
- Bot traffic, cron jobs, Action Scheduler
- Hosting capacity (other WP sites on same account perform normally)
- WPML cache (cleared multiple times)

**My current setup:**
- WordPress + WooCommerce 10.7.0
- WPML Multilingual CMS 4.9.2
- WPML String Translation 3.5.1
- WPML Multilingual for WooCommerce 5.5.5
- WPML SEO 2.2.5
- PHP 8.2, 8-process PHP limit on shared hosting

**Request:**

Since the issue is reproducible (it returns roughly 1 hour after any WPML state reset), I'd like to schedule a live diagnostic session during the "degraded" phase. I can time it so WPML has been running for 50+ minutes when we connect, so you can see the problem directly.

Please let me know:

1. What's the best way to schedule this - continue on this ticket, open a new chat at a specific time, or something else?

2. What debug tools or logs should I enable beforehand? I'd like to have useful diagnostic data ready when we connect.

3. Would you need temporary admin access to the site, or can you work from shared screenshots and System Status output?

4. Is there anything I should NOT do in the meantime (like clearing WPML cache) to preserve the state for diagnosis?

This is a production e-commerce site and the issue significantly impacts operations. Any help would be greatly appreciated.

Thank you,
[Your name]
April 23, 2026 at 10:16 am #17989865

Shekhar Bhandari
WPML Supporter since 03/2015

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

Thank you for contacting WPML support. I’ll be happy to assist you with this issue.

Live diagnostic session
We don’t offer scheduled sessions. The best approach is to start a live chat when the issue is about to occur — ideally during the degraded phase, as you mentioned.

Please be sure to reference this ticket so our team can quickly review the context.

Debug tools and logs
Before starting the chat, please enable:

- WordPress debug log:


define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

- Query Monitor plugin (to review slow queries and hooks)

If possible, we also recommend contacting your hosting provider in advance to check whether they have logs from the last time the issue occurred.

Access requirements
For deeper analysis, temporary admin access is usually required.

What to avoid before diagnosis
To preserve the issue:

- Do not clear WPML cache
- Avoid deactivating/reactivating WPML or related plugins
- Avoid major changes (updates or configuration changes)

We look forward to your message when you're ready.

Thanks