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
If you’re a website owner, manager, or developer, you know to always check your website’s performance and design on both desktop vs mobile, especially since Google’s big drive for mobile-first. Google has even centred their 2021 Core Web Vitals around making sure that your website is efficient on mobile.
Google had a good reason to be pushing us to make sure our websites were mobile-friendly since it’s estimated that 61% of customers in the US now land on a website through a mobile device.
So with all of this focus on making sure your website:
- Works on mobile (at the very least)
- Loads just as fast as desktop
- Has mobile optimised content
- Passes Core Web Vitals
“The market share ratios of those OSs are Android 47.51%, iOS 41.97%, Symbian 3.31%, and Windows phone OS 2.57%. There are some other mobile OSs that are less used (BlackBerry, Samsung, etc.)”
According to sciencedirect.com
What are some of the fundamental ways that your website can change depending on the mobile and browser?
There’s a variety of things on your website that can be impacted depending on what the customer is using to look at your website. For example:
1. Screen size
If you’ve optimised your website for mobile and considered a “small screen” in relation to desktop, how do you know “one size fits all”? Your website content isn’t going to automatically fit all mobile screen types meaning you run the risk of vital content like CTAs being missed out/cut out or below the fold on mobile.
One way to check this is by using another of Google’s key tools (are you starting to see a theme here?) which is The Mobile-Friendly Test Tool. Alternatively, if you’re a developer use the “meta viewport” tag in the HTML.
2. Page speed and loading time
Your website loading time can affect everything from your conversions to your SEO rankings so getting it right on both desktop and mobile is a must. But it doesn’t stop there. You have to make sure that whatever browser someone could be using on mobile is also loading fast (i.e. less than 2 seconds). For example, iOS users tend to use Safari. How does your website load on mobile Safari on iOS vs desktop Safari?
How do I check this?
Firstly, check your overall page speed on mobile before you get more granular. If you can see that your website is very slow on mobile in general, you need to fix the significant factors before diving into browsers on mobile devices and which devices at that.
You can check by using Google’s Page Speed Insights which will show you the speed of your website loading, if it “passes” Core Web Vitals, and what areas need to be worked on like LCP.
Once you’ve checked this, you can use Google Analytics to go more granular.
3. Responsiveness of visual content
If your website is super responsive on Chrome on desktop, you’re winning! If it’s super responsive on iOS on Safari, you’ve nabbed a large majority of your audience. But what if Microsoft Edge isn’t working on mobile?
Responsiveness is not a given. That is the key thing to remember and the only way you will know if there’s an issue is to test, test, test. If you’re using a CMS system that allows you to pick a “theme”, you should be able to see in its description whether it’s considered responsive across all devices.
Other tips include making sure videos are responsive on mobile, images are compressed, and table data is responsive on mobile.
These are just 3 examples of how a lack of mobile optimisation can affect your customer engagement with your website.
If you want full website monitoring to ensure your website is loading fast, and not continuously experiencing website downtime, sign up to StatusCake for free. It’s genuinely free!
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