When LCP Moves and Nobody Deployed: Browser Release Cadence and Your 28-Day Field Window

Tuesday's PageSpeed Insights field band for LCP looks worse than last week. The release calendar is empty. Staging is quiet. The account manager still gets the "what did we ship?" email.

CrUX is a 28-day rolling average of real Chrome sessions. From Chrome 153 Stable on 8 September 2026, Chrome also moves to a two-week Stable cadence, so one field window can blend more than one browser major with different paint behaviour. An amber band after a quiet week is often population mix (who updated Chrome, which channel they use), not proof that engineering shipped a regression on Tuesday.

We already separate pipeline lag from rolling-window fix lag. The third clock agencies rarely label is browser release cadence inside the field window. When nobody deployed but field LCP drifts, you need browser rows on the same calendar as app, CDN, and tag changes, sample thresholds before you slice by Chrome major, and scheduled lab runs as same-week proof that the origin did not change.

• Put Chrome Stable (and Extended Stable where it matters) on the same release calendar as deploys.

• Keep unsegmented LCP, INP, and CLS as the retainer headline; treat Chrome-major slices as appendix diagnostics with sample counts.

• Pair field collectionPeriod dates with scheduled lab runs on money URLs.

• Escalate on code when lab budgets break or lab and field move together after a deploy; investigate population mix when lab is flat across a Stable line.

Read more: when LCP moves with nobody deployed: browser release cadence and the 28-day field window