Error best practices in page speed

Hey, thank you for the bug report, but this part is an external tawk.to API.
I'm not sure if it is possible to handle this in the module, I'll try to check their API, maybe, there are some changes here.

So, it isn't directly connected to this module or to the tawk.to chat.
Generally, it is more about CORS and security. In order to avoid this issue you should update your CORS configuration on the server.
Sorry, but it is the only way.
Something like this should work:

Access-Control-Allow-Origin: https://embed.tawk.to

You can try this module https://www.drupal.org/project/cors_ui → and configure in Allowed Origins related host.

Let me know if this helped.

https://stackoverflow.com/a/72211930
https://github.com/ticgal/jsaddons/issues/3

@Andriy Khomych I'm sorry to reopen the topic but even google page speed keeps showing errors in cors I followed the recommendations you gave for nginx and the cors_ui module, although maybe I'm not configuring something well in that module

@Nelo_Drup, sorry, I cannot help here.
The module is just rendering tawk_to according to their manual.
I've used it before and had no issues.
Attached example of no CORS error at my local instance.

@Nelo_Drup, by the way I'm postponing an issue, maybe, you can collect more information.

@Andriy Khomych The module works perfectly with the latest improvements that were made to it, it shows that it has improved a lot but when you can try google page speed there you will see that problem is not serious and does not affect use, if not by following the recommendations of gogole page speed

@Nelo_Drup, yeah, thanks, as I said I cannot help here - it requires a direct connection and trying to update/fix the server side.
As you can see from my screenshot no CORS error is in the console.
If you look at this issue https://www.drupal.org/project/tawk_to/issues/3222887 💬 Tawk to widget blocked by CORS policy Closed: outdated
It was about the same error.

@Nelo_Drup, I checked the issue once more using page speed. Well, despite no error in the browser it still is in the page speed report.
At this point, I cannot say what can be done. It is possible to play with tawk_to load script and postpone it for 5-10 seconds or provide such an option, which could help with resolving an issue, but it isn't an issue from this module.
Another option that I see is to contact tawk_to support and discuss the issue directly with them.
From my point of view, it sounds like a wrong warning in the page speed, because no such error in the browser.

@Andriy Khomych Exactly the same if or I can make it work in pagespeed I will comment here

any updates on this cors?
how to defere loading as an alternative