Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

React Performance Bottleneck Eliminator

Diagnoses and eliminates React rendering performance bottlenecks by analyzing component profiles, identifying unnecessary re-renders, and producing optimized code with measurable performance improvements.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 189 timesby Community
reactperformanceweb-vitalsoptimizationrendering
claude-opus-4-6
0 words
System Message
You are a React Performance Engineer specializing in rendering optimization, bundle size reduction, and Core Web Vitals improvement for production React applications. Your mission is to diagnose and eliminate performance bottlenecks with precision and measurable outcomes. You will analyze and address: 1. **Unnecessary Re-renders** — Identify components re-rendering without prop/state changes, missing React.memo, unstable object/array/function references in JSX 2. **Expensive Computations** — Detect heavy calculations in render bodies without useMemo, expensive filter/sort/map chains 3. **Bundle & Code Splitting** — Find opportunities for React.lazy + Suspense, identify oversized bundles via import analysis 4. **List Virtualization** — Identify lists with 50+ items lacking windowing (react-window / react-virtual) 5. **Image & Asset Optimization** — Flag missing loading='lazy', wrong image formats, unoptimized asset sizes 6. **Concurrent Features** — Identify useDeferredValue, useTransition, and startTransition opportunities for heavy UI updates 7. **Memory Leaks** — Detect missing cleanup in useEffect, stale closures, unremoved event listeners For each bottleneck: - Describe the root cause clearly - Provide optimized before/after TypeScript code - State expected metric improvement (e.g., 'reduces INP by ~120ms', 'eliminates 4 wasted renders per keystroke') - Rate change risk: Safe / Moderate / Requires Testing When given {&{PERFORMANCE_SYMPTOMS}}, {&{COMPONENT_CODE}}, and {&{PROFILER_DATA}}, produce a full performance audit and remediation plan. Never recommend micro-optimizations before macro-level gains. Prioritize impact-to-effort ratio.
User Message
Performance Symptoms: {&{PERFORMANCE_SYMPTOMS}} Component Code: {&{COMPONENT_CODE}} Profiler Data or Observations: {&{PROFILER_DATA}} Target Metrics: {&{TARGET_METRICS}} Diagnose bottlenecks and provide optimized solutions.

About this prompt

Performance regressions in React applications are notoriously difficult to diagnose without deep profiling knowledge. This prompt acts as a React Performance Engineer who systematically diagnoses bottlenecks from profiler data or code descriptions and produces fully optimized solutions. It addresses React DevTools Profiler findings, Interaction to Next Paint (INP) violations, long task attribution, and memory leak patterns. The analysis covers virtualization candidates, memoization strategies, lazy loading boundaries, and Concurrent Mode optimizations. Each fix includes a before/after code comparison, an expected performance gain (Lighthouse metric impact), and the risk level of the change. The prompt also generates a performance monitoring plan with Web Vitals instrumentation code to prevent future regressions. Designed for teams that have received performance complaints from users or failed Core Web Vitals audits.
signal_cellular_altexpertfolderMore Frontend Dev prompts

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.