Search results and measurement
Field data: meaning, examples and practical use
Field performance data comes from measurements observed during actual visits, such as loading, interaction and layout behavior. It reflects diverse real devices and networks but applies only to the population covered by the measurement system.
Also known as: Valós felhasználói adatok
At a glance
- Field data comes from actual visits.
- Coverage, period and device grouping are necessary context.
- A new fix does not instantly replace historical observations in an aggregate report.
On this page

Which conditions does it capture?
Visitors have different phones, networks, cache states and behaviors. A single average can therefore mislead. Core Web Vitals assessment uses percentiles and appropriate grouping to understand how many experiences meet a target.
Where can the observations come from?
Your own real-user measurement or a source such as the Chrome User Experience Report. Coverage and aggregation can differ between systems. Comparing lab and field data therefore requires more than placing two numbers side by side.
Example: a fast office test and slower phones
Imagine a team viewing its site on powerful laptops over wired connections. Some actual visitors use less capable phones and receive a slow main image. Field observations can reveal that experience; the office test does not represent those visitors by itself.
What does the aggregate not explain?
A summary does not necessarily identify the file or task causing a delay. Laboratory testing and technical investigation may still be needed. Check the reporting window: a few visits after a fix do not immediately replace the entire earlier sample. Separate a completed deployment from demonstrated improvement for the measured population.