Mixed Content Warnings on HTTPS
Your site loads securely over HTTPS, yet the padlock shows a warning or is missing. This is often a mixed content issue, where the page itself is secure but some items on it — perhaps an image or script — are still loading insecurely.
Browsers flag this because a single insecure item can undermine the whole page's protection. The fix is to make sure everything loads over HTTPS, and this guide explains how.
Why It Happens
Mixed content usually creeps in from older links and embedded resources.
- An image or file linked with
http://instead ofhttps://. - An embedded video or widget loading insecurely.
- A hard-coded link left over from before HTTPS was enabled.
- A stylesheet or script from an insecure source.
How to Spot the Culprit
These steps help narrow down which item is at fault.
- Note which page shows the warning.
- Look for recently added images, videos or embeds.
- Check whether the warning appears on every page or just one.
- Send us the page address so we can scan it.
How We Resolve It
We can run an automatic scan that finds every insecure resource and update the links to HTTPS, or apply a rule that upgrades them site-wide. This restores the full padlock for every visitor.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.