This article explains how to fix mixed content errors that cause security warnings on your HTTPS website.
What Are Mixed Content Errors?
Mixed content errors happen when your website uses HTTPS (secure) but loads some files like images, videos, or scripts using HTTP (not secure). This creates a security warning in browsers and can prevent parts of your website from working properly.
You'll see these issues as:
- "Not Secure" warnings in the browser
- Missing padlock icon in the address bar
- Broken images or missing content
- Browser console errors mentioning "mixed content"
Finding Mixed Content Issues
Step 1: Check Your Browser
- Open your website in Google Chrome or Firefox
- Right-click anywhere on the page and select "Inspect" or "Inspect Element"
- Click the "Console" tab at the top
- Look for red error messages mentioning "mixed content" or "blocked loading"
- These errors will show you which files are causing problems
Step 2: Check the Address Bar
- Look at your website's address bar
- If you see a warning icon instead of a padlock, click it
- The browser will tell you what content is not secure
Fixing Mixed Content Errors
Method 1: Update URLs in WordPress
- Log into your WordPress admin dashboard
- Go to "Settings" then "General"
- Make sure both "WordPress Address" and "Site Address" start with "https://" (not "http://")
- Save the changes
- Clear your browser cache and check your site again
Method 2: Fix Images and Media
If specific images aren't loading properly:
- Go to "Media" in your WordPress dashboard
- Click on any image that's not displaying correctly
- In the URL field, change "http://" to "https://"
- Update the file
- Repeat for all affected images
Method 3: Check Your Content
- Edit the pages or posts with missing content
- Look for any links, images, or embedded content that start with "http://"
- Change these to "https://" or remove the "http://" part entirely
- Update the page
Method 4: Plugin Conflicts
Some plugins can cause mixed content issues. If the above steps don't work, you may have a plugin conflict that needs resolving.
Checking Your Fix
- Clear your browser cache completely
- Visit your website in a private/incognito browser window
- Check that the padlock icon appears in the address bar
- Verify all images and content load correctly
- Test on different devices and browsers
If you're still stuck after trying these steps, contact Web60 support. Include details about which pages show errors and what your browser's console messages say.
FAQ
Q: Why does my website sometimes show "Not Secure" even with SSL?
A: This happens when some content on your page loads using HTTP instead of HTTPS. All content must use HTTPS for the secure padlock to appear.
Q: Will mixed content errors affect my Google rankings?
A: Yes, Google considers HTTPS a ranking factor. Mixed content issues can negatively impact your search engine visibility.
Q: Can I ignore mixed content warnings?
A: No, these warnings reduce visitor trust and some browsers will block insecure content entirely, breaking your website's functionality.
Q: Why do mixed content errors happen after switching to HTTPS?
A: Old content often contains hardcoded HTTP links. When you switch to HTTPS, these links become mixed content that browsers flag as insecure.
Q: Do mixed content errors affect website speed?
A: Yes, browsers may block or delay loading mixed content, which can slow down your website and create a poor user experience.
Q: How can I prevent mixed content errors in future?
A: Always use relative URLs (without http:// or https://) when linking to content on your own website, and ensure any external links use HTTPS.
Q: What's the difference between active and passive mixed content?
A: Active mixed content (scripts, stylesheets) gets blocked by browsers completely. Passive mixed content (images, videos) may load but still triggers security warnings.
Last updated: 1 March 2026