Monitoring
Status Pages
Pricing
Over the past few weeks we’ve been looking at feature requests on our Page Speed monitoring feature, and today we’ve released the next phase which introduces a wide range of improvement and new functionality.
One of the most frequent requests we’ve had is giving our customers the ability to ensure that Page Speed testing does not affect users’ analytics stats.
To address this we’ve added both the ability to not load code from common trackers like Google analytics by default and also a function which will include a DNT (Do Not Track) header with all outgoing requests, meaning users will no longer need to add custom filters within their analytics accounts in order to exclude this traffic.
Another big request was that users would like to be able to define the connection type that’s used for the Page Speed monitoring. We now allow you to select one of the following options in-app for your Page Speed tests, and the normal speeds are still available as the default option:
Next, we’ve added the ability to set the screen resolution and view type for the Page Speed test, this allows you to simulate tests from different devices/screen sizes. Both desktop and mobile variants are offered, and you can see the current options below:
You can now set a custom user agent which can be useful for accessing pages with certain restrictions, and also if for any other reason you’d prefer not to use our default user agent: StatusCake_Pagespeed_Indev
Our final update to the Page Speed monitoring feature is the ability to send custom headers with the test, again this will enable testing on sites where this was not previously possible.
If you’d like to learn more about Page Speed testing check out our Knowledgebase here.
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
