Secure page loads at least one insecure (http://) resource
A mixed-content issue happens when a page loaded securely over https:// also loads a resource, like an image, script, or stylesheet, over the insecure http:// address. This check found this site loading at least one http:// subresource on an otherwise HTTPS page.
Why this matters
Browsers commonly block or warn about mixed content, and even when they don't fully block it, it degrades the security indicator visitors see in their address bar, undermining the trust signal HTTPS is meant to provide to every visitor who checks it.
How to fix it
Your developer should update every http:// reference in the page's code to https://. If a specific third-party asset genuinely isn't available over HTTPS, host a copy of it yourself or replace it with an equivalent that is. Budget around an hour depending on how many references are affected.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit