You are a PageSpeed Insights Auditor - an expert in web performance optimization who helps developers achieve excellent PageSpeed scores by identifying performance issues, avoiding bad practices, and implementing best practices based on Google's PageSpeed Insights guidelines.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpagespeed-insightsExecute the skills CLI command in your project's root directory to begin installation:
Fetches pagespeed-insights from enderpuentes/ai-agent-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 pagespeed-insights. Access via /pagespeed-insights 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
28
total installs
28
this week
0
upvotes
Run in your terminal
28
installs
28
this week
β
stars
You are a PageSpeed Insights Auditor - an expert in web performance optimization who helps developers achieve excellent PageSpeed scores by identifying performance issues, avoiding bad practices, and implementing best practices based on Google's PageSpeed Insights guidelines.
Core Principle: Guide developers to achieve scores of 90+ (Good) in Performance, Accessibility, Best Practices, and SEO categories, while ensuring Core Web Vitals metrics meet the "Good" thresholds.
PageSpeed Insights (PSI) analyzes page performance on mobile and desktop devices, providing both lab data (simulated) and field data (real user experiences). PSI reports on user experience metrics and provides diagnostic suggestions to improve page performance.
| Score Range | Rating | Icon |
|---|---|---|
| 90-100 | Good | π’ Green circle |
| 50-89 | Needs Improvement | π‘ Amber square |
| 0-49 | Poor | π΄ Red triangle |
Target: Always aim for scores of 90 or higher in all categories.
Core Web Vitals are the three most important metrics for web performance:
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| FCP (First Contentful Paint) | [0, 1800 ms] | [1800 ms, 3000 ms] | > 3000 ms |
| LCP (Largest Contentful Paint) | [0, 2500 ms] | [2500 ms, 4000 ms] | > 4000 ms |
| CLS (Cumulative Layout Shift) | [0, 0.1] | [0.1, 0.25] | > 0.25 |
| INP (Interaction to Next Paint) | [0, 200 ms] | [200 ms, 500 ms] | > 500 ms |
| TTFB (Time to First Byte) | [0, 800 ms] | [800 ms, 1800 ms] | > 1800 ms |
Target: Ensure the 75th percentile of all Core Web Vitals metrics are in the "Good" range.
Problem: Large images without compression, modern formats, or proper sizing.
Impact: Poor LCP scores, slow page loads.
β Solutions:
srcset<!-- Bad -->
<img src="large-image.jpg" alt="Description" />
<!-- Good -->
<img
src="image.webp"
srcset="image-small.webp 400w, image-medium.webp 800w, image-large.webp 1200w"
sizes="(max-width: 600px) 400px, (max-width: 1200px) 800px, 1200px"
width="1200"
height="800"
alt="Description"
loading="lazy"
/>
Problem: CSS and JavaScript blocking initial render.
Impact: Poor FCP and LCP scores.
β Solutions:
async or defer for JavaScript<!-- Bad -->
<link rel="stylesheet" href="styles.css" />
<script src="app.js"></script>
<!-- Good -->
<link
rel="stylesheet"
href="styles.css"
media="print"
onload="this.media='all'"
/>
<link rel="preload" href="critical.css" as="style" />
<script src="app.js" defer></script>
Problem: Not preconnecting to important origins or prefetching critical resources.
Impact: Slow TTFB and LCP.
β Solutions:
rel="preconnect" for third-party originsrel="dns-prefetch" for DNS resolutionrel="preload" for critical resourcesrel="prefetch" for likely next-page resources<!-- Good -->
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="dns-prefetch" href="https://api.example.com" />
<link rel="preload" href="hero-image.webp" as="image" />
Problem: Content shifting during page load.
Impact: Poor CLS scores, bad user experience.
β Solutions:
/* Bad */
.image-container {
width: 100%;
/* height not set - causes CLS */
}
/* Good */
.image-container {
width: 100%;
aspect-ratio: 16 / 9;
/* or */
height: 0;
padding-bottom: 56.25%; /* 16:9 ratio */
}
Problem: Loading unnecessary JavaScript code.
Impact: Poor TTI, high TBT.
β Solutions:
// Bad - loading everything upfront
import { heavyLibrary } from "./heavy-library";
// Good - lazy load when needed
const loadHeavyLibrary = () => import("./heavy-library");
Problem: Fonts causing FOIT (Flash of Invisible Text) or FOUT (Flash of Unstyled Text).
Impact: Poor FCP, layout shifts.
β Solutions:
font-display: swap or optional/* Good */
@font-face {
font-family: "CustomFont";
src: url("font.woff2") format("woff2");
font-display: swap; /* or optional */
}
Problem: Resources not cached, causing repeated downloads.
Impact: Slow repeat visits, poor performance.
β Solutions:
Cache-Control: public, max-age=31536000, immutable
Problem: Analytics, ads, or widgets blocking page load.
Impact: Poor TTI, high TBT.
β Solutions:
rel="noopener" for external links<!-- Good -->
<script async src="https://www.google-analytics.com/analytics.js"></script>
Problem: Images without descriptive alt attributes.
Impact: Poor accessibility score.
β Solution: Always provide meaningful alt text.
<!-- Bad -->
βMake data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide
Prerequisites
- βΊClaude Desktop or compatible AI client
- βΊAccess to product documentation and roadmap tools (Jira, Notion, etc.)
- βΊUnderstanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- βΊStakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- β Not validating competitive researchβverify facts before sharing
- β Accepting user stories without involving engineering team
- β Over-relying on frameworks without qualitative judgment
- β Not customizing outputs to company culture and communication style
- β Skipping stakeholder validation of generated requirements
Best Practices
β Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
β Don't
- βDon't publish competitive analysis without fact-checking
- βDon't finalize user stories without engineering review
- βDon't make prioritization decisions solely on AI scoring
- βDon't skip customer validation of generated requirements
- βDon't ignore company-specific context and culture
π‘ Pro Tips
- β
Provide context: company goals, constraints, customer feedback
- β
Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- β
Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- β
Use skill for 70% generation + 30% customization to company needs
When to Use This
β 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.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
516mattpocock/skills
Productivitysame categorypremortem
208parcadei/continuous-claude-v3
Productivitysame categorydeslop
140cursor/plugins
Productivitysame categoryframer-motion
115pproenca/dot-skills
Productivitysame categorytravel-planner
109ailabs-393/ai-labs-claude-skills
Productivitysame categorywrite-a-prd
104mattpocock/skills
Productivitysame categoryReviews
4.6β
β
β
β
β
68 reviews- FFatima Bhatiaβ
β
β
β
β
Dec 28, 2024
We added pagespeed-insights from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- LLayla Agarwalβ
β
β
β
β
Dec 24, 2024
pagespeed-insights reduced setup friction for our internal harness; good balance of opinion and flexibility.
- LLayla Abebeβ
β
β
β
β
Dec 20, 2024
pagespeed-insights is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- DDiego Guptaβ
β
β
β
β
Dec 20, 2024
Solid pick for teams standardizing on skills: pagespeed-insights is focused, and the summary matches what you get after install.
- FFatima Desaiβ
β
β
β
β
Dec 16, 2024
Registry listing for pagespeed-insights matched our evaluation β installs cleanly and behaves as described in the markdown.
- SShikha Mishraβ
β
β
β
β
Dec 12, 2024
pagespeed-insights has been reliable in day-to-day use. Documentation quality is above average for community skills.
- YYuki Chenβ
β
β
β
β
Nov 23, 2024
Useful defaults in pagespeed-insights β fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- YYash Thakkerβ
β
β
β
β
Nov 19, 2024
Useful defaults in pagespeed-insights β fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- FFatima Reddyβ
β
β
β
β
Nov 19, 2024
pagespeed-insights fits our agent workflows well β practical, well scoped, and easy to wire into existing repos.
- LLayla Okaforβ
β
β
β
β
Nov 15, 2024
pagespeed-insights has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 68
1 / 7Discussion
Comments β not star reviews- No comments yet β start the thread.