Performance Bottleneck PR Inspector
For backend and frontend engineers reviewing changes that may introduce latency, memory, or rendering regressions.
Best for these models
๐ The Prompt
๐ Prompt available in download
Get the full prompt text in a downloadable .txt file. Free, no signup required.
Download PromptVariables to fill in
{{CODE_DIFF}} โ Replace with your input {{RUNTIME}} โ Replace with your input {{LOAD_PROFILE}} โ Replace with your input {{FOCUS}} โ Replace with your input About this prompt
Performance Bottleneck PR Inspector helps teams identify code changes that may slow down requests, increase memory usage, or create rendering regressions. It acts like a senior performance engineer, reviewing the diff for algorithmic complexity, unnecessary allocations, blocking calls, repeated queries, and expensive UI re-renders. The prompt is especially useful when changes look correct but could quietly degrade user experience under load.
This template is built for backend engineers, frontend leads, and platform teams who need a fast performance review before merging. It asks the model to explain why a change is costly, estimate the likely impact, and suggest alternatives that preserve behavior. The result is practical feedback that can be used in PR comments or shared during engineering review meetings. It is useful for services with strict latency budgets, dashboards with heavy client-side logic, and APIs that must stay efficient at scale.
Customize by adding your code diff to {{CODE_DIFF}}, the runtime in {{RUNTIME}}, and any load expectations in {{LOAD_PROFILE}}. If you want the model to focus on a specific area, set {{FOCUS}} to database, rendering, caching, or concurrency. The prompt returns findings ranked by impact, plus concrete optimization ideas and tradeoffs. For deeper analysis, run it once on the backend path and once on the user-facing path to catch both server and client regressions.
Key features
- Finds latency regressions before they hit production users.
- Highlights memory waste, repeated work, and blocking operations.
- Explains tradeoffs between readability, speed, and maintainability.
- Useful for scaling reviews on APIs and frontends.
- Returns ranked recommendations by likely performance impact.
Best for
- โ Backend engineers optimizing API endpoints and database access
- โ Frontend leads reviewing rendering-heavy component changes
- โ Platform teams enforcing latency budgets and resource limits
Tips
- ๐ก Include expected traffic or latency targets in {{LOAD_PROFILE}} for more precise recommendations.
- ๐ก Set {{FOCUS}} to one area at a time, like caching or rendering.
- ๐ก Ask for tradeoff notes when you want alternatives ranked by complexity and payoff.
What you'll get
A ranked performance review with high, medium, and low impact issues. It calls out expensive loops, redundant queries, memory-heavy patterns, and rendering hot spots. Each item includes a short explanation, the likely user impact, and a practical optimization. The review ends with a merge recommendation and notes on whether profiling is needed.
Preparing your download...
Download PromptRelated prompts
API Contract Review Analyst
For engineers reviewing API changes that may break clients, contracts, or backward compatibility guarantees.
API Mock Server Blueprinter
For teams building mock services that simulate realistic API behavior before backend completion.
API Reference Documentation Forge
For platform teams generating accurate API reference docs from schemas, routes, or endpoint notes.
Backend Test Fixture Architect
For senior engineers creating reusable fixtures and mocks for complex backend test suites.