Comprehensive Core Web Vitals audit with root-cause diagnosis and resource optimization guidance.
Works with
Covers five key metrics (LCP, CLS, INP, FCP, TTFB) with diagnostic trees that pinpoint specific causes like slow servers, missing image dimensions, font loading issues, and main-thread blocking
Includes structured resource analysis breaking down HTML, CSS, JavaScript, images, fonts, and third-party script sizes against industry benchmarks
Provides prioritized fix recommendations ordered
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaudit-speedExecute the skills CLI command in your project's root directory to begin installation:
Fetches audit-speed from calm-north/seojuice-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate audit-speed. Access via /audit-speed in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
5
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
5
stars
Deep Core Web Vitals audit with root-cause analysis trees and resource optimization recommendations.
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5s | 2.5s - 4.0s | > 4.0s |
| CLS (Cumulative Layout Shift) | < 0.1 | 0.1 - 0.25 | > 0.25 |
| INP (Interaction to Next Paint) | < 200ms | 200ms - 500ms | > 500ms |
| FCP (First Contentful Paint) | < 1.8s | 1.8s - 3.0s | > 3.0s |
| TTFB (Time to First Byte) | < 800ms | 800ms - 1800ms | > 1800ms |
Gather this context:
If no data is available, suggest running Google PageSpeed Insights on the key URLs.
LCP measures when the largest visible element finishes rendering. Diagnose:
Is TTFB slow (> 800ms)?
Is the LCP element an image?
width/height attributes, use fetchpriority="high" on LCP image, preload the LCP imageIs the LCP element text?
font-display: swap or optional, preload critical fonts, subset fonts to used charactersIs render-blocking CSS/JS delaying the LCP?
<head>, synchronous JS before contentCLS measures unexpected layout shifts. Diagnose:
Do images/videos lack dimensions?
width and height attributes to all <img> and <video> elements, use CSS aspect-ratioDo ads or embeds inject content?
contain-intrinsic-size for lazy contentDo fonts cause text reflow?
font-display: optional (no swap = no shift), or match fallback font metricsDoes dynamic content insert above the fold?
INP measures responsiveness to user interactions. Diagnose:
Is the main thread blocked by long tasks?
requestIdleCallback or setTimeout, code-split heavy modulesDo event handlers do heavy synchronous work?
Are third-party scripts competing for the main thread?
loading="lazy" for embeds, consider removing low-value scriptsBreak down the total page weight:
| Resource Type | Size | Assessment | Action |
|---|---|---|---|
| HTML | [x] KB | [ok/large] | Compress, reduce inline styles/scripts |
| CSS | [x] KB | [ok/large] | Remove unused CSS, minify, critical CSS extraction |
| JavaScript | [x] KB | [ok/large] | Code-split, tree-shake, defer non-critical |
| Images | [x] KB | [ok/large] | Modern formats, responsive sizes, lazy load below fold |
| Fonts | [x] KB | [ok/large] | Subset, limit families/weights, preload critical |
| Third-party | [x] KB | [ok/large] | Audit necessity, defer, self-host if possible |
Benchmarks:
Core Web Vitals
| Metric | Value | Rating | Root Cause |
|---|---|---|---|
| LCP | [value] | Good / Needs Improvement / Poor | [identified cause] |
| CLS | [value] | ... | ... |
| INP | [value] | ... | ... |
| FCP | [value] | ... | ... |
| TTFB | [value] | ... | ... |
Resource Breakdown [Table from Resource Analysis]
Priority Fixes
For each failing metric, ordered by impact:
[Metric]: [Root cause]
...
Quick Wins List optimizations that require minimal effort:
width/height to imagesfetchpriority="high" on LCP imagePro Tip: Use the free CWV Impact Calculator to estimate the traffic impact of fixing Core Web Vitals, and the Critical CSS Generator to extract above-the-fold CSS. SEOJuice MCP users can run
/seojuice:page-audit [domain] [url]for instant CWV scores, Lighthouse data, and resource breakdowns.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in audit-speed — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for audit-speed matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: audit-speed is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in audit-speed — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added audit-speed from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
audit-speed is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
audit-speed reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: audit-speed is focused, and the summary matches what you get after install.
audit-speed is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend audit-speed for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 51