Get Velonic
PRACTICAL GUIDE

PageSpeed Insights: why field data and lab scores disagree

Understand the report's real-user and simulated sections, missing field data and how to verify a recent performance change.

Velonic resource library · Published 3 October 2026 · 2 min read

Use lab results to investigate a change and field data to understand the visitors represented in the report.

Read the two sections separately

PageSpeed Insights combines simulated Lighthouse results with real-user data from CrUX when enough data exists. Field results cover a trailing 28-day period. A lab run describes a particular test, so a change made today does not instantly replace the historical experience summarized above it.

Check the scope of the field result

Record whether the report shows data for the tested URL or the whole origin. When there are not enough samples for a page, the tool may use origin-level data or show no field data. A quiet new page with no field report has not automatically passed or failed the visitor-experience test.

Build a before-and-after record

Save the report URL, test date, device mode, individual metrics and environment information. Run the same page several times in comparable conditions. Record a range rather than selecting the highest score. A visual improvement or faster menu should also be checked directly; the score alone does not describe every user task.

Interpret a recent change carefully

After improving a page, use lab evidence to see whether the targeted behavior changed. Continue observing field data as new visits enter its collection period. If the origin contains many templates, do not attribute an origin-wide result to one edited hero. Keep the scope and date beside every number used in a report.

Choose the next investigation

A slow loading metric points toward delivery and rendering evidence. A responsiveness problem needs interaction testing. Layout movement needs observation during the visit. Use the metric to choose a question, then collect the relevant trace or reproduction. This workflow prevents repeated changes based only on an overall score.

Put it into practice

  • Distinguish lab and real-user sections.
  • Record URL-level versus origin-level scope.
  • Keep comparable repeated runs.
  • Allow for the field-data collection period.
  • Investigate the metric tied to the actual symptom.

AI-assisted educational content prepared for the Velonic resource library. How these guides are prepared.

All performance articlesVelonic documentation
ORDER PREVIEW

Your next gear.

Sold and supported by Host & Tech · hostandtech.com

Demo checkout. No payment is collected and no license is issued. Final seller details, taxes and payment accounts must be configured before launch.

Terms · Refunds & cancellation