performance-eval

Evaluate front-end web performance using Core Web Vitals and RAIL model analysis.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cjohnhanson/codelikecody --skill performance-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-eval
Source: https://github.com/cjohnhanson/codelikecody/tree/main/skills/performance-eval
Command: npx skills add https://github.com/cjohnhanson/codelikecody --skill performance-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Front-end performance evaluation helps teams diagnose and fix UX latency by analyzing metrics, rendering behavior, and anti-patterns to deliver faster, more reliable applications.

Core Features & Use Cases

  • RAIL model guidance for designing interaction budgets.
  • Core Web Vitals analysis including LCP, INP, CLS interpretation and thresholds.
  • Evaluation workflows covering data gathering, budgeting, anti-pattern scans, and critical path analysis.
  • Use Case: Optimizing a new page by setting budgets and tracing bottlenecks from load to interactivity.

Quick Start

Apply RAIL-based budgets and LCP/INP/CLS evaluation to rapidly assess front-end readiness and identify optimization steps.

Frequently Asked Questions about performance-eval

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

FAQPage Schema
How do I evaluate Core Web Vitals like LCP, INP, and CLS for my web application?

Evaluate Core Web Vitals by analyzing LCP, INP, and CLS metrics against established thresholds to identify rendering bottlenecks. This structured analysis interprets user-centric data to pinpoint specific latency issues affecting front-end performance.

What is the RAIL model and how do I use it to set frontend performance budgets?

The RAIL model defines user-centric performance targets for Response, Animation, Idle, and Load interactions. Apply RAIL guidance to establish specific performance budgets, ensuring your web application meets latency expectations for each interaction type.

How do I trace critical rendering path bottlenecks from page load to interactivity?

Trace critical rendering path bottlenecks by gathering lab audit data and scanning for front-end anti-patterns that block rendering. This evaluation workflow identifies resource sequencing issues delaying load and interactivity.

Can I use Lighthouse scoring to diagnose UX latency and optimize front-end readiness?

Use Lighthouse scoring to conduct lab audits that diagnose UX latency by measuring rendering behavior against performance budgets. This integration identifies optimization steps needed to improve overall front-end readiness.

What are common front-end anti-patterns that cause poor Core Web Vitals scores?

Common front-end anti-patterns causing poor Core Web Vitals scores include render-blocking resources, layout shifts, and heavy main-thread tasks. Scanning for these patterns during evaluation reveals specific structural issues degrading LCP, INP, and CLS.