Ask Claude to Diagnose and Fix Your Core Web Vitals
Poor Core Web Vitals — LCP, CLS, INP — hurt both user experience and search rankings, but reading the Chrome DevTools waterfall and knowing what to fix isn't obvious. Paste your data and let Claude interpret it.
Grab your vitals from the Chrome DevTools Performance panel or PageSpeed Insights and share them:
Here's my PageSpeed Insights report for the home page. LCP is 4.2s and CLS is 0.18.
Analyse the data and tell me the top three things I should fix first,
and show me the specific code changes needed.
[paste JSON export or key metrics here]
Claude will identify root causes — render-blocking scripts, missing width/height on images, layout shifts from late-loading fonts, third-party scripts delaying interactivity — and write the actual fixes, not just advice.
For Next.js or Nuxt projects, ask Claude to audit your components specifically:
Review @pages/index.tsx for Core Web Vitals issues.
I'm seeing high CLS — look for any elements that load without reserved dimensions,
late-injected content, or fonts without a fallback stack.
Suggest and apply the fixes.
Core Web Vitals are a diagnostic puzzle, not a checklist — Claude is good at connecting the symptom in the score to the specific line of code that caused it.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.