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



There are many ways of testing if your website is up but here at StatusCake we believe in the power of real browser testing. So what exactly is real browser testing? Traditionally website monitoring services load your websites HTML content via a simple communication method (sometimes wget, sometimes CURL), they simply pull the HTML but do not render it. This means none of the images are loaded, no remote content is pulled in and the only thing you’re actually testing is whether your webserver can deliver some HTML in a reasonable speed. Without rendering the website monitoring isn’t testing what a real visitor to your site would see and feel but rather what a brainless crawler would.
This is where Real Browser Testing comes into play. Rather than using the simple text based communication methods to do our HTTP testing we use what is called a full stack – that is to say our advanced systems literally open up a browser window and navigate to the URL you are monitoring and then waits for the entire page contents to download. This means every image, every bit of CSS and every line of JavaScript, our test scripts act like a real person and see like a real person.
What advantage does this have? Well firstly you can be sure the speeds your seeing are not that just of your HTML but your entire page loading, so you’ll be able to tell if for some reason your site was loading slowly at a set time (say for example – a CDN that you use for images became slow), this ability to see real time speed implications allows you to understand if you need to add more resources to your server at certain times to improve visitor satisfaction.
Real Browser Testing also allows our robot to be wiser in detecting issues. When your page gets stuck loading due to an erroneous javascript redirect then we can alert you – and if your site is setting a cookie based redirect loop we can also let you know about that!
Real Browser Testing takes a little more bandwidth but offers a lot more in terms of data relevance – and for those times you don’t need Real Browser Testing you can simply switch it off! We offer the Real Browser Testing functionality in all our packages, from free all the way up to business so really you have no reason not to get most more relative uptime monitoring!
Share this
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
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
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
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
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
Find out everything you need to know in our new uptime monitoring whitepaper 2021