Enterprise Core Web Vitals Remediation and Budgeting Roadmap
Design a tactical performance optimization plan targeting LCP, INP, and CLS improvements for complex web apps.
Use this template when an interactive enterprise web application is failing Core Web Vitals thresholds. It produces a granular remediation roadmap covering asset pipelines, hydration costs, and script execution budgets.
Role: Staff Web Performance Engineer specializing in runtime profiling, rendering pipeline optimization, and Core Web Vitals.
Context
- Current field metric telemetry: {{current_cwv_metrics}}
- Rendering and hydration architecture: {{ssr_framework}}
- Third-party script ecosystem: {{third_party_scripts}}
- Hosting and edge infrastructure: {{hosting_infrastructure}}
- Target Interaction to Next Paint ceiling: {{target_inp_threshold}}
- Business revenue/conversion objective: {{conversion_impact_goal}}
Task
Create a tactical engineering remediation plan that diagnoses root causes behind {{current_cwv_metrics}}, details code-level optimizations across {{ssr_framework}}, and establishes automated performance budgets to hit {{target_inp_threshold}} and support {{conversion_impact_goal}}.
Method
- Deconstruct the critical rendering path to isolate render-blocking resources impacting LCP on {{hosting_infrastructure}}.
- Profile main-thread long tasks to identify JavaScript execution bottlenecks directly affecting {{target_inp_threshold}}.
- Audit DOM mutations and dynamic layout shifts caused by {{third_party_scripts}} and async font loading.
- Design an optimized asset delivery strategy including image priority hints, modern image formats, and edge caching.
- Formulate selective hydration, code-splitting, or server-component migration patterns for {{ssr_framework}}.
- Structure a third-party script governance policy utilizing web workers or deferred execution sandboxes.
- Establish automated CI/CD performance budgets with PR regression gates for synthetic and real-user monitoring.
Constraints
- MUST specify measurable sub-metrics (e.g., TTFB, FCP, TBT) alongside the primary Core Web Vitals.
- MUST NOT recommend eliminating business-critical scripts without providing an architectural off-main-thread alternative.
- All recommended runtime optimizations must run within the constraints of {{ssr_framework}}.
- Budgets must explicitly prevent regressions above {{target_inp_threshold}}.
Output format
Provide the deliverable in 4 structured markdown sections:
- Diagnostics & Root Cause Analysis (Breakdown of LCP, INP, and CLS failure modes)
- Tactical Engineering Action Items (Priority-ranked matrix: Effort vs. Metric Impact)
- Third-Party Script & Hydration Architecture (Containment and offloading strategy)
- Continuous Enforcement Framework (Lighthouse CI budgets, RUM alerts, and PR checks) Total length should be between 700 and 1000 words.
Self-review
- Did I provide concrete technical solutions for INP rather than just generic script minification?
- Does the plan address the interaction between third-party tags in {{third_party_scripts}} and main thread locking?
- Are all action items explicitly prioritized by business impact towards {{conversion_impact_goal}}?
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.