Unfortunately, this is not the first time I have had discussions of this type with your technical support. 6 months ago I had to spend 2 weeks to make you understand (with evidence in hand) that Webp pages were being compressed by your caching solution and not by my site.
Honestly I'm tired of hearing that the problem is the site. In fact it's a good excuse when it comes to 2layer applications.
The site has 98% of the core vitals as reported in the first message. The problem is not the site.
The problem is the myriad of EZOIC scripts that are injected into it and are not customizable and manageable and make the site heavier, reducing performance by over 50% and every 3 months we need to get back on it because google console reports that all the pages are not optimized, like the image shown in the attachment.
I recommend that you find a way to allow your clients to have full autonomy over your scripts.
Please, given that a meeting was held at the entrance to activate DNS integration and prevent the site from being unreachable, is it possible to hold the same meeting to eliminate integration?