web-perf

Analyze web page performance with Chrome DevTools MCP to measure Core Web Vitals.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/FabioFiorita/tastik --skill web-perf-fabiofiorita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-perf
Source: https://github.com/FabioFiorita/tastik/tree/main/.agents/skills/web-perf
Command: npx skills add https://github.com/FabioFiorita/tastik --skill web-perf-fabiofiorita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web performance auditing is essential for delivering fast, reliable experiences. This skill provides a structured approach to measure Core Web Vitals, identify render-blocking resources, and diagnose network and caching issues using Chrome DevTools MCP.

Core Features & Use Cases

  • Core Web Vitals measurements (FCP, LCP, TBT, CLS, Speed Index) to quantify user-perceived performance.
  • Resource and network analysis to identify render-blocking assets, dependency chains, and caching gaps.
  • Guided workflows for audits, profiling, debugging, and optimization, with actionable recommendations and repeatable checks.

Quick Start

Navigate to the target page and start a performance trace to collect metrics.

Frequently Asked Questions about web-perf

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

FAQPage Schema
How do I measure Core Web Vitals and identify render-blocking resources on my site?

You can measure Core Web Vitals and identify render-blocking resources by running a performance trace using Chrome DevTools MCP. This skill analyzes metrics like FCP, LCP, and CLS to pinpoint assets and dependency chains slowing down your page.

What's the best way to audit web performance bottlenecks across multiple pages?

To audit web performance bottlenecks across pages, use guided workflows that navigate to each target URL and collect performance insights. This approach provides repeatable checks and actionable recommendations for each location.

Do I need a configured MCP server to run web performance diagnostics?

Yes, you need a configured MCP server to run web performance diagnostics. This skill relies on Chrome DevTools MCP commands like navigate_page and performance_start_trace to collect metrics and generate diagnostics.

Can I use Chrome DevTools to profile site speed and debug Lighthouse scores?

Yes, you can use Chrome DevTools to profile site speed and debug Lighthouse scores. The skill leverages DevTools MCP to measure Total Blocking Time, Speed Index, and other metrics to diagnose network and caching issues affecting your results.

Why does my page have a slow LCP and how can I diagnose the network issues?

A slow LCP often stems from network and caching gaps or render-blocking assets. By running a performance trace and analyzing resource dependencies, you can diagnose the exact network issues causing the delay.

What specific metrics are analyzed during a web performance trace?

A web performance trace analyzes Core Web Vitals including First Contentful Paint, Largest Contentful Paint, Cumulative Layout Shift, Total Blocking Time, and Speed Index to quantify user-perceived performance and locate bottlenecks.