hernan2022

I was able to fix it, the filter was correct. It was the type of block that inserted another lazy load

Thank you

Thank you

I understand, no problem

The only thing is that maybe I would appreciate a comment regarding XMLHttpRequest. I have done a clean installation locally and I can confirm that this does happen everywhere, also with the free plugin (especially on BuddyPress/Youzify pages), the easiest way is to check the browser console on those pages, the browsers understand that it is something undesirable

I would greatly appreciate it if you could at least communicate this to the rest of the Youzify team, as it does seem to be important to Google.

Thank you

Thanks for answering,

Youzify Pro: 3.3.9
Yozify Albums: 1.0.5

I confirm that the href warning disappears when disabling Youzify Albums. I can also report that by modifying the file \youzify-albums\public\functions\youzify-general-functions.php it is possible to add href=”#” to both links and the popup continues to work (it is the popup that appears when deleting an album or album element)

While testing I noticed a slightly more important problem. When an album is deleted, an error log is left in the activity feed

I think that the ideal thing to do when deleting an album is to delete all records in the activity feed, I think it is something that is worth checking.

But I would appreciate if you could comment on the warning about the synchronous use of XMLHttpRequest. I think this is the most important warning that Google is giving right now

To summarize the report:

• Google gives warning for synchronous use of XMLHttpRequest
• When an album is deleted, a record remains in the activity feed (and shows errors since deleted information is consulted)
• Album confirmation popup could have href=”#” to avoid Google warnings (this is less important)

Thank you

I understand, thanks for the information

ouch, so it’s not possible to disable the cache to an ESI nonce?

I think I’m confused, I hope that thos hook can help

https://docs.litespeedtech.com/lscache/lscwp/api/#set-custom-ttl

• This reply was modified 1 year, 5 months ago by hernan2022.

What I have finally done:

Since rating_nonce is already on the official list, just enabling ESI should make it an ESI block

Searching the theme files I found another very similar nonce block called “extra_rating_nonce”, I will add this one to the list preventivel

In functions.php I think I can assign TTL 0 to both ESI blocks with the following code

do_action( 'litespeed_control_set_ttl', 'rating_nonce', '0' );

do_action( 'litespeed_control_set_ttl', 'extra_rating_nonce', '0' );

Now I have the doubt if it really works, how can I check it? Should notices appear in the html? Does what I’m doing seem good?

https://brevenoticia.cl/noticias-internacionales/20-10-2023/hamas-libera-a-madre-e-hija-rehenes-estadounidenses/

At the end of the entry, next to share post, the stars for rating entry appear.

Thank you very very much

Oh what a shame, I think it was pretty simple, it was there in the official documentation

If I want that section not to be cached I should apply the following code:

add_action('litespeed_control_set_ttl', function($value) {
    if ($value === 'rating_nonce') {
        return '0';
    }
});

Does it seem correct? That’s the way to prevent caching to an ESI nonce?

Thank you, sorry for the newbie, I want to continue learning

• This reply was modified 1 year, 5 months ago by hernan2022.
• This reply was modified 1 year, 5 months ago by hernan2022.

Yes, the truth sounds the most logical. Locating that file makes the load a little heavier and I have also noticed that Google distributes the located file to the visitor (for example, I have the server in Brazil, if I locate it on the server it is distributed to the rest of the world with references to Brazil, On the other hand, if I leave it as it is, each visitor receives the file with references to their own country)

All the tests I have done indicate that it is correct, the best thing is to simply exclude gtag from optimization and delay without locating it on the server

Thank you ! Greetings

I found the error, I simply had to enter the full Google url and clear the server and cloudflare cache. By doing this, the resource is consumed locally without generating duplicates.

Today it’s back to normal, I wouldn’t know what happened

Maybe if it happens again I should disable the automatic request cron? (to reduce the possibility of blocking)

But in any case, right now everything is working normally again

In another project I was able to transform to webp without problems

Will I have to wait the full month for it to restart? =(

(I have not filled the monthly or daily quota, I have not transformed for several days)

Please help

Today I tried again, the same message appears. Looks like I’ve definitely been left out.

Any advice or help is appreciated.

I have done more tests, with Cron disabled (manual transformations) an error message does appear that mentions that I do not have enough quota for this month

It’s been two days without being able to convert to webp, I’m far from my monthly maximum

I have reviewed the list of transformed files and it does not seem correct, transformations that were done several days ago appear as today’s date

Please help

• This reply was modified 1 year, 5 months ago by hernan2022.
• This reply was modified 1 year, 5 months ago by hernan2022.

Thank you so much. I will do it in a little more time, I can even provide a testing environment with the theme already prepared and documenting in detail how to induce the problem. I will prepare everything that can be useful

Thank you very much for the support