Technical guide
Website performance: field data and lab tests
A lab test, such as Lighthouse, measures one simulated visit on one device. Field data measures what real visitors experienced over the last 28 days. Google’s Core Web Vitals assessment uses field data at the 75th percentile. Use the lab to find and verify fixes, and the field to judge whether real users got faster.
The three measures
| Measure | What it captures | Good |
|---|---|---|
| LCP | How fast the main content appears | 2.5 s or less |
| INP | How quickly the page responds to input | 200 ms or less |
| CLS | How much the layout jumps | 0.1 or less |
Why the numbers disagree
- The lab uses one simulated phone and network; your visitors use many.
- Field data lags: it covers the last 28 days, so fixes take weeks to show.
- Low-traffic pages may have no field data at all.
- INP needs real interaction, so labs approximate it.
Prioritising fixes
- Fix the templates with the most visits first.
- For LCP: size and preload the main image, cut render-blocking scripts.
- For CLS: reserve space for images, ads and banners.
- For INP: break up long JavaScript tasks and delay non-essential scripts.
Report lab and field results separately. A local Lighthouse score is not proof of real-user performance.
Sources
Primary references this guide relies on. Provider documentation changes, so check the source before acting.
Questions
Search Console’s Core Web Vitals report and PageSpeed Insights, when your site has enough traffic.
Ready to talk through your project?
Send a voice note, spreadsheet or a plain description of where your business is struggling. We’ll help you find the right next step.

