Mixed content is an HTTPS page that asks for something over plain HTTP — a script, a stylesheet, an image. Browsers upgrade images, audio and video to HTTPS where they can and block the rest, so the page loses its styling or features, and the padlock can turn into “Not secure”.
Mixed Content: The page at 'https://example.com/' was loaded over HTTPS, but requested an insecure script 'http://example.com/app.js'. This request has been blocked; the content must be served over HTTPS.
How 3 other clients word the same error
Chrome, for an image it upgraded
Mixed Content: The page at 'https://example.com/' was loaded over HTTPS, but requested an insecure element 'http://example.com/logo.png'. This request was automatically upgraded to HTTPS
Chrome, for a form
Mixed Content: The page at 'https://example.com/' was loaded over a secure connection, but contains a form that targets an insecure endpoint 'http://example.com/subscribe'. This endpoint should be made available over a secure connection.
Firefox
Blocked loading mixed active content “http://example.com/app.js”
| Error | Mixed Content: … was loaded over HTTPS, but requested an insecure … |
| Usually fixed by | The website |
| Shown in | The browser console; the address bar may say “Not secure” |
| Upgraded to HTTPS | Images, audio, video (Chrome 86, Firefox 127) |
| Blocked | Scripts, stylesheets, frames, fetch(), fonts |
Check the certificate a site serves
Mixed content is in the page itself: open the browser’s developer console (F12) to see each insecure address. Check here that the site’s certificate and HTTPS are sound first.
What it means
Content that cannot change the rest of the page — images, audio, video — is “upgradable”: current browsers quietly request it over HTTPS instead, and it breaks only if the file is not available there. Everything else — scripts, stylesheets, iframes, fetch() and XHR, web fonts — is blocked outright, because an attacker could change it in transit.
Chrome marks the page “Not secure” only when insecure content actually loaded; blocked or upgraded requests do not change the padlock. A form that posts to an http:// address also stops the page counting as secure.
Why it happens
- Hard-coded http:// addresses in the page, the theme or the content.
- A site moved to HTTPS whose database still holds the old http:// addresses (WordPress keeps them in posts and options).
- A third-party script, font or widget loaded from its http:// address.
- A form whose action is an http:// address.
How to fix it
- Open the browser’s developer console on the page and read the Mixed Content lines: each names the insecure address.
- Change those addresses to https:// (or to relative paths), and use the HTTPS versions of third-party resources.
- On WordPress, set both the WordPress Address and Site Address to https:// (Site Health offers an “Update your site to use HTTPS” button), then replace old http:// addresses in the database with WP-CLI search-replace — not a raw database replace, which breaks serialised data.
- As a safety net, send Content-Security-Policy: upgrade-insecure-requests, which makes the browser request every http:// resource over HTTPS — it fails without fallback for anything not available over HTTPS, and it does not replace HSTS.
Questions
Does Cloudflare’s Always Use HTTPS fix mixed content?
No. It redirects visitors to HTTPS, but it does not change the addresses inside your pages. Cloudflare’s Automatic HTTPS Rewrites can rewrite some of them, but not those loaded by JavaScript or CSS.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Mixed content — developer.mozilla.org
- Mixed content blocking in Firefox — support.mozilla.org
- HTTPS — Advanced Administration Handbook — developer.wordpress.org
- Mixed content errors — developers.cloudflare.com