Slow, jumpy pages cost leads. Visitors abandon pages that take too long to show content, tap buttons that do not respond, or lose their place when an image suddenly pushes text down. Core Web Vitals optimization addresses exactly these problems, and it matters for both search visibility and conversion.
What Core Web Vitals measure
Google's Core Web Vitals are three metrics based on real user experience:
| Metric | What it measures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to clicks, taps and typing | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout moves unexpectedly | 0.1 or less |
Thresholds are assessed at the 75th percentile of visits, separately for mobile and desktop. The definitions and thresholds are documented on web.dev.
Do Core Web Vitals affect rankings?
Core Web Vitals are part of Google's page experience signals. They are not a substitute for relevant, helpful content, and a fast page will not outrank a much better answer. In competitive results where content quality is similar, better experience can help. The bigger benefit is usually conversion: faster, more stable pages keep more visitors engaged.
How to measure Core Web Vitals
- Field data: the Core Web Vitals report in Google Search Console and the field section of PageSpeed Insights show real user data. Use these to decide what to fix.
- Lab data: Lighthouse and the lab section of PageSpeed Insights simulate a load. Use them to diagnose causes and test changes.
Group pages by template (homepage, blog post, service page, product page). Fixing a template fixes every page built on it.
Improving Largest Contentful Paint
LCP is usually a hero image, a large heading or a video poster. Common fixes:
- Optimise the LCP image: compress it, serve modern formats such as WebP or AVIF, size it for the viewport and avoid lazy-loading it.
- Prioritise it: use fetchpriority="high" on the main image and preload critical resources where appropriate.
- Reduce server response time: use caching, a content delivery network and efficient hosting.
- Remove render-blocking resources: inline critical CSS, defer non-critical JavaScript and limit web font variants.
- Avoid client-side rendering for main content: server-rendered HTML shows content sooner.
See the detailed guidance on optimising LCP.
Improving Interaction to Next Paint
INP measures responsiveness throughout the visit. Poor INP is usually caused by heavy JavaScript.
- Audit third-party scripts: chat widgets, heatmaps, A/B testing tools and multiple tag managers often block the main thread.
- Break up long tasks: split heavy JavaScript work so the browser can respond to input between tasks.
- Trim unused scripts: remove libraries and plugins you no longer need.
- Keep event handlers light: avoid doing heavy work immediately on click or keypress.
- Load non-essential scripts later: delay chat or marketing scripts until after interaction or idle time.
Google's guide to INP explains diagnosis with browser tools.
Improving Cumulative Layout Shift
CLS happens when content moves after it first appears.
- Set dimensions on images and videos using width and height attributes or CSS aspect ratios.
- Reserve space for embeds and ads so they do not push content when they load.
- Avoid inserting banners above existing content after load, such as late cookie notices.
- Use font-display strategies and matching fallback fonts to reduce text reflow.
- Animate with transforms rather than properties that change layout.
More detail is available in the CLS guide.
A practical Core Web Vitals optimization workflow
- Check the Core Web Vitals report in Search Console and list failing templates.
- Run PageSpeed Insights on a representative URL for each failing template.
- Identify the LCP element, the longest tasks and the largest layout shifts.
- Fix the biggest issue per template and deploy.
- Wait for field data to update (it is collected over 28 days) and confirm improvement.
Page speed SEO beyond Core Web Vitals
Core Web Vitals do not cover everything. Also check time to first byte, total page weight, the number of requests and how the page performs on slower mobile connections. Image-heavy pages benefit from responsive images and lazy-loading below-the-fold media.
Core Web Vitals on popular platforms
Most business websites run on a CMS or website builder, and each has typical weak points. WordPress sites often slow down because of heavy themes and many plugins; reducing plugins, using a lightweight theme and adding page caching usually helps. Page builders can output large amounts of CSS and JavaScript; disabling unused modules matters. Hosted builders limit server control, so image optimisation and script discipline become the main levers. Custom-built sites give the most control, which makes performance budgets and code reviews essential. Our WordPress vs Webflow vs custom comparison discusses these trade-offs when choosing a platform.
Why speed matters for conversion
Visitors arriving from ads or search decide quickly whether to stay. A slow landing page wastes the money spent to bring them there. Improving speed on high-traffic templates, especially PPC landing pages and pricing pages, often produces measurable conversion gains.
Common causes of poor Core Web Vitals on business sites
- Uncompressed hero images and background videos.
- Page builders that load large amounts of unused CSS and JavaScript.
- Many third-party scripts loaded on every page.
- Web fonts loaded in many weights.
- Cookie banners, pop-ups and chat widgets inserted late.
If you are planning a redesign, set performance budgets from the start. Our website design and development work treats speed as a requirement, and our technical SEO audit checklist covers related checks.
