Mixed Content Checker
Find insecure http:// images, scripts and styles on an HTTPS page.
About the Mixed Content Checker
Mixed content happens when an HTTPS page loads some resources over plain HTTP. Browsers block active mixed content (scripts, stylesheets, iframes) outright, which can break layouts and features, and they upgrade or warn about passive content such as images. Either way, the padlock can disappear and visitors may see warnings.
It usually appears after moving a site to HTTPS, when old content still contains hard-coded http:// URLs. This checker lists every insecure resource on the page, including CSS background images and form actions, so you can update them to https://.
Frequently asked questions
How do I fix mixed content?
Change resource URLs to https:// (or relative paths). In WordPress, a search-and-replace tool can update URLs in the database. Adding the CSP directive upgrade-insecure-requests is a quick safety net.
Does mixed content affect SEO?
Indirectly. Broken features and security warnings hurt user experience and trust.
Why does a resource still load over HTTP?
It may come from a theme setting, a plugin, a third-party widget or content saved in the database with absolute http:// URLs.