A slow WordPress site costs you twice: visitors leave before it loads, and Google says Core Web Vitals align with what its ranking systems reward. The fix is rarely one magic plugin. It is a short list of changes, done in the right order.
What are Core Web Vitals?
Core Web Vitals are three Google metrics that measure real users’ experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). A page passes when at least 75% of visits meet the “good” threshold for all three, based on real Chrome user data.
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | When the main content appears | ≤ 2.5 s | > 4.0 s |
| INP (Interaction to Next Paint) | How fast the page responds to taps and clicks | ≤ 200 ms | > 500 ms |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | ≤ 0.1 | > 0.25 |
Thresholds from Google’s Core Web Vitals definitions.
Step 1: Measure before you change anything
- Run your key pages through PageSpeed Insights (pagespeed.web.dev). Look at the field data first; that is what Google uses.
- Open Search Console → Core Web Vitals to see which groups of pages fail on mobile and desktop.
- Note the LCP element PageSpeed reports. It is often a hero image or heading.
Step 2: Fix the server (biggest impact on LCP)
- Use good hosting. Cheap shared hosting is the most common cause of slow WordPress sites.
- Run a current PHP version supported by your host and plugins.
- Enable page caching through your host or a caching plugin, so pages are not rebuilt on every visit.
- Use a CDN to serve images and files from locations near your visitors.
Step 3: Optimize images
- Resize images to the size they are displayed. Do not upload a 4000px photo for a 600px slot.
- Serve modern formats such as WebP or AVIF.
- Do not lazy-load the hero image. Lazy-loading the LCP image delays it; lazy-load images further down instead.
- Always set width and height on images to prevent layout shift (CLS).
Step 4: Cut plugin and script bloat (biggest impact on INP)
- Audit plugins. Remove anything inactive or duplicated. Fewer, well-built plugins beat many small ones.
- Watch page builders. They often load scripts and styles on pages that do not use them.
- Delay third-party scripts like chat widgets, heatmaps and social embeds until after the page loads or the user interacts.
- Avoid long JavaScript tasks. Heavy sliders and animation libraries are common INP problems.
Step 5: Stop layout shift (CLS)
- Reserve space for images, videos, ads and embeds.
- Preload your main web fonts and use
font-display: optional, orswapwith a size-matched fallback font, to avoid layout shift. - Do not inject banners or cookie bars above existing content after load; overlay them instead.
Step 6: Keep it fast
- Re-test after every theme, plugin or design change.
- Keep WordPress core, themes and plugins updated.
- Review Search Console’s Core Web Vitals report monthly.
Quick checklist
- Field data checked in PageSpeed Insights
- Quality hosting, current PHP, page caching on
- CDN enabled
- Images resized, WebP/AVIF, dimensions set
- Hero image not lazy-loaded
- Unused plugins removed
- Third-party scripts delayed
- Fonts preloaded with a stable fallback, no late-loading banners
If you would rather hand this off, RouteSync’s WordPress development and maintenance service includes speed audits and fixes, and our web development team builds fast sites from the start.
Key takeaways
- Targets: LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1 at the 75th percentile.
- Fix in order: hosting and caching → images → plugins and scripts → layout shift.
- Never lazy-load the hero image, and always set image dimensions.
- Use field data, not just lab scores, to judge progress.
Frequently asked questions
What are good Core Web Vitals scores?
A page passes when, at the 75th percentile of real visits, Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less.
Why is my WordPress site slow?
The most common causes are slow hosting, large uncompressed images, too many or heavy plugins, page builders loading unused scripts, no page caching and third-party scripts such as chat widgets and trackers.
How do I test my WordPress site speed?
Use PageSpeed Insights (pagespeed.web.dev) to see real-user Core Web Vitals and lab diagnostics, and the Core Web Vitals report in Google Search Console to see which page groups fail.