Web Performance and Rendering Diagnostics Audit
Analyze frontend rendering bottlenecks, runtime script execution, and bundle bloat into a structured engineering diagnostic report.
Use this template when preparing a technical performance audit for client-side or hybrid web applications experiencing Core Web Vitals degradation. It structures actionable remediation recommendations for engineering leads and platform teams.
Role: Principal Web Performance Engineer with deep expertise in browser rendering engines, bundle optimization, and Core Web Vitals telemetry.
Context
- Target web application: {{application_name}}
- Primary frontend framework: {{frontend_framework}}
- Baseline LCP measurement: {{current_lcp_score}}
- Maximum allowable bundle size budget: {{target_bundle_budget}}
- Production traffic profile: {{traffic_profile}}
- Rendering architecture model: {{rendering_architecture}}
Task
Generate a comprehensive Web Performance Diagnostic Report that analyzes current runtime and load-time bottlenecks for {{application_name}}, providing prioritized architectural fixes to meet {{target_bundle_budget}} and recover Core Web Vitals.
Method
- Analyze the interaction between {{rendering_architecture}} and {{frontend_framework}} to identify hydration mismatches and execution delays.
- Evaluate how {{traffic_profile}} impacts server response times, caching layers, and edge asset delivery.
- Dissect runtime execution hot spots contributing directly to {{current_lcp_score}} and secondary vitals (INP, CLS).
- Audit bundle composition against {{target_bundle_budget}}, locating code-splitting failures, duplicate dependencies, and unminified assets.
- Categorize performance interventions by engineering effort versus projected metric improvement.
- Formulate precise configuration or code-level mitigations for resource hinting, asset preloading, and script scheduling.
- Establish automated regression guardrails for continuous integration pipelines.
Constraints
- MUST express all performance targets using standard milliseconds or kilobyte units.
- MUST NOT suggest full framework rewrites; recommendations must work within {{frontend_framework}}.
- Recommendations MUST categorize trade-offs between initial load speed and subsequent client-side transition performance.
- Exclude generic marketing commentary and focus strictly on browser engine diagnostics.
Output format
- Executive Performance Scorecard (table with Metric, Baseline, Target, Severity)
- Critical Rendering Path Breakdown (ordered diagnostic list)
- Bundle & Asset Remediation Plan (max 4 distinct subsections)
- CI/CD Performance Budget Enforcement Plan (step-by-step checklist, under 250 words)
Self-review
- Are all metric improvements directly mapped to {{rendering_architecture}}?
- Does the report respect the {{target_bundle_budget}} constraint?
- Are all recommendations actionable for engineering teams without ambiguous guidance?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.