cloudres

Thanks for the feedback. Maybe it’s something that you and WPML needs to investigate. Is there something that can I do it to help you in that sense?

Thanks @jeroenrotty.

Dear @maybellyne,

happy to received an answer at the end. Thanks! Happy to say also that it worked! It fixed the problem on our staging web site.

Now I’d like to ask you how can we avoid that it will happen on our production web site updating Yoast. Is there a way to avoid it?

If not, what exactly happens resetting those records? I want to be sure that I do not need to check all the web site to see that our work wasn’t lost.

Thanks a lot for your time.

Obviously I would appreciate if you can suggest a way to re-save all archive pages in one way. Without opening them one by one.

Considering that we always paid for recharging our credits on Quic.Cloud, this is a very very slow support. Let me say that @qtwrk.

It works, it was been just a cache problem.

@qtwrk so using “JS Deferred Excludes” we can exclude from the delaying also. That’s fine, we’ll try it asap. Thanks!

We’re occurring another problem related to this. There is an icon of shopping cart above the fold on our web site that shows the number of products inside the cart. Without loading the Ajax it does not work before clicking. I think that it is a common problem in a web site that sells online. Also in this case, maybe a feature to excluding some files would be good.

It sounds great. We’ll try it asap.

Another question. Is there a way to exclude the Google Analytics js from this delaying? There could be some situations where the customer click on a link in page quickly, without waiting the loading of JS files. Mainly from smartphone where you can just click without scrolling or moving a cursor. I ask this, because after the delaying JS activation I saw a drop in visits by Google Analytics.

Ops, it’s true. CSS and JS files on the cart and checkout pages are not minified by default. While I confirm without any doubt that the cache doesn’t works there. But so why automatically the JS Delay works there? Is should not be excluded by default?

Dear @qtwrk,

why should I disable all optimization inside cart/checkout? CSS/JS minified are still useful there.

But if I delays the loading of JS files there, Amazon Pay doesn’t shows its login button for example. Same result with Apple Pay or Google Pay by Stripe and again other problems with PayPal.

It’s acceptable from desktop, because moving the cursor the JS are loaded without any evident problem on the screen. But from the smart phone it’s different. If the customer does not touch the monitor nothing happens there. When the customer touch the monitor there is an huge blocking time, because all JS must be loaded. In that case there is also a re-syncronization of the cart content… it is not a good experience for the customer. A customer could leave the page because could not understand what it’s happening.

This is why I’m writing you.

@serpentdriver we’re not joking. If a fix exists, please paste a link that points directly to it. Do not ask to find something in a documentations long tons of words. For your information we already take a look at the documentation, but we didn’t find anything related to JS Delayed.

Thanks.

@serpentdriver unfortunately your is not an useful comment. I’ll wait for another supporter comment. Thanks the same!

Thanks a lot for clarified this!

The fix suggested by WPML fixed the issue on our sitemap. They said that will add it on one of next WPML releases. Thanks the same for the support!

Our web site is on a LS server, so we could use it. But we didn’t understand the utility. Could you explain us better?