Welcome to the WPML support forum. I will do my best to help you to resolve the issue.
I checked it here in Google Chrome Incognito mode during the busy internet hours of our time. Both the Hebrew and English posts show similar loading times for me.
Please check the attached images for more details and let us know your feedback.
Have you received any feedback from the LiteSpeed team?
which we did, and indeed after the first entrance to the site, the cache works perfectly.
BUT what is odd, is that Hebrew pages gets cache hit as i have shown above, and other (secondary) languages, are never HIT (=MISS) but after the page load, if i try to go to other pages on the site they most likely a hit.
It seems something related to secondary languages - litespeed suggest some kind of rule
this is what they wrote
"you may need that rule to make the currency or language to work properly"
we do have from you also snippet you gave us in the past related to ?currency=XXX
but since even without ?currency=XXX things are slow on first entrance, i guess it could be WPML code related issue with cookies and litespeed
by the way, adding the below code to WPML website, is definitely welcome
<IfModule LiteSpeed>
RewriteRule .? - [E=Cache-Vary:client_currency_cookie]
</IfModule>
because after you enter the site, things are super fast,
but they are super fast also on hebrew if the page was cached already, so i don't understand why only for /en/ /ru/ /de/ /nl/
things are slow on the first access only
since you know WPML by far better than me, maybe its worth first to look at dev console and maybe you will see different cookies on the secondary languages than on the main language (hebrew) and maybe you would know what is going little sideways
they claim that normally every entrance should be a miss unless you created a rule for that,
and it seems you did create a rule for it in the master language but for the secondary languages, you didn't
if you speak to litespeed about it the ticket numbers are:
103817 and 558213
I have another hypnosis, because Hebrew doesn’t have several currencies,
It works straight with cache.
"because Hebrew doesn’t have several currencies,
It works straight with cache."
and if i am right, then it would be an easy wpml fix to solve this other languages with extra snippet or code fix, that if loaded without ?currency=XXX
then it should somehow not transmit that it needs special cookie for currency like the hebrew and use that language main default currency
Thank you for the updates. For your kind attention, you are currently using a very old version of WooCommerce and WooCommerce Multilingual plugins.
Since the version 5.1.2 of WooCommerce Multilingual, we introduced most of the performance fixes and improvements on it. In this case, we would really advise trying the latest version 5.3.3.1, the latest version. It has lot of fixes. Please check the change log for more details.
Therefore it would be great if you could try it on your staging site (a clone copy of the live site) to confirm whether it resolves the issues or not. Please check and let us know your feedback.
i checked your changelog, and i didn't see any fix related to litespeed since my version
1. either you are lurcing in the dark
2. OR you didn't write in the changelog in related to litespeed fix to what i was showing you.
A. is my hypothesis correct, that hebrew works fast because it doesn't hav multi currency?
B. Did you check with litespeed how to make all languages work fast even with multi currency so is cached?
C. AT LAST after we resolve it, i will need your assistance to modify the ?currency=XXX you gave me in the past, so its cached as well
THIS IS THE LATEST FROM LITESPEED on ticket: 558213
- and it does seem like a collaboration bug between litespeed and wpml that needs to be addressed !
and in order to properly display the currency and language , the cookie must be set
and in order to set cookie , the PHP must be triggered
and in order to trigger the PHP , the cache must be missed as cache hit will avoid launch PHP process.
I have had this conversation with WPML team some times ago , and attempt to find a solution to make first visit cache hit with multi-language/currency , believe me , we spent a lot of time and effort to it , but unfortunately we can't find a good solution for such
Thank you for your feedback. I have shared it with our team. Please note that the last major release of WooCommerce Multilingual is 5.3. Rest of the releases are fixes and improvements.
We request to upgrade to you to the latest version in a staging site to make sure the bug exists with the latest versions or not. As you know, the backward compatibility is very very tough to implement.
We will get back to you on this soon. Please wait.
"I have had this conversation with WPML team some times ago , and attempt to find a solution to make first visit cache hit with multi-language/currency , believe me , we spent a lot of time and effort to it , but unfortunately we can't find a good solution for such"
Hebrew gets cached, others don't, this is whats WPML needs to figure out why
1. it could be how you treat the main language that is working correctly and secondary not
2. OR i could be that because HE has 1 currency while others have multiple
but even if its 2, you found via 1 the way to make the first hit of 2 gets cached if you fix the code together with litespeed
Thank you for providing us with the details. I've forwarded them to our second-tier team for further investigation. We'll update you soon. Please wait.
We have found the ticket LiteSpeed team has mentioned. Our compatibility team were in touch with them and we had a detailed debugging on this in the past. As per our their last communication, they were working on a solution for this. Please check the following replies for more details.
