One-click install
npx skills add https://github.com/mynameistito/opencode-config --skill web-perf-mynameistito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-perf
Source: https://github.com/mynameistito/opencode-config/tree/main/skills/web-perf
Command: npx skills add https://github.com/mynameistito/opencode-config --skill web-perf-mynameistito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually identifying web performance bottlenecks, render-blocking resources, layout shifts, and accessibility gaps is time-consuming and prone to oversight, leading to poor user experience, high bounce rates, and lower search engine rankings. This Skill automates the end-to-end performance audit process to quickly surface actionable issues.

Core Features & Use Cases

  • Core Web Vitals Measurement: Accurately measures FCP, LCP, TBT, CLS, and Speed Index against official Google thresholds to assess page performance.
  • Network & Resource Analysis: Identifies render-blocking resources, network dependency chains, missing preloads, caching misconfigurations, and oversized uncompressed payloads.
  • Accessibility Gap Detection: Flags high-level accessibility issues including missing ARIA IDs, poor contrast ratios, and missing focus indicators.
  • Use Case: For a SaaS product page with a 4.2s LCP score, use this Skill to trace the performance bottleneck, identify unoptimized hero images and render-blocking CSS, and get prioritized fixes to bring LCP under the 2.5s good threshold.

Quick Start

Use the web-perf skill to audit the performance of your public website https://your-site.com and receive a prioritized list of fixes to improve its Core Web Vitals scores and page load speed.

Frequently Asked Questions about web-perf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit web performance and improve Core Web Vitals?

You can audit web performance by analyzing page load behavior to identify bottlenecks like render-blocking resources and layout shifts. This skill measures metrics like FCP and LCP against Google thresholds to provide prioritized fixes for improving Core Web Vitals.

Why does my page have a slow LCP and how do I trace the bottleneck?

A slow LCP is often caused by unoptimized hero images or render-blocking CSS. By capturing performance traces and analyzing network requests, you can trace the bottleneck and receive actionable insights to bring LCP under the 2.5s threshold.

What's the best way to identify render-blocking resources and network dependency chains?

The best way to identify render-blocking resources is to capture performance traces and analyze network dependency chains. This process flags missing preloads, caching misconfigurations, and oversized uncompressed payloads that degrade page speed.

Do I need the Chrome DevTools MCP server to debug slow page speed?

Yes, you need access to the Chrome DevTools MCP server to debug slow page speed. It is required to capture performance traces, analyze network requests, and extract accessibility snapshots for actionable optimization insights.

Can I detect accessibility gaps like poor contrast ratios during a performance audit?

Yes, you can detect accessibility gaps during a performance audit by extracting accessibility snapshots. This flags high-level issues including missing ARIA IDs, poor contrast ratios, and missing focus indicators alongside web performance metrics.

Does web performance optimization work for both internal and public websites?

Web performance optimization applies to auditing both public and internal websites. By profiling page load behavior and measuring Core Web Vitals, it resolves bottlenecks to improve user experience and search engine rankings across site types.