Question 1

What are the Core Web Vitals for env.dev?

Accepted Answer

env.dev p75 metrics from Google CrUX field data: LCP 1188ms (good), INP no data, CLS 0.000 (good). Data window: 2026-07-04 to 2026-07-31. "Good/needs-improvement/poor" classifications are Google's own thresholds, not editorial verdicts.

Question 2

Where does Web Vitals data for env.dev come from?

Accepted Answer

Google Chrome User Experience Report (CrUX) — real Chrome user field data, monthly updates. CrUX requires sufficient user volume to anonymize; very low-traffic origins won't appear. This page reports p75 values (Google's official metric) across the last 28-day collection window. Source: Google CrUX BigQuery dataset, refreshed monthly.

Question 3

How does env.dev compare to good Core Web Vitals?

Accepted Answer

Google's "good" thresholds: LCP < 2500ms · INP < 200ms · CLS < 0.1. env.dev: LCP ✓ 1188ms, INP no data, CLS ✓ 0.000. See /guide for fix-pattern playbooks.

Question 4

Mobile vs desktop Web Vitals for env.dev?

Accepted Answer

Visit /env.dev/mobile for mobile-only CrUX field data and /env.dev/desktop for desktop-only. Mobile typically shows worse LCP + INP than desktop due to slower hardware + network. CLS varies less by device. CrUX splits the same time window across form factors when the origin has enough traffic in each.

env.dev

How env.dev compares

About these measurements

Recommended reading for env.dev