INP profiler
Real-user CrUX field data from Google. INP, LCP and CLS at p75 over the last 28 days, mobile and desktop side by side. The first call to a URL can take up to a minute as Google warms its cache.
Pulling field data from CrUX (this can take 30 to 60 seconds)...
How to read these numbers
INP: Interaction to Next Paint
How long it takes from a user tapping or clicking before they see a visual response. Good is < 200 ms. Needs improvement is 200–500 ms. Poor is > 500 ms. 43% of sites silently fail this metric in 2026, almost always because of hydration cost in React or Next.
LCP: Largest Contentful Paint
When the largest visible element finishes rendering. Good is < 2.5 s. Most sites that pass Lighthouse but fail real-user data are losing to LCP-on-slow-mobile.
CLS: Cumulative Layout Shift
How much the layout jumps around as the page loads. Good is < 0.1. Caused by images without width/height, late-loaded ads, custom fonts swapping.
Mobile and desktop are different stories
CrUX collects data separately by form factor. Most sites are 30–50% slower on mobile. Look at both. The mobile numbers are what affects most of your traffic and your rankings.
If you see "no field data"
Your URL needs enough real-user traffic for Google to publish CrUX data for it. New pages, niche pages, and low-traffic sites may show "n/a". For those, lab data from Lighthouse is the next best signal.
Failing INP? That's our web-dev side.
We fix INP issues in React, Next and Nuxt builds for clients on a regular basis. Hydration analysis, scheduler.yield() rollout, third-party script audits. Usually 2–4 week engagements.