Core Web Vitals 2026: the three metrics Google measures
Core Web Vitals cover three specific parameters Google uses to judge the quality of what a visitor actually experiences on your site. Each one has clearly defined boundaries for “good”, “needs improvement” and “poor”.
LCP: largest contentful paint (loading speed)
LCP measures how fast the largest visible element on the page loads, usually the main image at the top or the main headline. The current thresholds, according to official Google data, are:
- Good: up to 2.5 seconds
- Needs improvement: 2.5 to 4.0 seconds
- Poor: more than 4.0 seconds
On WordPress sites the LCP score usually falls apart because of images that were never prepared for the web (a plain JPEG where a modern WebP would do), because of a slow server, or because badly written code blocks rendering and holds the page back.
INP: interaction to next paint (interactivity)
INP is the new measurement, live since March 2024. It measures the time from the moment a visitor does something on the site (a mouse click, a tap on a phone screen, typing text) to the moment the browser visually shows the result of that action. The thresholds are:
- Good: up to 200 milliseconds
- Needs improvement: 200 to 500 milliseconds
- Poor: more than 500 milliseconds
INP is stricter than the old FID, because it tracks every single click and action during a visit, not just the first one. Sites that lean on a lot of heavy background code, such as visual page builders, sliders or complex filters, struggle with this score the most.
CLS: cumulative layout shift (visual stability)
CLS measures how much the parts of a page move around while the site is loading. It happens when ads pop in unexpectedly, when text changes size, or when images have no reserved space and push everything below them down the page. A result counts as good when CLS stays below 0.1.
Sites built in Elementor sometimes have trouble with this sudden shifting. The reason is usually that images do not have exact dimensions (width and height) set, or that custom fonts load too late, so the visitor first sees plain system text and only then the designed typeface.
Where to check Core Web Vitals for your WordPress site
Before you start speeding anything up, you need to know where you stand. There are two kinds of data: lab data, which is a simulation, and field data, which comes from real visitors.
Google Search Console: field data (real visitors)
The Google Search Console report shows information collected from real people visiting your site. This is the most important source, because it shows exactly what Google is actually scoring.
If the site is new or has few visitors, the tool may report that there is not enough data. In that case, fall back on simulated lab data.
PageSpeed Insights: lab data (simulation)
Google PageSpeed Insights combines a simulated measurement with real user data, when there is enough of it. Simulations are excellent for finding exactly where the problem sits, in other words for diagnosis, but they do not always show how the site really behaves on different phones and different connection speeds for real visitors.
Chrome DevTools: developer tooling
For the most detailed check available, the developer tools inside Chrome (the performance panel and the Lighthouse tab) give you a precise view of which file is slowing the page down. This level of analysis is a required part of professional website maintenance.
Improving LCP on WordPress sites
LCP is the metric you have the most control over, and it is where cleaning up a WordPress site produces the fastest, most visible results.
The hero image: WebP and early loading
The big image at the top of the page, the hero image, is the main culprit behind a bad LCP score in about 80% of cases. Three steps are mandatory:
- Convert images to WebP: move all of your featured images to this modern format. If you use Elementor Pro, use its built in image optimization, or reach for a dedicated plugin such as Imagify or ShortPixel.
- Preload the image: put a directive in the site header so the browser fetches that first image ahead of everything else:
<!-- Goes in the WordPress theme <head> or through a plugin such as Perfmatters -->
<link rel="preload" as="image" href="/wp-content/uploads/hero-slika.webp"
fetchpriority="high">
- Turn off lazy loading for the first image: the hero image must not have it enabled, otherwise it shows up too late. For every other image on the page, lazy loading is very much worth having.
Good hosting and server speed
Slow hosting drags the LCP score down directly. The time the server needs to send the first byte of data to the visitor has to stay under 600 milliseconds. That is why we mostly use fast LiteSpeed servers for client projects, paired with their official caching plugin, LiteSpeed Cache.
Render blocking code
Files that control the look and the behavior of the site, and that try to load before the page structure itself, stop the site from rendering for the visitor. The fix is simple: defer every script that is not needed right away, and inline the design code for the part of the page the visitor sees first.
Improving INP and CLS on Elementor sites
Elementor by itself produces a lot of background code that slows down how quickly a site responds and hurts the INP score. Here is what you can actually do about it.
Improving the INP score (how fast the site responds)
The usual suspects behind bad INP scores on Elementor sites are:
- Heavy image slider plugins, especially the ones that pile on animations
- Too many live chat widgets and assorted tracking scripts
- Poorly written contact form plugins that load all of their code even on pages that have no form at all
The fix: go into Elementor settings and turn on the advanced options for shipping only the elements you need and for optimized loading (Optimized DOM Output and Improved Asset Loading). They cut down the amount of unnecessary code the visitor’s device has to process.
Preventing content jump (CLS) in Elementor Pro
To avoid the page shifting under the reader:
- Every image needs an exact height and width. Elementor usually handles this automatically, as long as you upload the image through the regular media library with correct data.
- Set web fonts so text displays immediately, or consider using standard system fonts for body copy, if that fits your brand.
- Ads and embedded third party elements, such as YouTube videos or Google Maps, need a placeholder of fixed dimensions reserved up front. That way the rest of the text does not jump down when the video finally loads.
Core Web Vitals 2026 is not a one time job
Core Web Vitals 2026 is not something you configure once and forget forever. Every new plugin, every new image and every design update can affect speed. That is why the state of the site has to be monitored regularly.
Turn on alerts in Google Search Console so you get an email the moment speed scores drop. Also run a quick performance check after every larger change. Treat speed and site behavior as routine hygiene and part of professional website maintenance, not as something you only look at once there is a problem.
Planning a new site and want every Google test in the green from day one? Every project under our website development service already includes full speed work and optimization at no extra charge. Get in touch for details.
Frequently asked questions about Core Web Vitals 2026
Does a bad Core Web Vitals score directly push a site down in Google search?
Yes. Loading speed and interaction are part of what Google treats as page experience, and that is an official ranking factor. Still, Google has been clear that genuinely useful content remains the absolute priority. A site with great writing and a poor speed score can still sit on page one. But when two sites have equally good content, the faster one with better technical scores wins.
What is the difference between the new INP metric and the old FID?
The old FID only tracked the first action a visitor took on the site, and only how long the site needed to start processing that command. INP tracks absolutely every interaction across the whole visit and measures the total time until the visitor actually sees the change on screen. That makes INP a far more complete, and far stricter, score.
Which plugin is best for speeding up WordPress sites?
If your site runs on a LiteSpeed server, their official LiteSpeed Cache plugin is a complete solution. It covers caching, image compression and stripping unnecessary lines of code out of your site. For other server types, WP Rocket is an excellent paid option that delivers great results. Perfmatters is useful when you want fine grained control over what loads on a given page. Worth knowing: all of these plugins need precise manual tuning, because the factory settings are rarely the best option.
Does using Elementor slow a site down and hurt the score?
Elementor does generate more design and functionality code than a site coded from scratch, and that can slow loading down if nobody pays attention. Even so, with the right settings inside the builder, carefully compressed images, unused elements removed and genuinely fast hosting, excellent speed test results are entirely achievable. The paid Pro version of Elementor offers considerably better performance options than the free one.
How often should Core Web Vitals be checked?
At least once a month, as part of a regular technical review. A check is mandatory every time you make a larger change, such as a design update, new plugins or a big batch of new content. Google Search Console will email you a warning on its own if scores fall below the allowed threshold, so just make sure those notifications are turned on in your account settings.
