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
Website page speed has become more important than ever, especially now Google’s Core Web Vitals are pushing mobile-first and penalising websites it deems to be “too slow”. This means that there is a direct link between slow page speed and lower SEO rankings, and therefore potentially, less traffic to your website. It’s not just SEO you have to worry about, Google has even suggested that your ads on both mobile and desktop could be impacted if your landing pages are loading too slowly.
But it’s not only Google that is punishing slow page speed, website visitors are becoming more and more impatient with slow loading times, meaning they’re bouncing straight off and going elsewhere. But what is the optimum page speed for your website, and more pressingly, how do you achieve it?
“If your site loads in 0.8 seconds, it is faster than approximately 94% of the web”
https://www.semrush.com/blog/how-to-improve-your-google-pagespeed-insights-score/
What we mean by page speed
It’s easy to forget that there are a plethora of different elements working in the background to load a website and its many pages. So when we say, “a fast page speed”, it sounds as though this is something that is automatic, or at least, very simple. This couldn’t be further from the truth. Websites have to load each and every page, and on those pages, each and every aspect of them. There’s so much that needs to be loaded in such a short space of time that getting it right can prove extremely difficult for most website owners.
What can impact page speed
There are plenty of things that can impact a website’s page speed. Here are just three ways:
- Poor CMS system – if you have a high volume of unused plugins having to load continuously, this could make your website very slow
- Unneeded/unused code is a very typical reason for slow page speed
- Too many large images/videos trying to load on a singular page or multiple pages across your website
It’s important to note that every user will experience your website differently, even when it comes to loading time. This could be because they’re on a different browser, for example, Chrome might load your website far faster than Firefox.
What Google says about page speed
Google suggests that your website load time should be less than 2 seconds, meaning any website slower than this is going to start seeing its SEO impacted.
But why are Google so focused on page speed?
“Optimized web experiences lead to higher user engagement, conversions, and ROI; performance is a feature and a competitive edge.”
https://developers.google.com/web/updates/
They’ve gone so far as to build the tool Page Insights, helping you to identify slow loading pages on your site quickly so you can do something about them. The best part is, this tool will tell you which part of your website is causing the slowness i.e. the Largest Contentful Paint.
Our blog on Core Web Vitals explains LCP a little further:
It’s important to note, however, that there are several factors that can influence LCP load time. These include:
- Slow loading resources on the page that should be optimised by compressing text, resizing images etc.
- Render-blocking JavaScript and CSS can slow download times, so you want to reduce CSS blocking time by minifying your CSS, deferring non-critical CSS and inline critical CSS.
- Slow server response times means that a browser waits longer to receive content from the server. You can use TTFB (Time to First Byte) to measure response times and improve your TTFB by optimising the server, routing to a CDN, using signed exchanges and caching assets.
StatusCake and page speed monitoring
Page Insights is a great tool for manual page by page checking of your website. We provide something different with automated monitoring with fast check rates that allow you to see when your website is loading slowly and more importantly why. This gives you the chance to rectify the situation before it damages your brand, and your potential traffic. Want to know more? You can sign up for a free for life account or trial our Superior plan for free today!
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