The playbook
Core Web Vitals: Metrics and Measurement
Measure Core Web Vitals by defining field experience by page group precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Largest Contentful Paint concerns loading the main visible content, Interaction to Next Paint concerns responsiveness, and Cumulative Layout Shift concerns visual stability. Investigate the responsible element or interaction. Use field observations for real-user conditions and laboratory tests to diagnose particular changes.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | field experience by page group |
| Unit | What one page or query record or completed outcome represents |
| Included records | The scope identified by template and metric |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | analytics owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as review field data separately from laboratory tests. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For Core Web Vitals, explain the condition before applying that calculation. If the question is whether the team can test focused changes without breaking functionality, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If metric changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying template records are complete.
- Look for this known failure: treating a single lab score as a complete user-experience measure.
- Verify that the process still includes: find the page elements contributing to poor experiences.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, compare representative field results and functional checks over time. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about field experience by page group, not a favorable-looking number.
Keep page purpose visible throughout the work. A technically valid page can still fail to answer the reader’s question. Separate access and discovery problems from content problems so that the assigned action matches the cause.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now