Skip Navigation

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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: America/Los_Angeles (GMT-08:00)

This topic contains 9 replies, has 3 voices.

Last updated by Bobby 7 months, 1 week ago.

Assisted by: Bobby.

Author Posts
June 17, 2024 at 1:17 pm #15745733

Károly Farkas

Background of the issue:
Our site feels slow. If we disable WPML, the site speed noticeably increases.
The main parameters:
200.000+ products,
hosted on a strong server,
PHP 8.1,
No active Query monitor or SSL redirection plugins.
Index WP MySQL For Speed plugin is active.
I have already walked through these recommendations: https://wpml.org/forums/topic/how-can-i-improve-performance-of-a-slow-site/ except for cache, because all cache solutions we tried so far made the site slower. (it is under development, we are continuously trying to make cache work). However, since the site is slower when WPML is active (and according to documentation, it should not be), I would like to know if your developers can detect any particular issue related to WPML.

Symptoms:
The site is slower when WPML is active.

Questions:
Can your developers detect any particular issue related to WPML that is causing the site to slow down?

June 19, 2024 at 5:12 am #15752564

Mihai Apetrei
Supporter

Languages: English (English )

Timezone: Europe/Bucharest (GMT+02:00)

Hi there.

Yes, we would be happy to take a closer look at this.

We would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and us can see and have access to it.

Our Debugging Procedures

We will be checking various settings in the backend to see if the issue can be resolved. Although we won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, we will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Please let us know if that would be ok for you.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

**IMPORTANT**

- Please make a backup of the site files and database before providing us access.

- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.

The private box looks like this: hidden link

We will be waiting for your response.

Kind regards,
Mihai Apetrei

June 25, 2024 at 1:16 am #15813317

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

thank you for the access details!

Is this a live site or a staging environment? If it is a live site, do you possibly have a staging environment where the performance issue is reproduced?

We can create one for you if needed but since there is a large number of products it would be good to test on an existing staging env.

July 1, 2024 at 7:49 am #15866275

Károly Farkas

Hello!

I modified the access details in the private message for the test site. The test site is on the same server, but different directory (and of course different database). The test site does not have images.

July 2, 2024 at 8:44 pm #15878161

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Thank you,

I was able to access the backend. I am testing this and will update you shortly

July 3, 2024 at 7:06 pm #15886542

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

Here are my findings:

7s load time without WPML

There are many 404 errors due to the missing/broken images and icons which can be causing a performance hit on the staging site.

However, enabling WPML makes the site unusable at the moment. My load time was around 3-5 minutes... is this what you are also experiencing on your live site?

Not sure if the 404 errors are exaggerating these times.

Switching from the Child theme to Flatsome and activating WPML

backend load time 3s

front end load time 4.3s

These results point towards an issue between the Child Theme and WPML.

Are you currently using a lot of custom code/functions in your Child theme? Any new ones added recently that could have caused some compatibility issues?

Please do note that our support provides limited support when it comes to custom work, however, I will do what I can to help you resolve this issue.

If you developed the child theme I recommend to review the functions or custom code used or to contact your developer to also review this.

Let me know your results, please.

July 4, 2024 at 8:43 am #15890354

Károly Farkas

Hey Bobby,

Thank you for the checks and the explanation.

There are a lot of customizations on the site, but they are all in the "FS" plugin. In the child theme, there are no custom code.

However, I double checked the child theme's functions.php and found a snippet - related to WPML, which made the site unresponsible earlier as well. I'm not sure if it was left there by the previous supporter (it was a different issue: https://wpml.org/forums/topic/cannot-open-wpml-settings-page-fatal-error/) or by you, but now I commented it out, because this certainly "kills" the site.

So without this snippet, you can test the site with WPML enabled/disabled. Our expreience was that the site loads cc. 2 times slower with WPML enabled.

If you want to exclude all custom code (written by me, the developer of the site) you could disable "FS" plugin.

However if the No.1 "suspect" remains the child theme, then it must be some theme related setting, which causes the long loading times (3-4 seconds are not the best, but we would be ok with that, it's much better than 7s).

Thanks

July 5, 2024 at 10:38 pm #15900430

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Thank you for confirming!

I added no script during this debugging session, therefore it must have been from the previous ticket, glad it has been deactivated now.

Reviewing the performance now with your parent theme and a minimal environment I am not seeing a major increase of performance with WPML enabled vs without.

Checking out the FTTB loading time I get an increase from 1.33 to 1.44

Screen Shot 2024-07-05 at 2.54.06 PM.png
July 13, 2024 at 3:05 pm #15947602

Károly Farkas

That is indeed not a big difference.
Would you be so kind to make a test with woocommerce and all Dokan plugins enabled? (Dokan + Dokan pro + Dokan WPML) Because these three plugins (Woo, Dokan, WPML) are the most important plugins of our site.

July 16, 2024 at 10:07 pm #15962866

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

Running the test again with these plugins activated I am getting the same results.

The major difference in performance is only made when switching from the Child theme to the Parent theme (going from 5s to 1.4s)

The topic ‘[Closed] WPML slows down site with huge number of products’ is closed to new replies.