What is mixed-content?

To put this simply, the term “mixed content” means the website you’re visiting is served securely (using “https”protocol) but if you look closely you will soon find out that it itself is requesting content over non-secure connections (“http”) in some (or even worse all) cases.
It is a common mistake as it’s not that difficult to have these two different HTTP and HTTPS protocols at the same time. Yet in this case mixed content warning will be displayed and browsers display warning messages into the console and remove green lockers to indicate to the users of your website. It will always scream that this web contains some insecure content and it is not nice.

Why is it better to have this problem solved?

Even though it is common, it is not great to have mixed content on your website. First of all the scripts (it can also be images or styles) you are loading over http become a gateway for man-in-the-middle attacks (the main thing SSL tries to prevent in the first place). Also having some mixed content on your page causes browsers to show a “not secure” warning to your users or visitors. In many cases browsers will simply block outgoing non-secure requests and you can definitely see why it's not a great thing to have on your web!

How to fix mixed content problems?

In theory it’s a simple task: just change all the URLs in your website to begin with “https”. Sounds great and easy, but in practice, it’s not so simple to find and change all those tricky hidden links as well as the resource you’re loading may not be available over https. It is even more difficult to do it if you do not know that you have any mixed content in there.
Trust your good friend Linko and mixed content check will be effortless and simple!