QHX
← All insights

Core Web Vitals: What Actually Affects Rankings and Conversions

UncategorizedNov 3, 20264 min read

Website speed advice is everywhere, and much of it is expensive. Before you pay for a speed project, it helps to know what Google actually measures, how much it matters, and which fixes make a real difference for your visitors.

Key takeaways

  • Core Web Vitals are three measurements of real-world experience: loading (LCP), responsiveness (INP) and visual stability (CLS).
  • They are part of how Google assesses page experience, but relevant, helpful content still matters more. Speed won’t rescue a weak page.
  • The fixes with the biggest impact are usually images, hosting and caching, and third-party scripts, not chasing a perfect score.

The three metrics, in plain English

Largest Contentful Paint (LCP): how fast the main content appears

LCP measures how long it takes for the largest visible element, usually a hero image or headline, to appear. Google considers 2.5 seconds or less good.

Interaction to Next Paint (INP): how fast the page responds

INP measures how quickly the page reacts when someone taps, clicks or types. It replaced the older First Input Delay metric in March 2024. 200 milliseconds or less is good. A page that freezes for a moment after you tap a menu has an INP problem.

Cumulative Layout Shift (CLS): how much the page jumps around

CLS measures unexpected movement, like a button sliding down just as you go to tap it because an image or banner loaded above it. A score of 0.1 or less is good.

Google assesses each metric at the 75th percentile of real visits, separately for mobile and desktop. In other words, most of your visitors, not just the ones on fast connections, need a good experience for a page to pass.

How much do they affect rankings?

Google has said that Core Web Vitals are used by its ranking systems as part of page experience. It has also been clear that great page experience does not override relevance. A slow page with the best answer can still outrank a fast page with a thin one.

The practical takeaway: treat Core Web Vitals as a quality baseline, not a magic ranking lever. Fix what is clearly broken, then put your energy into content and conversion.

The stronger business case is often your own visitors. People leave pages that load slowly, jump around or ignore their taps. Those are lost enquiries and sales, whatever your ranking.

Fixes that are usually worth paying for

1. Images, especially the first one

The LCP element is often a large image at the top of the page. The highest-impact steps are usually to:

  • Serve it at the size it is actually displayed, in a modern format such as WebP or AVIF.
  • Avoid lazy-loading it. Lazy loading is great for images further down the page, but it delays the one visitors see first.
  • Give it a higher loading priority so the browser fetches it early.

2. Hosting, caching and server response

If the server takes a long time to start sending the page, everything else waits. Page caching, a good host and a content delivery network (CDN) for international visitors usually improve loading across the whole site at once.

3. Third-party scripts

Chat widgets, heatmaps, social embeds, multiple tracking tags and pop-up tools all compete for the browser’s attention. They are a common cause of poor INP. Audit them, remove what nobody uses, and load the rest after the main content.

4. Reserved space for images, ads and embeds

Most layout shift comes from elements that load without reserved space. Setting width and height on images and video, and reserving space for banners and embeds, fixes most CLS problems.

5. Fonts and render-blocking files

Too many font files, or CSS and JavaScript that must load before anything appears, delay the first view. Loading fewer font weights and deferring non-critical scripts often helps.

Fixes that rarely move the needle

  • Chasing a perfect Lighthouse score. The lab score is a diagnostic tool. What counts for Core Web Vitals is real-user data.
  • Shaving a few kilobytes off an already light page while a heavy chat widget stays in place.
  • Installing several optimization plugins at once. They often overlap, conflict, or break features. One well-configured caching setup beats three competing ones.

How to measure your site

  1. PageSpeed Insights: enter any URL. The top section shows real-user data (when Google has enough), and the lower section shows lab diagnostics with specific suggestions.
  2. Google Search Console: the Core Web Vitals report groups similar pages, so you can fix a whole template at once.
  3. Your own phone: open your key pages on mobile data. If something feels slow or jumpy to you, it does to your customers too.

Where to start

Start with the pages that make you money: your homepage, main service or product pages, and top landing pages. Check them in PageSpeed Insights, fix the biggest issue on each, and measure again after a few weeks of real-user data.

Speed work pays off most when it is focused. A faster page that also explains your offer clearly and makes the next step obvious is what turns visits into customers.

Work with QHX

Want help putting this into practice?

Tell us about your website and goals. We will reply with honest first thoughts and a suggested starting point.