Core Web Vitals became an official Google ranking signal in May 2021. But beyond rankings, slow pages directly destroy conversion rates, and the impact is measurable, predictable, and in most cases, fixable with targeted technical work.
The 1-second rule
Studies consistently show that a 1-second delay in page load time reduces conversions by approximately 7%. On a mobile device with a slow connection, the impact is even greater. Google's own data shows that as page load time increases from 1 to 3 seconds, bounce probability increases by 32%.
The ranking correlation
In every competitive audit I have conducted, insurance, eCommerce, SaaS. The sites passing Core Web Vitals on mobile consistently outrank those that don't. QBE was the only Australian home insurer passing CWV on mobile and ranked #1 for "Home Insurance" while competitors sat at positions 2–6.
Mobile-first reality
Google uses your mobile performance as the primary ranking signal, not desktop. Yet most sites have significantly worse mobile scores than desktop. The revenue impact calculation weights mobile traffic share because that is where the performance gap, and therefore the revenue leak, is largest.
What I found on a real client site
Vuly Play's homepage had a 3/100 mobile PageSpeed score and a total network payload of 74MB, driven by three autoplay MP4 video loops each exceeding 10MB. After identifying and fixing these issues, the page speed score improved dramatically and the site's mobile organic traffic grew accordingly. The biggest single fix was replacing the video loops with lightweight poster images.
What is a good Core Web Vitals score?
Google defines "good" as: LCP (Largest Contentful Paint) under 2.5 seconds, INP (Interaction to Next Paint) under 200ms, and CLS (Cumulative Layout Shift) under 0.1. All three must pass on mobile for your page to be considered CWV-compliant. Check your scores in Google Search Console under "Core Web Vitals" or at pagespeed.web.dev.
What causes a high CLS score?
CLS is caused by elements that shift the page layout as it loads, most commonly images without explicit width and height attributes, web fonts that swap in late, dynamically injected banners or ads, and animations that affect layout. The fix is usually to reserve space for every element before it loads using explicit dimensions or aspect-ratio CSS.
How quickly can CWV issues be fixed?
Quick wins like adding image dimensions, enabling compression, and deferring non-critical scripts can be done in a day and show results within the next Google crawl cycle (typically 2–4 weeks). More complex fixes like code splitting and CDN configuration take longer but have a proportionally larger impact.