Free Core Web Vitals checker: lab numbers versus what users get
A lab measurement and your real users' experience are different numbers, and only one of them affects ranking. Here is how to read both.
By Sapun Lamichhane · Arcetis
Core Web Vitals are three measurements of how a page feels: how long until the main content appears, how quickly it responds to interaction, and how much it moves around while loading. They are ranking factors, and more importantly they are the difference between a visitor staying and leaving.
Lab and field are different questions
A lab measurement is a single simulated visit under controlled conditions. Field data is what actually happened to real people on real devices and connections. They frequently disagree, and both are correct.
The distinction that matters: ranking uses field data. Lab data is a diagnostic — its value is telling you which element is responsible, which script is blocking, which image is oversized. Use lab numbers to find causes, and field data to decide whether you have a problem worth solving.
This is also why a lab score varies between runs. Network conditions and server load move it, and a swing of several points between consecutive measurements is ordinary rather than a fault in the tool.
Largest Contentful Paint
How long until the largest element above the fold renders. On most pages that element is one image or one heading, and identifying which is 90% of the work.
- Preload it, and never lazy-load it. Lazy-loading the LCP element is the single most common self-inflicted performance wound.
- Serve it in a modern format at the size it is actually displayed.
- Remove render-blocking resources ahead of it in the load order.
Cumulative Layout Shift
How much the page moves while loading. The cause is almost always content arriving without reserved space.
- Set explicit width and height on every image and video.
- Reserve space for anything injected after load — banners, ads, cookie notices.
- Preload web fonts so text does not reflow when they arrive.
Interaction to Next Paint
How quickly the page responds when someone interacts. Poor INP is nearly always JavaScript occupying the main thread when the user taps.
Break long tasks into smaller ones, defer anything not needed for the first interaction, and be sceptical of third-party scripts, which are the usual cause and the least examined.
What free means here
Our performance checker is free, with no account needed for your first full scan. It measures on the live rendered page rather than estimating, names the element responsible for your LCP, and states plainly that lab numbers vary between runs — a tool that hid that variance would be easier to trust and worse to use.