Identify the field data and its exact scope
Know whose experience a number describes.
Use this for: The representative public pages selected for this review.
Run an important public page through PageSpeed Insights and look first at the real-user section. Check whether the report describes the URL itself or the whole origin, meaning the shared protocol and hostname. Keep mobile and desktop results separate.
Note the shown collection period and available metrics. An origin result cannot establish that every page template performs the same way. If field data is unavailable, keep that status explicit and use lab tests to investigate; missing data is not a good result.
Hypothetical example: A new product URL shows origin-level field data. The team uses it as site context and tests the product template separately instead of calling that URL passed.
- Open the real-user section for the selected URL.
- Identify URL versus origin, device and collection period.
- Keep unavailable metrics distinct from measured results.
More help and optional notes
If it fails: Correct the scope labels before prioritizing fixes.
Retest: Recheck the scope whenever another URL or report is used.
Not applicable: No pages or features in the stated scope require this check.
Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

