Goal
A short list of the fixes that will move this page from failing to passing, in the order a developer should do them.
Inputs
- Page URL and type: [e.g. home page, product page, blog post]
- Field data from the report: [LCP, INP and CLS at the 75th percentile, mobile and desktop, or "not enough data"]
- Lab data and diagnostics: [paste the opportunities and diagnostics sections]
- LCP element named in the report: [e.g. hero image, heading text]
- Site platform and constraints: [e.g. WordPress with a page builder, custom React app, cannot change hosting]
Steps
- State which metrics pass and which fail, using field data first and lab data only when field data is missing.
- For each failing metric, find the likely cause in the pasted diagnostics.
- Match each cause to a specific fix for this platform.
- Rank fixes by expected effect against effort.
Output format
- | Metric | Field value | Lab value | Threshold | Pass or fail |
- Ranked fixes: | Rank | Metric | Cause from the report | Change to make | Effort (low, medium, high) | Expected effect |
- Fixes to skip for now, with the reason.
- How to confirm the result: what to retest, and that field data takes about 28 days to update.
Check before answering
- Thresholds are correct: LCP 2.5 s, INP 200 ms, CLS 0.1, all at the 75th percentile.
- Every cause is taken from the pasted report, not from a generic speed checklist.
- Fixes name the element, file type or script involved.
- No promise of a ranking gain; speed is one signal among many.






