Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Why is avoiding mixed content on your pages important?
Mixed content occurs when the site is accessed over a HTTPS secure connection, but other resources on the page are loaded through an insecure connection. This is defined as “Mixed Content” as both HTTP and HTTPS content are being loaded on the same page when the request started as a secure HTTPS request.
In most cases, users will receive a warning from their browser to indicate that this is the case when visiting the site.
5.7% of Sites are Impacted
StatusCake Sample Size of 100,000 URLs
To protect the integrity, security, and secrecy of your data where necessary. It’s required that all resources be served over a HTTPS connection. If there’s a single resource on any given page that’s not secured in this way then your users will be informed that the page is not fully secure upon visiting.
Having a fully secured page will assure your users of the following facts:
- Visitors can be sure of the identity of the website.
- Visitors can be sure that nobody has tampered with the data they send and receive.
- Visitors can be sure that nobody unauthorized can view the data that they send and receive.
The Solution
With StatusCake you can now ensure that none of your pages contain Mixed Content, we’ve built this functionality into our SSL monitoring feature, so you can now be alerted the moment anything of this nature is found.
It’s important to note that mixed content will only be detected by us on the page you are testing, so a test on your homepage’s URL for SSL will not detect mixed content on other pages of the website. If you want to test more than one page then multiple tests would be required. Also worth remembering is that resources requested from scripts or within iframes will not be checked.
The option is enabled by default for all SSL testing as it’s an essential thing to watch out for – and alerting will fire automatically for any SSL tests that currently have a contact group. If you do not have a contact group attached to your SSL test it’s just a case of adding one and then entering the settings to select the “Mixed Content” check box.
For information on how to use the feature please check out our Knowledgebase article here.
StatusCake Team
Share this
More from StatusCake
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026