Your site moves from failing Core Web Vitals to passing on at least 75% of pageviews. Each metric (Interaction to Next Paint, Largest Contentful Paint, Cumulative Layout Shift) gets diagnosed at the source: which component, which third-party script, which font, which image, which layout-thrash. Fixes ship in priority order against the actual buyer-journey URLs; the verification reads from the Chrome User Experience Report, not Lighthouse alone, so the numbers reflect real-user performance rather than synthetic-lab.
INP fixes (input handler debouncing, long task breaking, hydration cost)
Before-and-after CrUX evidence: 28-day window pre and 28-day window post
Foundations
Every core web vitals fix engagement inherits the four UX Studio foundations.
Schema graph wired at every URL. Core Web Vitals budget agreed at scope. Crawler-access policy across 18 named AI crawlers. Schema-per-page rather than templated copies. The full foundations grid lives on the UX Studio overview.
PSI gives you a synthetic-lab score and a list of opportunities. The fix engagement reads CrUX (real-user data, the metric Google actually ranks on), traces every regression to a specific source-level cause, and ships fixes in dependency order. because some fixes (font loading, third-party scripts) unblock others. Synthetic-lab Lighthouse can score 95 on a page that real users experience as broken; the engagement targets the real-user metric, not the synthetic one.
Yes, in roughly 80% of cases. Most CWV failures trace to a small number of regressions: hero images not optimised, font loading blocking render, a single third-party script (analytics, chat, advertising tag) eating INP, layout shifts from late-loading widgets. Fixing those at source rarely requires a rebuild. The remaining 20% (sites where the framework choice itself is the bottleneck) get scoped as a redesign or a migration instead.
Two paths. If the script is configurable, the engagement covers tuning it: deferring load until interaction, conditional loading by route, replacing it with a lighter alternative (Plausible instead of GA4 + Hotjar, for example). If the script is structural to the business (Stripe checkout, an embedded booking widget), the fix is to budget the rest of the page so the third-party's overhead is absorbed elsewhere. Sometimes the right answer is to renegotiate the third-party itself; that's a business call, not an engineering one.
Work with valUX
Start where it hurts.
If your organic traffic is sliding, start with a Pulse audit. If you want a programme rather than a one-off, ask about a retainer. Either way, every enquiry is read by a senior architect, and you hear back within one working day.