Digging a bit deeper I can see this in console:
Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unauthorized code on your site.
To solve this issue, avoid using eval(), new Function(), setTimeout([string], ...), and setInterval([string], ...) for evaluating strings.
If you absolutely must: you can enable string evaluation by adding unsafe-eval as an allowed source in a script-src directive.
<meta http-equiv="Content-Security-Policy" content="script-src 'self' 'unsafe-eval';">
⚠️ Allowing string evaluation comes at the risk of inline script injection.
Affected Resources
1 directive
Source location: frame-boot.js?ver=1.11:48
Directive: script-src
Status: blocked
Does this provide anymore clues?
