Slow, jumpy pages lose visitors and rankings. WordPress Core Web Vitals are the three measurements Google uses to judge how fast your site loads, how quickly it responds and how stable it looks. Themes, page builders and plugins all affect them.
This guide explains each metric in plain language, shows what usually breaks it on a WordPress site and gives you a clear order for fixing it.
Quick answer
Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (visual stability). Good scores are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less. On WordPress, the usual causes are heavy images, too many plugins and scripts, bulky themes and banners that shift the layout.
What are WordPress Core Web Vitals?
WordPress Core Web Vitals are the page-experience metrics Google measures on real visits to your WordPress site: how fast the main content appears, how fast the page reacts to taps and clicks, and how much the layout moves while loading.
| Metric | What it measures | Good score | Common WordPress cause |
|---|---|---|---|
| LCP | Time until the largest element appears | 2.5 s or less | Large hero image, slow hosting |
| INP | Delay between a tap and the page responding | 200 ms or less | Heavy JavaScript from plugins and page builders |
| CLS | How much the layout shifts | 0.1 or less | Images without sizes, late banners and ads |
Fix LCP first
On most pages, the largest element is the hero image or the main product or post image. Make that one element fast.
- Resize and compress the image to the size it is displayed. See WordPress image optimization.
- Use WebP or another modern format.
- Do not lazy-load the first image on the page.
- Use page caching and a host with a fast server response.
- Limit web fonts to one or two families.
Improve INP by cutting JavaScript
INP punishes pages that look ready but ignore the visitor. The cause is usually too much JavaScript running at once.
- List every script loaded on your key pages.
- Remove plugins and widgets you no longer use.
- Delay non-essential scripts, such as chat widgets and trackers.
- Test real actions: open the menu, submit a form, add an item to a cart.
Features such as a slide-out cart or a quick view popup should update through AJAX without reloading the page, and should load their code only where it is needed.
Reduce CLS so nothing jumps
- Set width and height on every image and embed.
- Reserve space for banners, cookie notices and ads.
- Never insert new content above what the visitor is reading.
- Choose a fallback font close to your web font’s size.
How do you test Core Web Vitals in WordPress?
To test Core Web Vitals in WordPress, run key pages through PageSpeed Insights for a quick check and review the Core Web Vitals report in Google Search Console for real-visitor data collected over time.
- Test your homepage, a blog post and your most important landing page.
- Check mobile first, because most scores are worse there.
- Fix the biggest issue, then retest.
- Recheck monthly, and after every theme or plugin change.
Keep your plugin list light
Every plugin adds code. The best ones load scripts and styles only on the pages that use them. Read how to choose WordPress plugins before adding anything new, and test changes on a staging site.
If you run a shop, browsing features matter too. See Infinite Scroll vs Pagination and make sure product lists stay fast on phones. For more on small screens, read WordPress mobile optimization.
Core Web Vitals checklist
- Main image compressed, sized and not lazy-loaded
- Width and height set on all images
- Caching and fast hosting in place
- Unused plugins and scripts removed
- Space reserved for banners and notices
- Mobile tested first
- Search Console report checked monthly
Add features without slowing your site
Siteryn plugins load assets only on the pages that use them, which helps protect your PageSpeed score and Core Web Vitals.
Frequently Asked Questions
What is a good LCP score for a WordPress site?
An LCP of 2.5 seconds or less is considered good. Focus on the largest image or text block above the fold, and make sure it loads first.
Do WordPress plugins hurt Core Web Vitals?
They can, mainly through extra JavaScript and CSS. Plugins that load assets only where needed have much less impact. Test each new plugin before you go live.
Did INP replace FID?
Yes. INP replaced First Input Delay as a Core Web Vital in March 2024. It measures the responsiveness of all interactions on a page, not only the first one.
How often should I test Core Web Vitals?
Check Search Console monthly and retest after every major theme, plugin or design change. Field data takes weeks to update, so give changes time.
Final Thoughts
Core Web Vitals are a habit, not a one-time fix. Keep images light, scripts few and layouts stable.
Start with your most visited pages, fix LCP first and retest after every change.
