Website performance planning
How to scope Core Web Vitals remediation costs
Build a comparable estimate from measured field data, affected templates, confirmed root causes, implementation, regression testing, rollout and agreed monitoring. A single Lighthouse score or indexed-URL count is not a reliable price basis; this guide provides a quote-scoping method, not a universal market price.
Loading performance
Interaction responsiveness
Visual stability
Build a comparable estimate
Request separate scope for field-data review and reproduction, affected templates and components, fixes by confirmed cause, content or asset work, third-party dependencies, staging, device and browser regression, accessibility and conversion checks, deployment, rollback, and post-launch monitoring.
Compare like-for-like deliverables and exclusions. A useful total is the vendor's itemized discovery + implementation by template/cause + validation and release + agreed monitoring. Do not multiply one-page effort across every URL until templates and shared components are mapped; no price range is asserted without a defined scope.
Typical work categories
LCP work may involve image sizing, formats, priority, server response, render blocking, fonts, or client rendering. INP work may involve long tasks, event handlers, hydration, third-party code, and DOM complexity. CLS work may involve missing dimensions, late content, fonts, ads, banners, and injected widgets.
Include analytics and marketing stakeholders when third-party tools cause measurable delay.
Price the complete change
Include discovery, implementation, content or asset changes, staging, device and browser testing, accessibility regression, analytics validation, deployment, rollback, and post-launch field monitoring.
Prioritize reusable template fixes over one-page score chasing. Preserve conversion, consent, security, and business functionality while improving performance.
Primary sources
This page separates sourced facts from North Star's operational guidance. Check the current source before relying on a changing price, rule, list, or technical standard.
Questions businesses ask
Can a Lighthouse score determine the project price?
No. Use field data, representative templates, confirmed causes, implementation scope, regression work and release requirements to request an itemized estimate.
Should every URL be tested manually?
Test representative templates and high-value outliers, then use field data and automated checks to validate coverage.
How long until field data changes?
Field data uses a rolling collection window, so improvements do not appear immediately after deployment.
Turn the research into an operating plan
North Star can help assess the environment, define scope, document ownership, implement controls, and verify the result.
Request a performance assessment