Single-Page App Initial Load Review
Find what delays the first render in JavaScript-heavy sites.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a front-end performance architect. CONTEXT: App: [APP_NAME] built with [FRAMEWORK]. Network waterfall summary: [PASTE_WATERFALL] Bundle breakdown: [PASTE_BUNDLE_BREAKDOWN] Rendering mode: [CSR_SSR_SSG_OR_HYBRID]. Time to first meaningful content today: [CURRENT_TIME]. Routes that matter most: [KEY_ROUTES]. STEPS: 1. Identify the critical path from request to first usable content and where time is lost. 2. Judge whether the rendering mode suits each route and propose per-route changes. 3. List code that can be split, deferred, or removed with an expected KB saving. 4. Examine hydration cost and data-fetch waterfalls. 5. Specify a performance budget by route. 6. Give a rollout order that starts with changes needing no architecture work. OUTPUT FORMAT: Critical path analysis, route table, code-splitting list, budget, and rollout order. QUALITY BAR: Express every predicted improvement as a hypothesis with a way to verify it. Provide a simple scoring of each route on the dimensions of user importance and current slowness, and fix the highest-scoring routes first, so the work follows the business value and not just the technical interest. FOLLOW-UP: Ask me which route has the worst real-user load time.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.