Core Mobile Vitals: What Web Performance Teams Should Know (and What to Monitor Today)

Sponsors ask for "mobile vitals" in one breath. Your portfolio probably mixes responsive sites, WebViews, and native iOS or Android screens. The metrics behind that phrase depend on where the user actually loads content.

Google's Core Web Vitals apply to pages in Chrome. Embrace and SpeedCurve are promoting Core Mobile Vitals as a user-focused framework for native apps. Those are different lanes. Mobile CWV still means LCP, INP, and CLS on a phone form factor. CMV is an emerging native vocabulary organised around Screen Load, Smoothness, Responsiveness, and Stability. There is no Google-style public threshold table for CMV yet.

What web teams can monitor this quarter:

• Mobile web URLs: field LCP, INP, and CLS on a mobile strategy beside desktop, with scheduled lab runs when CrUX volume is thin.

• Hybrid WebViews: mobile CWV on the URL plus native traces for shell navigation.

• Native screens: keep vendor RUM or APM; map informal pillar goals when the app team adopts CMV, without inventing pass bands in contracts.

Apogee Watcher sits on the web and mobile-web layer: scheduled PageSpeed tests, vitals budgets, and portfolio alerts. It does not replace a native SDK. Layer tools instead of forcing one blended mobile score.

Read more: Core Mobile Vitals for web performance teams