Fail

The HTTPS page loads scripts or styles over HTTP

The short version

Load every script, stylesheet and frame over https://.

What it means

Your home page is served over HTTPS but loads at least one script, stylesheet, frame, form target or plugin over plain http://. The result lists the elements and their addresses.

Why it matters

Browsers block this active mixed content, so those scripts and styles simply don't load and the page may look or work broken. Where they did load, anyone on the network could change them and take over the page. Browsers also stop showing the padlock.

How to fix it

  1. Change each listed address to https://. Most hosts serve the same file over HTTPS.
  2. Use relative paths (/js/app.js) for files on your own site.
  3. Search your templates and database for http:// links to your own domain; a site moved to HTTPS often keeps old absolute links, for example in WordPress content.
  4. If a third-party host has no HTTPS, host the file yourself or replace it.
  5. Add Content-Security-Policy: upgrade-insecure-requests as a safety net.

Check it worked

Run the standard files check again. No active mixed content should be listed, and the finding should be gone.