Back to Blog

SEO

How to speed up your site: practical steps for Core Web Vitals

Admin User
How to speed up your site: practical steps for Core Web Vitals

This post is the practical side of our earlier Core Web Vitals and SEO impact article. There we introduced the metrics; here we look at what to do, in what order.

Target thresholds

According to web.dev, for page experience to count as "good," these values must be met for 75% of visits:

  • LCP (loading of the largest content element): 2.5 seconds or less,
  • INP (responsiveness to interactions): 200 milliseconds or less,
  • CLS (layout shift): 0.1 or less.

Look at the right data first

There are two kinds of data and they get mixed up. Field data is collected from real users' devices (Search Console's Core Web Vitals report, the top section of PageSpeed Insights). Lab data is a controlled test by tools like Lighthouse. Lab tests are good for finding problems, but Core Web Vitals assessment is based on real-user data. Note: Lighthouse has no direct INP measurement; it provides a proxy metric called TBT (Total Blocking Time).

So: first check in Search Console which URL group is "needs improvement / poor," then inspect that page with PageSpeed Insights.

Fixing LCP

  1. Which element is the LCP? Usually the top image or a large heading. The PageSpeed report shows it.
  2. Shrink the image: Modern formats (WebP / AVIF), the right size, srcset. Don't serve a 3000-pixel file for an image displayed at 600 pixels.
  3. Don't defer the LCP image: Don't lazy-load the main above-the-fold image; prioritize it (fetchpriority="high", priority in Next.js).
  4. Speed up the server response: Caching, a CDN, lighter page generation.
  5. Reduce render-blocking resources: Defer unnecessary CSS / JS files.

Fixing INP

  • Break up long JavaScript tasks; don't keep the main thread busy for long.
  • Remove third-party scripts you don't use (old widgets, unused tracking code).
  • Lighten event handlers that do heavy work on every click.
  • Avoid very large DOMs.

Fixing CLS

  • Give images and videos width / height (or an aspect ratio) so space is reserved in advance.
  • Reserve fixed height for ads, cookie banners and announcement areas.
  • Reduce the shift caused by web font loading with a font fallback and font-display.
  • Avoid content injected above existing content later.

Managing expectations

Speed exists as a ranking signal, but it doesn't override the others; good content still leads. Still, a slow page loses users and lowers ad landing page quality (the landing page experience component of Quality Score). After fixes, it can take a few weeks for field data to reflect them, since the report relies on recent user data.

For a technical speed audit see our SEO service, and for a general check use our SEO analysis tool.

Sources

How to Improve Site Speed: Core Web Vitals Guide | Auryn Dijital