Cost & planning
Performance pricing should be based on the bottleneck and the number of representative templates, not a promise to install a caching plugin or guarantee a synthetic score.
Direct answer
Codeable currently lists speed and security optimization from $420 as a public starting example. A real estimate changes with the number of page templates, third-party scripts, hosting limitations, image/media work, database behavior and whether WooCommerce or other dynamic features must be protected.
Current facts
Answer scope
Google currently defines good field performance as LCP ≤2.5s, INP ≤200ms and CLS ≤0.1 at the 75th percentile. These are better acceptance references than a guaranteed Lighthouse score.
Performance scope should name which representative pages and devices are being measured.
Codeable currently publishes speed and security optimization from $420. That is a useful marketplace example, but it cannot describe every site because the root cause may be a large hero image, JavaScript, hosting latency, database queries or a third-party widget.
A diagnostic phase should identify the highest-impact causes before a broad rebuild is proposed.
WooCommerce pages contain cart, session, account and checkout behavior that should not be cached indiscriminately. Performance changes may need exclusions, object caching or database work that does not exist on a static brochure site.
Testing should cover actual customer actions after any caching or script changes.
Chat, analytics, advertising, consent, A/B testing and embedded media can add network and main-thread cost outside the theme. The project may need coordination with marketing or legal owners before tags can be removed or delayed.
Performance work is faster when the business can decide which scripts are essential.
Use the same representative URLs, devices and tools before and after changes. Keep field data separate from lab diagnostics because field metrics need real-user traffic to update.
A useful report explains what changed and which remaining constraints are outside the implementation scope.
Questions
Google currently defines good as LCP ≤2.5s, INP ≤200ms and CLS ≤0.1 at the 75th percentile.
Codeable currently publishes a starting example of $420 for speed and security optimization. The actual cost depends on the bottleneck, templates, hosting, third-party scripts, ecommerce behavior and testing scope.
No. A single synthetic score is not the same as field Core Web Vitals, and a fixed 100 score should not be treated as a universal requirement.
Evidence
First-party platform documentation and clearly labelled public market benchmarks used for factual claims on this page. A source link does not imply endorsement.
Current field-performance metrics and good thresholds: LCP 2.5 seconds or less, INP 200 ms or less and CLS 0.1 or less at the 75th percentile.
Public 2026 specialist-market benchmark: estimates based on an $80–$120 USD hourly rate, with published starting prices for common WordPress work.
Start a conversation
Send the current setup and the result you need. I will review the problem and suggest the most practical next step.