- Home
- Skills
- Agents & Orchestration
- web performance regression detective
web performance regression detective
Detects, classifies, and prioritizes web performance regressions by correlating metrics with deployment changes.
$5
Works with the AI Agents you already use
web performance regression detective
Example session with this skill installed
Compare baseline (LCP 2100ms, CLS 0.05) to current (LCP 3800ms, CLS 0.25) after deploying hero-v2.jpg and updating analytics.js. Prioritize the fixes.
- Read your context and instructions
- Compiled the web performance regression
Detected Regressions
- CLS (0.05 -> 0.25): Significant. Suspected: hero-v2.jpg. Impact: High (SEO/Bounce risk).
- LCP (2.1s -> 3.8s): Significant. Suspected: hero-v2.jpg size. Impact: Medium.
Priority Fix: Optimize hero-v2.jpg to WebP and set explicit dimensions to resolve CLS.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Manual performance audits often fail to distinguish between random network noise and actual code regressions. Developers waste hours chasing minor metric fluctuations while critical Core Web Vitals issues slip into production undetected.
What it does
- Analyzes metric snapshots to identify statistically significant performance regressions in LCP, FID, CLS, and TTI.
- Correlates performance drops with specific deployments, asset updates, or third-party script changes.
- Scores and ranks remediation tasks based on user impact, business risk, and implementation effort.
- Generates structured re-verification plans including target metrics and synthetic monitoring tasks.
Why this beats prompting it yourself
General-purpose prompts often treat every metric increase as a bug. This skill uses specific statistical thresholds and heuristic mapping to filter out noise, ensuring you only alert the team for regressions that actually impact SEO and conversion rates.
Use cases
- Post-deployment sanity checks to catch layout shifts or bundle size bloat.
- Third-party dependency monitoring to detect slow external scripts.
- Prioritizing technical debt by quantifying the conversion risk of specific performance bottlenecks.
Known limitations
Requires accurate input metrics, as missing data leads to false classifications. Root cause detection is heuristic-based and may require manual verification for complex infrastructure issues.
Requires structured metric data. Root cause identification is based on correlation and may require manual investigation for complex system inter-dependencies.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
No special permissions declared or detected