Why does this happen?
Your site is configured to restrict one or more security policies through a Content-Security-Policy header and doesn't explicitly permit access to CrazyEgg.
Solving the Error
Ask your developer to add policies allowing script, connect and image access to *.crazyegg.com in the Content-Security-Policy header.
- Add *.crazyegg.com to default-src.
- If you have specific directives for script-src, connect-src, and/or img-src, also add *.crazyegg.com to each of those that are present.