web-performance-optimization▌
bobmatnyc/claude-mpm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Optimize web performance through Core Web Vitals, modern browser APIs (View Transitions, Speculation Rules), and framework-specific techniques.
Web Performance Optimization
Optimize web performance through Core Web Vitals, modern browser APIs (View Transitions, Speculation Rules), and framework-specific techniques.
When to Use This Skill
- Improving Lighthouse scores (target: 90+)
- Reducing page load times (target: <2.5s LCP)
- Optimizing Core Web Vitals for SEO rankings
- Implementing modern performance patterns (2025)
- Debugging performance bottlenecks
- Setting up continuous performance monitoring
Business Impact: 1 second delay = 7% conversion loss. 0.1s improvement = 8% increase in conversions.
Start Here: Quick Wins
High-ROI optimizations by time investment:
1 Hour Quick Wins (⭐⭐⭐⭐⭐ ROI):
- Add
loading="lazy"to below-fold images (40-60% weight reduction) - Enable compression (gzip/brotli) (70-80% transfer size reduction)
- Add
rel="preconnect"for critical origins (100-500ms savings)
1 Day Investments (⭐⭐⭐⭐ ROI):
- Implement code splitting (30-50% bundle reduction)
- Optimize LCP image with
fetchpriority="high"(200-400ms improvement) - Add basic service worker (instant repeat visits)
1 Week Comprehensive (⭐⭐⭐⭐⭐ ROI):
- Full caching strategy (HTTP headers + service workers)
- Bundle optimization (tree shaking, 40-60% reduction)
- Performance monitoring (Lighthouse CI + RUM)
→ See quick-wins.md for complete implementation details
Core Web Vitals at a Glance
| Metric | Target | Weight | Key Optimization |
|---|---|---|---|
| LCP (Largest Contentful Paint) | <2.5s | 25% | Optimize images, preload critical resources |
| INP (Interaction to Next Paint) | <200ms | 30% | Reduce JavaScript, break up long tasks |
| CLS (Cumulative Layout Shift) | <0.1 | 25% | Reserve space, optimize fonts |
| TBT (Total Blocking Time) | <200ms | 30% | Code splitting, defer non-critical JS |
| FCP (First Contentful Paint) | <1.8s | 10% | Eliminate render-blocking resources |
→ See core-web-vitals.md for deep dive on each metric
Modern Patterns (2025)
View Transitions API - Smooth page transitions without JavaScript
@view-transition { navigation: auto; }
Speculation Rules API - Prerender pages for instant navigation
React Server Components - Zero-bundle server components
Priority Hints - fetchpriority="high" for LCP optimization
Content Visibility - CSS-based rendering optimization
→ See modern-patterns-2025.md for cutting-edge techniques
Navigation
Quick Start (Load First)
- ⚡ Quick Wins - Time-boxed optimizations (1hr/1day/1week) with ROI ratings. Load FIRST for immediate impact.
Deep Dives
- 📊 Core Web Vitals - LCP, INP, CLS optimization strategies with debugging workflows. Load when targeting specific metrics.
- 🔧 Optimization Techniques - Image, JavaScript, CSS, resource loading, caching patterns. Load when implementing specific optimizations.
Modern Features
- ✨ Modern Patterns 2025 - View Transitions, Speculation Rules, RSC, Islands Architecture. Load when adopting cutting-edge patterns.
Framework-Specific
- ⚛️ Framework Patterns - Next.js, React, Vue, Vite, Astro, SvelteKit optimizations. Load for your framework.
Measurement & Monitoring
- 📈 Monitoring - Lighthouse CI, RUM setup, performance budgets, debugging tools. Load when setting up continuous monitoring.
Key Reminders
- Measure first, optimize second - Always baseline with Lighthouse/WebPageTest before changes
- Focus on user-centric metrics - Core Web Vitals > vanity metrics
- Test on real devices - 53% of mobile users abandon after 3 seconds
- Monitor continuously - Performance degrades over time without vigilance
- Prioritize by ROI - Start with Quick Wins (high impact, low effort)
Red Flags
Stop and reconsider if:
- Optimizing without baseline measurement
- Focusing only on Lighthouse score (ignoring field data)
- Ignoring mobile performance (53% abandon rate after 3s)
- Loading all resources eagerly (no lazy loading)
- No caching strategy implemented
- Third-party scripts loaded synchronously
- Missing performance monitoring/budgets
Integration with Other Skills
- nextjs-core - Next.js Image component, font optimization, static generation
- react - Component optimization, memoization, code splitting
- vite - Build optimization, chunk splitting
- typescript-core - Type-safe performance patterns
Real-World Impact
Conversion Impact:
- Pinterest: 40% faster perceived wait = 15% more sign-ups + 15% more SEO traffic
- Zalando: 0.1s improvement = 0.7% revenue increase
- AutoAnything: 50% faster load = 12-13% sales increase
SEO Impact:
- Core Web Vitals are ranking factors (June 2021+)
- 75% of users passing Core Web Vitals = ranking boost
- Mobile-first indexing prioritizes mobile performance
Remember: Performance is a feature, not an afterthought. Every millisecond counts. Start with Quick Wins for immediate impact.
How to use web-performance-optimization on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add web-performance-optimization
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches web-performance-optimization from GitHub repository bobmatnyc/claude-mpm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate web-performance-optimization. Access the skill through slash commands (e.g., /web-performance-optimization) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★64 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
web-performance-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Evelyn Kim· Dec 20, 2024
Solid pick for teams standardizing on skills: web-performance-optimization is focused, and the summary matches what you get after install.
- ★★★★★Olivia Johnson· Dec 20, 2024
Keeps context tight: web-performance-optimization is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Olivia Desai· Dec 16, 2024
Registry listing for web-performance-optimization matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ama Ndlovu· Dec 4, 2024
web-performance-optimization reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yusuf Taylor· Dec 4, 2024
web-performance-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chinedu Shah· Nov 23, 2024
Registry listing for web-performance-optimization matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aisha Okafor· Nov 23, 2024
Keeps context tight: web-performance-optimization is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Piyush G· Nov 19, 2024
Keeps context tight: web-performance-optimization is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yusuf Thomas· Nov 11, 2024
web-performance-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 64