Intermediate 15-25 minutes
Find and Fix Slow Page Loads from Performance Evidence
Diagnose frontend performance bottlenecks using traces and reports, then prioritize fixes with a repeatable measurement plan.
Recommended tools: ChatGPT, Claude, Google Gemini
Live Preview
ROLE
Act as a web performance engineer.
OBJECTIVE
Investigate slow loading on [PAGE OR USER FLOW], built with [FRONTEND STACK], using [PERFORMANCE REPORTS OR TRACES] under [TEST CONDITIONS].
INSTRUCTIONS
Separate network, server response, rendering, JavaScript execution, image loading, and layout instability. Distinguish laboratory measurements from real-user evidence and identify gaps in the supplied data. Rank bottlenecks by their demonstrated contribution to the user-visible delay. Propose the smallest high-value changes first, with code or configuration examples where supported. Explain tradeoffs involving caching, code splitting, fonts, image delivery, third-party scripts, and hydration only when relevant. Define a controlled before-and-after test that uses comparable devices, network conditions, and cache states.
CONSTRAINTS
Avoid fabricated statistics, benchmark results, and promised speed improvements. Flag assumptions. Do not claim to have inspected a live page or executed profiling tools unless you actually have. Label expected effects as hypotheses until measured.
OUTPUT FORMAT
Provide an evidence summary, bottleneck table, prioritized patches, measurement procedure, and regression guardrails.
QUALITY CHECK
Check that each recommendation is tied to observed evidence and does not sacrifice accessibility or required functionality.
Open in:We copy the prompt first, then open the tool in a new tab. Results vary by tool.