Core Web Vitals are three measurements Google uses to describe real-world user experience: how quickly the main content loads, how quickly the page responds when someone uses it, and how stable the layout is while everything loads. If your site fails them, Search Console and PageSpeed Insights will tell you, usually in red text that does not explain much.
Disclosure: this article contains affiliate links, including links to Fiverr and Hostinger. If you buy through them, I may earn a commission at no extra cost to you. Read my affiliate disclosure for details.
This guide translates that red text into plain language, and into the changes that usually fix it on a WordPress site.
The three Core Web Vitals and their targets
Segments are drawn at equal width for readability, not to scale.
A page passes when at least 75 percent of real visits, measured separately for mobile and desktop, land in the good range for all three metrics. So it is not enough for your own phone to feel fast.
LCP: Largest Contentful Paint
LCP measures how long the largest visible element takes to appear. On most WordPress pages that is a hero image, a featured image or a large heading. Good is 2.5 seconds or less.
What usually slows it down
- A slow server response, from weak hosting or no page cache.
- A hero image that is too big, or one that is lazy-loaded when it should load first.
- Render-blocking CSS and JavaScript that holds back the first paint.
- Web fonts that load late and delay the headline.
What to do about it
- Use a page cache and quality WordPress hosting. If the server takes a second to answer, everything else starts late.
- Compress and right-size the hero image, use WebP, and do not lazy-load it.
- Defer scripts that are not needed for the first screen and keep critical CSS small.
- In PageSpeed Insights, open the diagnostics and look for the Largest Contentful Paint element. It tells you exactly which element to work on.
Slow server response? Start with hosting
Server response time is one of the first things that affects LCP. If your site stays slow after caching and image fixes, compare hosting plans. Hostinger’s hosting runs on LiteSpeed server technology and supports the LiteSpeed Cache plugin for WordPress.
Compare Hostinger web hostingAffiliate link. It opens your cart with a plan preselected, so you can change the plan, billing term and add-ons before you pay. Check the renewal price too.
INP: Interaction to Next Paint
INP replaced First Input Delay as a Core Web Vital in March 2024. It looks at how long the page takes to respond visually after taps, clicks and key presses during the whole visit, and reports one of the slowest. Good is 200 milliseconds or less.
What usually slows it down
- Heavy JavaScript from themes, page builders and sliders.
- Third-party scripts such as chat widgets, ad tags, analytics and tag managers.
- A very large page structure that takes the browser a long time to update.
What to do about it
- Remove plugins and widgets you do not use. Every one of them can add code to every page.
- Delay or drop third-party scripts. Ask whether anyone really reads that heatmap.
- Keep the page structure simple and avoid deeply nested layouts.
- Test on a real mid-range phone. INP comes from real usage, so a fast laptop hides the problem. Lab tools use Total Blocking Time as a rough stand-in.
CLS: Cumulative Layout Shift
CLS adds up unexpected movement on the page: the button that jumps just as you tap it, or the paragraph pushed down by a banner that loads late. Good is 0.1 or less.
What usually causes it
- Images, videos and embeds without set dimensions.
- Cookie banners, popups and ads inserted above existing content.
- Web fonts that swap in with different spacing than the fallback font.
What to do about it
- Make sure images and embeds have width and height, or a fixed aspect ratio.
- Reserve space for banners and ad slots with a minimum height.
- Use font-display swap with a fallback font that is close in size.
A quick reference
| Metric | Usual WordPress causes | First things to try |
|---|---|---|
| LCP | Slow server response, oversized or lazy-loaded hero image, render-blocking CSS and JavaScript | Page cache and better hosting, right-sized hero image, defer non-critical scripts |
| INP | Heavy theme or builder JavaScript, chat widgets, trackers, tag managers | Remove unused plugins, delay or drop third-party scripts, keep the page structure small |
| CLS | Images and embeds without dimensions, late banners and popups, font swaps | Set dimensions, reserve space, use font-display swap with a close fallback font |
Lab data and field data are not the same thing
PageSpeed Insights shows two kinds of results, and mixing them up is the most common source of confusion.
- Field data comes from real Chrome users over roughly the previous 28 days. This is what Google uses to assess your Core Web Vitals.
- Lab data is a single simulated test. It is great for finding causes, but it is not the official verdict.
That means the lab score can change as soon as you fix something, while the field data takes up to about four weeks to catch up. If your site has little traffic, there may be no field data at all, and the lab test is all you have.
A sensible order of work for Core Web Vitals
- Take a full backup of your site.
- Test a few key pages, such as the homepage, a post and a landing page, in PageSpeed Insights, and check the Core Web Vitals report in Search Console.
- Fix server response and caching first, because everything else depends on it.
- Fix the LCP element, usually the hero image.
- Remove, delay or defer scripts that are not needed straight away.
- Reserve space for images, banners and embeds to stop layout shifts.
- Retest, compare with your first results, and keep an eye on Search Console over the following weeks.
Does it affect rankings?
Page experience is a ranking signal, but a modest one. Strong, relevant content still wins over a perfect score on thin content. Think of Core Web Vitals as removing a handicap, and as a way to stop visitors leaving before they read anything. The second benefit is often the bigger one.
Related reading: Elementor mobile PageSpeed fixes, speeding up a WooCommerce store, technical SEO basics and how Google crawls and indexes websites.
Prefer to compare your options first? You can also browse independent WordPress speed specialists on Fiverr, read their reviews and ask for before and after reports before you choose anyone.
Want someone to find and fix the cause?
I check what is actually slowing your WordPress site down, back it up, fix it without touching your design, and send a before and after PageSpeed and GTmetrix report. Send your URL and I will run a free speed check before you order.
View the gig on Fiverr →Message me on WhatsAppQuick answers
Can anyone guarantee a specific PageSpeed or GTmetrix score?
No. Results depend on your hosting, theme, plugins and third-party scripts. A trustworthy provider tells you what is realistic for your site before starting, and shows a before and after report afterwards.
Will my site stay fast after the work is done?
Yes, as long as nothing heavy gets added later. New plugins, large images and extra tracking scripts can slow it down again, so test after every big change.
Do page builders and themes like Elementor, Divi or Astra make this harder?
They can add weight, but all of them can be optimized. The right fixes just differ from site to site.
