Performance
wp-cwv-field-triage
Trace WordPress Core Web Vitals
Traces poor WordPress Core Web Vitals from field data to the plugin, theme, setting or third-party tag responsible.
- Area
- Performance
- Checked against
- WordPress 7.1.2, web-vitals 6.2.2
- Last verified
- 26 September 2026
- Files
- SKILL.md, 9 references, 4 scripts
How it works
- 1Establish field evidence by page, device, metric and time period.
- 2Split the failing metric into the parts that explain where time or movement comes from.
- 3Collect real-user attribution when the existing field data lacks an owner.
- 4Map scripts, images, handles and elements to plugins, themes, core or third parties.
- 5Check WordPress causes that match the failing metric part.
- 6Confirm suspects on staging by changing one thing and repeating the same lab test.
- 7Propose approved fixes, then verify the result with field data.
Use it when
- Find what causes poor LCP, INP or CLS on WordPress.
- Investigate a Core Web Vitals regression.
- Decide whether to configure, replace or remove a measured component.
- Check whether a fix improved field performance.
How it stays safe
- Starts read-only and asks for approval before each site change.
- Tests changes on staging before production.
- Keeps API keys in the user's shell and leaves credentials out of output.
- Labels each suspected owner as Confirmed, Likely or Hypothesis based on the evidence.
Install it
Copy the whole wp-cwv-field-triage folder into your agent's skills folder, not only SKILL.md.
git clone --depth 1 https://github.com/hamzaahmadaslam/agent-skills.git
cp -R agent-skills/wp-cwv-field-triage "<your agent's skills folder>/"