We noticed that you have a non-standard setup where the container and privacy templates are loaded asynchronously only in response to first user’s interaction. Is it set up in this way on purpose? If not, I would advise to modify that mechanism so that the container is always instantly fetched and initiated on each page.
When it comes to point 1 and 3 - could you try using auto margins and let me know if this fixes your issue?
Hi, thanks for your prompt reply. I think the container loading issue can be that we are using a performance optimization plugin. However, when I implemented the code in practice on our cookie policy page, the code was not in the first screen view, so that fixed the problem as people needed to scroll to see it. Cookie Policy | Enea
I also fixed the issue with the cut off on mobile by limiting the width to 350 px which actually work well also for desktop I think. So, I am good now. Thanks for your help and analysis.