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
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
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026