With more and more people moving to use SSL on their sites for improved security or just to get brownie points from Google, the issue of insecure connections will begin to become more commonplace. Insecure connections can be caused by a number of factors, such as expired certificates, but the most common issue will likely be mixed content types (secure and insecure elements on the same page).
Mixed content connections present themselves with a missing or broken padlock in the browser’s address bar. This won’t just impact the savvy or observant web surfer but may even trigger browser or antivirus warnings that will result in lost website traffic or sales.
So what causes the broken or missing padlocks in your browser?
How do I find these insecure calls?
You could search through your website’s templates, CSS, and content manually but that could take an incredible amount of time. And you will probably end up pulling your hair out trying to find out why your secure page is not fully secure.
Or you could just use Why No Padlock and get an instant report identifying the insecure elements in your page for you.
How do I fix these insecure calls?
If you have some web smarts, it’s just a matter of updating the URLs of insecure elements to use HTTPS instead of HTTP. If digging into your website’s code isn’t your cup of tea, contact your Webmaster or Virtual Assistant.
Or WordPress users may want to try the “SSL Insecure Content Fixer” plugin from the WordPress Plugin Directory though we highly recommend fixing your issue the old fashioned way as it doesn’t make a lot of sense to use a plugin instead os setting up your site correctly.