Web Performance Optimization
ListedHelps with web development, performance optimization, optimization as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bobmatnyc/claude-mpm-skills --skill web-performance-optimization -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bobmatnyc
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: www.webpagetest.org.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
www.webpagetest.orgundeclaredWhat it found
- universal/web/web-performance-optimization/references/monitoring.md:675contacts www.webpagetest.org
curl "https://www.webpagetest.org/runtest.php?url=https://example.com&k=YOUR_API_KEY&f=json"
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bobmatnyc/claude-mpm-skills at 718070a7d6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 718070a7d6
- Scanned
- 8 files, 6,041 lines
About this skill
What it does
This skill enables AI agents to analyze and improve the loading speed, responsiveness, and overall efficiency of web applications. It focuses on identifying performance bottlenecks and implementing strategies to reduce render-blocking resources and optimize asset delivery.
When to use it
- Diagnosing slow Time to Interactive (TTI) or First Contentful Paint (FCP) metrics in production environments.
- Optimizing large-scale e-commerce sites where image and script loading delays impact conversion rates.
- Reducing Cumulative Layout Shift (CLS) by analyzing resource loading order and sizing attributes.
- Preparing websites for Core Web Vitals updates to ensure search engine ranking stability.
Key capabilities
- Analyzing network waterfall data to identify render-blocking resources.
- Recommending code splitting and lazy loading strategies for JavaScript bundles.
- Optimizing image formats, compression, and delivery methods (e.g., WebP, AVIF).
- Evaluating CSS critical path extraction opportunities.
Example prompts
- "Analyze this React application's Lighthouse report and suggest specific changes to improve its Largest Contentful Paint score."
- "Identify render-blocking resources in this HTML file and propose a refactoring plan to prioritize above-the-fold content."
- "Optimize the image delivery strategy for this landing page to reduce Total Blocking Time by at least 30%."
Tips & gotchas
Ensure you have access to real-world performance data (e.g., Lighthouse, WebPageTest) before asking for optimization strategies, as generic advice may not address specific bottlenecks. Always test changes in a staging environment first, as aggressive optimizations like code splitting can introduce new runtime complexity if not implemented carefully.