Google has used Core Web Vitals as a ranking signal for years, but the real reason to care is simpler: faster websites sell more. Every extra second of load time increases bounce rate and lowers conversions, especially for mobile visitors on slower networks.
This guide explains the three metrics in plain English, shows you how to find what is slowing your site down, and lists the fixes that make the biggest difference, including platform-specific tips for WordPress, Shopify, Webflow and Next.js.
What are Core Web Vitals?
Core Web Vitals are three metrics Google uses to measure the real experience of loading and using a page:
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP: Largest Contentful Paint | How fast the main content appears | ≤ 2.5 s | 2.5–4 s | > 4 s |
| INP: Interaction to Next Paint | How quickly the page responds to taps, clicks and typing | ≤ 200 ms | 200–500 ms | > 500 ms |
| CLS: Cumulative Layout Shift | How much the layout jumps while loading | ≤ 0.1 | 0.1–0.25 | > 0.25 |
A page passes when at least 75% of real visits hit the “good” threshold for all three.
Why website speed matters for your business
- Rankings: Core Web Vitals are part of Google’s page experience signals. When two pages are equally relevant, the faster one has the edge.
- Conversions: visitors abandon slow pages. Shaving even a second off your load time can noticeably lift enquiries and sales.
- Ad costs: landing page experience affects Google Ads quality scores, so slow pages can cost you more per click.
- Trust: a page that jumps around or freezes when tapped feels broken, and visitors rarely give it a second chance.
Step 1: Measure the right data
There are two kinds of speed data, and mixing them up is the most common mistake we see:
| Tool | Data type | Use it for |
|---|---|---|
| Google Search Console (Core Web Vitals report) | Field (real users) | Seeing which page groups fail and tracking progress |
| PageSpeed Insights | Field (top) + lab (bottom) | Checking one URL and getting a diagnosis |
| Chrome DevTools (Performance panel, Lighthouse) | Lab | Debugging exactly what blocks loading or interaction |
| WebPageTest | Lab | Waterfalls, filmstrips and testing from different locations |
Rule of thumb: use field data to decide what to fix and lab tools to work out how.
Step 2: Fix Largest Contentful Paint (LCP)
LCP is usually your hero image, a banner or the main heading. It breaks down into four parts: server response time, the delay before the resource starts loading, the download itself and the time to render it. Fix them in this order:
- Speed up the server (TTFB). Use page caching, a CDN and decent hosting. Shared hosting with no caching often accounts for a full second or more on its own.
- Make the LCP image discoverable early. Use a normal
<img>tag (not a CSS background), addfetchpriority="high"and never lazy-load above-the-fold images. - Shrink the image. Serve WebP or AVIF, size it for the device with
srcsetand compress it. A 2 MB hero image is the single most common LCP problem. - Remove render-blocking resources. Inline critical CSS, defer non-essential CSS and JavaScript, and preload your main font with
font-display: swap.
Step 3: Fix Interaction to Next Paint (INP)
INP measures how long the page takes to respond visually after a visitor interacts. Poor INP is almost always caused by too much JavaScript on the main thread.
- Cut JavaScript. Remove unused plugins, sliders, animation libraries and old tracking tags.
- Delay third-party scripts. Load chat widgets, heatmaps and social embeds after the first interaction or when they scroll into view.
- Break up long tasks. Split heavy work into smaller chunks so the browser can respond to input between them.
- Keep event handlers light. Show visual feedback immediately, then do expensive work afterwards.
- Avoid huge DOMs. Pages with thousands of elements (often from page builders) are slow to update.
Step 4: Fix Cumulative Layout Shift (CLS)
- Always set
widthandheight(oraspect-ratio) on images, videos and iframes. - Reserve space for ads, embeds, cookie banners and announcement bars.
- Never insert content above existing content after the page loads, unless the visitor asked for it.
- Use
font-display: swapwith a well-matched fallback font, orsize-adjust, so text does not jump when web fonts load. - Animate with
transformandopacityinstead of properties that change layout.
Step 5: Tame third-party scripts
Marketing tags are the silent killer of website speed. Every pixel, chat widget and A/B testing tool adds JavaScript. Audit them every quarter:
- Remove tags for campaigns and tools you no longer use.
- Load tags through Google Tag Manager with sensible triggers rather than on every page.
- Replace heavy embeds (YouTube, maps) with a lightweight preview that loads the real embed on click.
Platform-specific quick wins
WordPress
- Use a lightweight theme or a custom block theme instead of a heavy multipurpose theme.
- Use a quality caching plugin plus server-level caching and a CDN.
- Audit plugins ruthlessly. Our WordPress speed guide covers the full process.
Shopify
- Remove apps you no longer use; many leave scripts behind in your theme.
- Choose a fast Online Store 2.0 theme and compress product images.
- See our tips on optimising your Shopify store for mobile.
Webflow
- Limit heavy interactions and Lottie animations on mobile.
- Compress images before upload and use Webflow’s responsive image settings.
- Read how to speed up a Webflow website.
Next.js and React
- Use server rendering or static generation for content pages; see server-side rendering with React.
- Use the built-in image and font optimisation, and keep client components small.
- Follow our guide to optimising React performance.
Core Web Vitals checklist
- Field data checked in Search Console
- Page caching and CDN enabled
- Hero image is WebP/AVIF, correctly sized, not lazy-loaded, with
fetchpriority="high" - Critical CSS inlined; fonts preloaded with
font-display: swap - Unused plugins, apps and tags removed
- Third-party scripts delayed until interaction
- Width and height set on all media; space reserved for banners and embeds
- Performance budget agreed and checked monthly
Make speed a habit
Performance is not a one-time project. New plugins, campaigns and tracking pixels slowly erode your scores. Set a performance budget (for example: LCP under 2 seconds and less than 300 KB of JavaScript), check Search Console monthly, and test every major change before it goes live. A regular website maintenance routine keeps speed from slipping.
Get expert help with Core Web Vitals
Want measurable results without the trial and error? Our website speed optimization service audits your site, fixes the bottlenecks and reports before-and-after Core Web Vitals. Contact Webyant for a free speed review.
- website optimization
- core web vitals
- page speed
Rutvik Padhiyar
Frontend Developer, Webyant Technologies
Rutvik turns static designs into fast, responsive interfaces that feel great on every screen. A frontend developer at Webyant since 2024, Rutvik works across WordPress, React and Next.js, with a soft spot for clean code, smooth interactions and green Core Web Vitals scores.
Need help with this? Explore our services



