Desktop works. Mobile is broken.
Responsive bugs can leave desktop healthy while mobile users see overflow, missing buttons and unusable navigation.
By Ștefan P
In this article · 6 sections
There is no single version of your website.
A customer opening your site on a laptop and another opening it on an iPhone may receive the same URL but very different interfaces.
That is why a desktop screenshot cannot prove your mobile site is healthy.
Responsive bugs are production bugs
A CSS change can leave desktop untouched while breaking one breakpoint completely.
For example:
@media (max-width: 768px) {
.checkout-actions {
display: none;
}
}The desktop monitor sees the checkout button.
The mobile customer does not.
Everything else can remain healthy.
The server returns 200. JavaScript loads. TLS is fine.
The problem exists entirely inside the rendered layout.
Common mobile-only failures
Some of the most frustrating responsive bugs are surprisingly small:
- a CTA pushed outside the viewport;
- horizontal overflow;
- navigation that opens behind another layer;
- fixed headers covering content;
- text clipped by a container;
- buttons hidden by a sticky element;
- forms wider than the screen;
- modals impossible to close.
None require the server to fail.
The same page needs separate expectations
Visual monitoring only works if the comparison is meaningful.
A mobile screenshot should be compared with an accepted mobile baseline.
A desktop screenshot should be compared with desktop.
Otherwise the monitoring system is comparing two layouts that were intentionally designed to be different.
Witch keeps the viewports separate for exactly this reason.
DOM and visual evidence work better together
A visual difference might tell you that something moved.
A DOM signal can tell you that the expected element disappeared.
A failed resource might explain why.
Combined evidence is much more useful than a screenshot saying:
23.4% differentbecause a percentage is not a diagnosis.
Test the interface users actually receive
Responsive design is not a cosmetic layer placed on top of a website.
For many products, mobile is the product.
If a navigation button disappears or checkout becomes unreachable on a small screen, infrastructure health does not matter much to the affected customer.
Monitoring should reflect that.
Witch can monitor desktop and mobile independently, keeping visual evidence and browser signals for each viewport.