Core Web Vitals are three measurements of how a page feels to a real visitor: how fast the main content appears, how quickly the page responds when someone taps or clicks, and whether the layout jumps around while loading. Google calls a page “good” when it loads its main content in 2.5 seconds or less, responds to interaction in 200 milliseconds or less, and shifts by no more than 0.1. For a small-business WordPress site, most of the improvement comes from a short list of unglamorous fixes.
The three numbers, in plain words
| Metric | What it measures | “Good” threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How long until the biggest thing on screen, usually the hero image or heading, is visible | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page reacts after a tap, click or key press | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less |
INP replaced the older First Input Delay metric in 2024, so any guide that still talks about FID is out of date.
Why it matters for a business site
Speed is one signal among many. Google has been clear that relevant, useful content comes first, so a fast page full of thin content will not outrank a slower page that answers the question properly. Speed matters most in two places: it decides whether a visitor stays long enough to read, and it affects the cost of your ads, because slow landing pages waste paid clicks. For a business that gets most enquiries from phones on mobile data, that is real money.
What WordPress 7.0 does and does not change
WordPress 7.0 was released on 20 May 2026. It brought a refreshed dashboard, improved editing tools, groundwork for AI features and some performance and accessibility improvements, including better handling of images. Reviewers disagree on how much it changes front-end speed, and at least one detailed comparison concludes that the bigger recent front-end loading gains came earlier, in WordPress 6.9. The sensible conclusion is that updating is worth doing for security and features, but it will not fix a slow site by itself. Problems caused by heavy images, too many plugins, poor fonts and slow hosting are still yours to solve.
Step 1: measure before you touch anything
- Open the Core Web Vitals report in Google Search Console. It shows real-visitor data grouped by page type.
- Run your home page and one key service page through PageSpeed Insights, on mobile first.
- Write down LCP, INP and CLS for each. Fix one thing at a time and re-test, so you know what worked.
Step 2: fix the biggest causes first
Images (the usual LCP culprit)
- Resize images to the size they are actually shown. A 4,000 pixel photo displayed at 800 pixels wastes bandwidth.
- Use modern formats such as WebP.
- Set width and height on every image so the browser reserves space. This alone fixes most layout shift.
- Lazy-load images below the first screen, but never the hero image at the top. Lazy-loading the main image makes LCP worse.
Fonts
- Use one or two font families, and only the weights you actually use.
- Host fonts on your own server where you can, and use a sensible fallback so text appears immediately.
Plugins and page builders
- Deactivate and delete plugins you do not use. Each one can add scripts and styles to every page.
- Be careful with heavy page builders and “add-on” packs. A lighter theme and the block editor usually load faster.
- Load scripts only where they are needed. A contact-form plugin does not need to run on every blog post.
Third-party scripts (the usual INP culprit)
- Chat widgets, tracking pixels, heat maps and social feeds all run JavaScript that can make taps feel sluggish.
- Keep the ones that earn their place and remove the rest. Load the rest after the page has become interactive.
Caching and hosting
- Use a caching plugin properly configured for your host. LiteSpeed Cache works well on LiteSpeed servers.
- Put a CDN in front of image-heavy sites if visitors come from several countries.
- Run a currently supported PHP version. Newer versions are faster, as long as your theme and plugins support them.
- If your server is slow to respond, no front-end tweak will fully hide it.
Step 3: stop layout jumps
- Reserve space for ads, banners, embeds and cookie notices instead of letting them push content down after load.
- Do not insert content above existing content once the page has started rendering.
- Test on a real phone, not only a desktop browser.
Step 4: keep it fast
Speed decays quietly. Every new plugin, image and tracking script adds weight. Check Search Console’s Core Web Vitals report monthly, compress images before you upload them, and review plugins every quarter.
Frequently asked questions
Is a perfect PageSpeed score necessary?
No. Passing the Core Web Vitals thresholds for real visitors matters more than a score of 100 in a lab test. A score of 100 can come at the cost of features you need.
How long until improvements show in Search Console?
The Core Web Vitals report uses field data collected over roughly the previous 28 days, so improvements appear gradually, not overnight.
Should I switch to a different theme?
Only if measurement shows the theme is the cause. Many sites get most of the gain from images, plugins and caching alone.
The short version
Measure first. Fix images, trim plugins and scripts, reserve space for anything that loads late, and re-test on mobile. Updating to WordPress 7.0 helps, but the large wins are still on your side of the fence.
If you would like a fast, clean site built properly from the start, see our website design service, or ask for a free audit and we will tell you what is slowing yours down.
This article reflects what was publicly reported up to 28 October 2026. Platforms change quickly, so check the official source before you act.