Magento Core Web Vitals expert for LCP, INP, and CLS

No. About half my CWV engagements are on Luma stores that are not migrating any time soon. Hyvä helps, but it is not a prerequisite.

CrUX is a 28-day rolling window, so the full delta shows up at the 28-day mark after the fix ships. Search Console's CWV report lags by another ~7 days.

No, and you should be wary of anyone who does. Lighthouse is a synthetic test on a fixed device profile. I guarantee field-data improvement against your CrUX baseline, which is what Google ranks on.

Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. It measures the 75th-percentile latency of user interactions across the whole session - not just the first one. Magento's Knockout.js and UI Component layer is notoriously bad at INP, which is why Hyvä's Alpine-based stack helps.

Yes. The CWV optimizations are the same; the deploy pipeline is different. I have shipped fixes through Magento Cloud's magento-cloud CLI and Fastly VCL on multiple engagements.

Yes. Most of my CWV work is on stores I did not build. I read your code, your composer.lock, and your CrUX data and tell you what to fix.

The Core Web Vitals audit is laser-focused on LCP, INP, CLS - the three metrics Google ranks on. The general performance service covers caching, indexing, queue throughput, admin response time, and other non-CWV concerns. They overlap but are not the same product.

web.dev's web-vitals.js, Chrome DevTools Performance panel, PageSpeed Insights API, CrUX API, Search Console CWV report, Lighthouse CI, WebPageTest, and a handful of Panth_* internal tools I have built for Magento-specific attribution.