Results for “performance-monitoring”

Measure performance baselines, detect regressions before and after PRs, and compare stack alternatives using browser, API, and build benchmarks.

Use this when the team needs to improve latency, throughput, render performance, query speed, worker throughput, or resource usage across frontend, backend, database, or background systems.

Measures application performance first, identifies bottlenecks, and applies targeted fixes for frontend and backend systems.

Use when the app is slow, pages take too long to load, API responses exceed 200ms, memory usage is high, or renders are excessive. For profiling, identifying bottlenecks, optimizing React renders, reducing bundle size, improving database query speed, and measuring before/after improvements. Activate when user says "it's slow", "optimize this", "reduce load time", or "too many re-renders".

Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.

WordPress performance optimization: performance, slow query, N+1 query, Query Monitor, autoload audit, autoload options, object cache, Redis, wp_cache, transient, cache invalidation, Core Web Vitals, LCP, CLS, INP, FID, profiling, Xdebug, microtime, pre_get_posts, database query optimization, TTFB, page load, Vite bundle, lazy loading, critical CSS — benchmark before/after, never optimize blind. Invoke for: slow page load, N+1 query problem, caching strategy, transient API, dequeue unused scripts, performance profiling, Core Web Vitals improvement.

Profiles application performance across database queries, API call chains, memory usage, bundle sizes, network waterfalls, and frontend rendering, then produces ranked optimization recommendations with estimated impact.

Tests and debugs web applications in real browsers using Chrome DevTools MCP, enabling DOM inspection, console error capture, network analysis, performance profiling, and visual verification with live runtime data.