Mixed Content Warning
Your site has SSL, but some pages still show "Not Secure" or a broken padlock because they load insecure images, scripts, or files.
Common signs of this issue
- The site has https:// but the padlock is broken or shows "Not Secure" on some pages.
- Certain images, fonts, or scripts don't load on the secure version.
- Browser tools mention "mixed content" or "insecure resources."
- It started after switching the site to https.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Note which pages show the warning — often it's only pages with an embedded item (a map, video, slider, or pasted image).
- Look for content loaded from
http://instead ofhttps://— that's the root of "mixed content." - Check whether it appeared right after enabling SSL; older content often still points to the insecure address.
- Try viewing the page in a private window to rule out a cached old version.
- If you recently embedded something from another site, test removing it temporarily to see if the warning clears.
What this usually means
The page itself loads securely, but it pulls in one or more items over an insecure connection. Browsers flag the whole page as not fully secure until every item loads over https.
This is common right after moving a site to https, when older links and embeds still point to http addresses.
What not to do
- Don't ignore it — visitors still see a "Not Secure" signal that erodes trust.
- Don't strip out SSL to "make the warning go away"; that's the wrong direction.
- Don't bulk-edit the database to swap addresses without a backup.
When to get help
Clearing mixed content is usually a tidy, contained task — finding the insecure items and updating them. If it's spread across an older site, a helper can fix it in one pass safely with a backup in place.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
I have SSL — why "Not Secure"?
Because something on the page (an image, script, or embed) still loads over insecure http. The browser flags the whole page until every item is secure.
Will this hurt my site?
It undermines visitor trust and can block some content from loading. It's worth clearing, though it's usually a straightforward fix.