开始使用
Website Speed Audit - CWV Repair Plan

Website Speed Audit - CWV Repair Plan

Turn "the site feels slow" into a Core Web Vitals repair plan your team can execute. This download skill helps choose the right measurement surface, establish LCP / INP / CLS baselines, separate lab data from field data, classify root causes, ICE-rank fixes, and write each P0 action with verification method, expected metric movement, and a performance-budget guardrail. Built for conversion drops, launch regressions, and stakeholder pressure where a prettier Lighthouse score is not enough.
#营销#产品#分析
评分
需要更多评价
订单数
0
如何使用
下载

What This Agent Helps With

Website Speed Audit turns "the site feels slow" into a measured Core Web Vitals repair plan. It is built for teams dealing with mobile conversion drops, launch regressions, stakeholder pressure around performance, or Lighthouse reports that look busy but do not explain what to fix first.

What You Get

  • A measurement plan for PageSpeed Insights, Lighthouse, WebPageTest, Chrome DevTools, CrUX, GA4, and Search Console
  • Baselines for LCP, INP, CLS, TTFB, FCP, and speed index, with lab-vs-field caveats
  • Root-cause classification across image weight, render blocking, third-party scripts, server response, JavaScript cost, layout shifts, fonts, cache policy, and route/template issues
  • ICE-ranked P0 fixes with owner, expected metric movement, and verification method
  • A dated repair plan written to journal/speed-audits/{site-slug}-{YYYY-MM-DD}.md

Best For

  • Founders and marketers seeing conversion drop after a launch
  • Product managers turning vague "site is slow" complaints into a repair sprint
  • Frontend and growth teams prioritizing Core Web Vitals fixes
  • CRO or SEO teams that need speed recommendations tied to user experience, not vanity scores

Workflow

  1. Define the affected page, device, geography, and business symptom.
  2. Pick the right measurement surface and collect comparable lab and field signals.
  3. Classify speed issues by Core Web Vitals impact and likely user-visible friction.
  4. Prioritize fixes with ICE and separate quick wins from engineering work.
  5. Write a repair plan with verification gates and performance-budget guardrails.

Important Note

This is a download skill. Buyers run it locally with their own AI tool and paste observations, exports, screenshots, or measurements from their performance tools. It is not a hosted scanner and does not require the publisher to hold API keys.