Docs Security
No mixed content
Checks that an HTTPS homepage does not load scripts, stylesheets, images or frames over plain http:// addresses.
What it checks
We read the homepage HTML and look for addresses that start with http:// in four places: stylesheet links, <script src>, <img src> and <iframe src>.
Other places, such as srcset, video sources, CSS background images, fonts and files added by JavaScript, are not checked. If the homepage itself is on plain HTTP, this check passes, because the HTTPS check already covers that.
- PassNone of those resources use http://, or the page is not on HTTPS.
- FailAt least one resource loads over http://.
Why it matters
Browsers block insecure scripts, stylesheets and frames on HTTPS pages, and current browsers try to upgrade insecure images and drop them if that fails. Either way, part of the page goes missing or breaks, and the browser may stop showing the page as fully secure.
How to fix it
Change each http:// address to https://. First check the file is really available over HTTPS; if it is not, host a copy yourself or find another source.
Old addresses often sit inside content saved in the database, in theme settings, or in pasted embed codes, so search all three.
Platform notes
Use a search and replace tool, or WP-CLI's search-replace command, to change old http:// addresses in the database. Take a backup first.
Automatic HTTPS Rewrites can rewrite http:// links to resources that are known to work over HTTPS. The check reads the page as Cloudflare delivers it, so rewritten links count as fixed.
Mixed content on these platforms usually comes from custom code, embeds or images pasted with http:// addresses. Check custom code blocks and embed widgets.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.