Mobile vs Desktop Core Web Vitals: Why You Need to Monitor Both

Most teams treat Core Web Vitals like one scoreboard. They run a quick test, pick a single set of scores, and move on. The problem is that Core Web Vitals are defined per page load ; device shows up in how you measure—mobile versus desktop in lab emulation, or in field data grouped by form factor. The same URL can therefore produce different LCP, INP, and CLS results across those contexts. Mobile and desktop travel different routes through your UI, assets, network conditions, and interaction patterns. If you monitor only one side, you will miss regressions that matter—and you will struggle to justify prioritisation when clients ask, “Why did this change?” The trap: one device, one story It’s easy to fall into a workflow like this: Mobile is “important”, so you track mobile CWV only. Desktop is “nice to have”, so you leave it until later. When something breaks, you re-run tests and pick the latest scores to explain the incident. This approach has two predictable failure modes: Hidden re