A website is opened in a browser via HTTPS but is not shown as "secure".
- The certificate is valid;
Page source code contains links to non-secure resources, for example:
CONFIG_TEXT: <link rel="stylesheet" type="text/css" href="http://www.example.com/css/style.css" />
The website has mixed content. In other words, even if the website is loaded over HTTPS some of the files for the website are loaded over HTTP.
In case of a WordPress site, WordPress HTTPS add-on can be installed. Although WordPress HTTPS does its best to fix all insecure content, there are a few cases that are impossible to fix. Here are some typical examples.
- The element is external (not hosted on the server) and is not available over HTTPS. These elements will have to be removed from the page by disabling or modifying the theme or plugin that is adding the element.
To identify what is causing the page(s) to be insecure on the website, follow the instructions below:
In a web-browser, open the page, that is having issues.
Open the Developer Tools (F12).
Switch to the Console tab.
For each item that is making the page partially encrypted, it is required to see an entry in the console similar to “The page at https://www.example.com/ displayed insecure content from http://www.example.com/.” Note that the URL that is loading insecure content is HTTP and not HTTPS.
Once the insecure elements are identified, review the website code, e.g. figure out what theme or plugin is causing these elements to be loaded.