What the metrics measure
Core Web Vitals are Google’s measures of real-world page experience:
- Largest Contentful Paint (LCP) measures how quickly the main content appears. Google’s guidance considers 2.5 seconds or less good.
- Interaction to Next Paint (INP) measures responsiveness to user input across the visit. A value of 200 milliseconds or less is considered good.
- Cumulative Layout Shift (CLS) measures visual stability. A score of 0.1 or less is considered good.
Check Google’s current documentation for thresholds. The metrics are assessed at the 75th percentile of real visits, so they reflect the experience of typical and slower users, not just your fast laptop.
Diagnose before changing things
- Use field data. Check the Core Web Vitals report in Search Console and the Chrome User Experience Report through PageSpeed Insights.
- Use lab tools for debugging, such as Lighthouse and browser developer tools, remembering that lab results differ from field data.
- Test the key templates: home page, blog post, category, product, cart and checkout.
- Test on a mid-range phone and a throttled connection.
- Look at the waterfall to find slow servers, big files and blocking scripts.
Fix what the data shows, not generic checklists.
Common WordPress causes and fixes
| Symptom | Typical cause | Fix |
|---|---|---|
| Slow server response | Cheap shared hosting, no page caching, slow database | Better hosting, full-page caching, object caching, PHP updates |
| Poor LCP | Large hero image, slow font loading, render-blocking CSS | Compress and size images, preload the LCP image, avoid lazy loading it, optimize CSS delivery |
| High INP | Heavy JavaScript, many plugins, long tasks | Remove or delay scripts, simplify page builder output, break up long tasks |
| High CLS | Images without dimensions, late-loading ads and embeds, web fonts swapping | Set width and height, reserve space, use font-display and preload fonts |
| Heavy pages | Page builders, bloated themes, sliders | Lightweight theme, fewer widgets, remove sliders |
| Many requests | Plugins loading assets everywhere | Load scripts only on pages that need them |
| Database slowness | Autoloaded options, transients, old revisions | Clean and index, limit revisions |
Hosting and caching
Quality hosting with current PHP, adequate resources and server-level caching often gives the biggest single gain. Add page caching so most visitors receive prebuilt HTML, and a content delivery network for static assets. For logged-in or dynamic pages, such as carts, use object caching and exclude dynamic content from page cache rules. Test checkout carefully after enabling caching.
Images and media
- Resize to the dimensions displayed.
- Use modern formats such as WebP or AVIF where supported, with fallbacks.
- Lazy-load below-the-fold images, but not the main hero image.
- Set explicit width and height attributes.
- Compress video, or host through a video service and load it on interaction.
- Use responsive image attributes, which WordPress adds when it generates sizes.
Theme and page builder choices
Themes and builders differ widely in output weight. Choose lightweight themes, avoid stacking multiple builders and test pages after building. Remove unused features, fonts and icon libraries. Consider custom blocks for repeated components.
Plugins and scripts
Audit plugins. For each, ask whether it is needed, what it loads and whether a lighter alternative exists. Deactivate and delete unused plugins. Review third-party scripts such as chat, analytics, ads and social embeds, which commonly harm INP and LCP. Delay non-essential scripts until interaction, and load them conditionally. Use a tag manager thoughtfully, since it can also become a dumping ground.
Fonts
Limit the number of font families and weights, self-host where appropriate, preload critical fonts and use a fallback display strategy to avoid invisible text and layout shifts.
WooCommerce specifics
Product pages, carts and checkout are dynamic. Reduce plugin overhead, avoid heavy cart fragments requests on every page, optimize product images and test with real catalog sizes. High-performance order storage and database optimization can help large stores.
Keep it fast
Performance regresses over time. Add performance checks to your process: test before and after plugin or theme changes, set a budget for page weight and scripts, and monitor Core Web Vitals monthly.
FAQ
Do Core Web Vitals affect rankings?
They are part of Google’s page experience signals, but content relevance matters more. Poor performance also hurts conversion and usability regardless.
What is the quickest win for a slow WordPress site?
Often better hosting with page caching, followed by image optimization and removing unnecessary plugins and scripts.
Why is my lab score good but my field data poor?
Real users have slower devices and networks, and field data covers whole visits. Use field data to prioritize and lab tools to debug.
Do I need a developer to fix this?
Some fixes are simple settings, while theme, script and database problems often need developer help.
Sources and further guidance
Platform features and requirements change. Check the linked primary documentation for your implementation.
TURN INSIGHT INTO ACTION
Let’s talk about your next step.
Share your workflow, your current systems and what you want to improve. We’ll help shape a practical way forward.
Discuss your project ↗