Website speed
What Core Web Vitals measure and what to fix first.
A speed score is easy to chase and easy to misread. This guide explains the three Core Web Vitals, the difference between lab and field data, and the order in which to look at the usual causes of a slow WordPress site.
The three metrics
Loading, responsiveness and visual stability.
Google describes Core Web Vitals on web.dev (opens in a new tab). Each metric has a “good” threshold, measured at the 75th percentile of page visits, separately for mobile and desktop.
01
LCP: Largest Contentful Paint
How long it takes for the largest visible element, usually a heading, image or video, to appear. Good is 2.5 seconds or less.
02
INP: Interaction to Next Paint
How quickly the page responds after a click, tap or key press, across the whole visit. Good is 200 milliseconds or less. INP replaced First Input Delay in March 2024.
03
CLS: Cumulative Layout Shift
How much the content moves unexpectedly during the visit, for example when an image without dimensions pushes the text down. Good is 0.1 or less.
Lab and field data
A test result is not what visitors experience.
Lab data comes from a single simulated visit, such as a Lighthouse test in PageSpeed Insights. It is useful for finding causes and checking a fix, but it uses one device and one connection.
Field data comes from real Chrome users through the Chrome UX Report, collected over the previous 28 days. The Core Web Vitals report in Search Console uses it. Sites and pages with little traffic often have no field data at all.
An example from this website: on 18 October 2026, PageSpeed Insights gave our home page a lab score of 100 on mobile and desktop, with LCP of 0.9 seconds on mobile, CLS of 0 and a page weight of about 28 KiB. On 10 November 2026, after the home page was redesigned, the median of three tests was 98 on mobile and 100 on desktop, with LCP still 0.9 seconds on mobile, CLS of 0 and a page weight of about 79 KiB. Neither measurement had field data, because the site is new. Until field data exists, the lab result is a technical check, not proof of what visitors experience.
Common causes
Where to look first on a slow WordPress site.
01
Large or late images
An oversized hero image or slider is a very common LCP problem. Serve images at the size they are shown, in a modern format, and do not lazy-load the image at the top of the page.
02
Slow server response
If the first byte arrives late, everything else waits. Page caching, a current PHP version and suitable hosting often matter more than front-end tweaks.
03
Render-blocking CSS and heavy web fonts
Large theme or page-builder stylesheets and several web font files delay the first paint. Remove what the page does not use and limit font weights.
04
Third-party scripts
Chat widgets, tag managers, ads and embedded videos often cause poor INP and long blocking time. List every external script and decide whether it is still needed.
05
Elements without reserved space
Images, ads, embeds and cookie banners without fixed dimensions move the content and raise CLS.
An example from our work: on igrice.hr, the largest element (LCP) on a game page went from 5.95 s to 0.90 s on 23 October 2026, after unnecessary gallery code was removed. It was measured under Lighthouse’s mobile conditions (slow 4G, throttled CPU, no cache). The igrice.hr case study describes the other changes.
Priorities
Fix the metric that fails, on the pages that matter.
- Start with field data in Search Console if it exists, and group pages by template rather than fixing URLs one by one.
- Work on the metric that is outside the good range. A lab score that moves from 92 to 98 rarely changes anything for visitors.
- Fix templates and shared components first, such as the header, hero and footer, because one change improves many pages.
- Re-test after each plugin, theme or tracking change, not only once a year.
Google confirms that Core Web Vitals are used by its ranking systems, but its page experience documentation (opens in a new tab) also says that good results do not guarantee top rankings. Relevant, useful content still comes first.
Checklist
A speed review in eight steps.
- Check the Core Web Vitals report in Search Console and note whether field data exists.
- Test the home page and one page of each main template in PageSpeed Insights, on mobile and desktop.
- Note the LCP element and which phase takes longest: time to first byte, resource load delay, resource load duration or element render delay.
- Compare the size of the largest image with the size at which it is displayed.
- List every third-party script and the reason it is on the site.
- Confirm images, embeds and banners have reserved dimensions.
- Check page caching and the PHP version with your host.
- Write down the results with the date, so the next test has something to compare with.
Speed checks belong in regular maintenance. Our WordPress maintenance checklist covers what to check before and after updates.
Is your site slow after updates?
Tell us which pages slowed down and after which change. We will review the site and agree which checks belong in your WordPress maintenance plan.