What is a good PageSpeed score?

The score is a lab estimate that changes between runs. Focus on Core Web Vitals from real users in Search Console, and aim for the good thresholds.

Do caching plugins fix everything?

No. Caching helps server response time, but heavy images, too many scripts and layout shifts still need fixing directly.

Should I change themes?

If your theme loads large frameworks or sliders on every page, a lighter theme can be the single biggest improvement. Test on a staging copy first.

WordPress Speed and Core Web Vitals: What to Fix First

By Repvox Digital editorial team Published October 25, 2026 2 min read

Code editor open on a laptop during website optimisation

Numbers in this article are industry data from the sources linked or simple examples, not Repvox results. Your market and results will differ.

In this article

Slow pages cost you visitors and paid clicks. Google measures page experience with three Core Web Vitals. According to web.dev (Google), a page is "good" when, for at least 75% of visits:

LCP (Largest Contentful Paint) is 2.5 seconds or less: how fast the main content appears.
INP (Interaction to Next Paint) is 200 milliseconds or less: how quickly the page responds to taps and clicks.
CLS (Cumulative Layout Shift) is 0.1 or less: how much the layout jumps around.

Here is the order in which we fix WordPress sites in our website speed service.

1. Measure real users first

Open Search Console's Core Web Vitals report to see which page groups fail on mobile and desktop. Then test a representative page in PageSpeed Insights. Fix the templates that affect the most pages first.

2. Images

Serve WebP or AVIF in the right size for the screen, using srcset.
Do not lazy-load the hero image. Give it high fetch priority instead.
Always set width and height (or aspect-ratio) so the layout does not jump.

3. Plugins and page builders

Every plugin can add CSS and JavaScript to every page. List your plugins, remove what you do not use, and replace heavy ones (sliders, multiple analytics plugins, social feeds) with lighter options. Heavy page builders often load large libraries site-wide.

4. Third-party scripts

Chat widgets, heatmaps, multiple pixels and embedded maps or videos are common INP problems. Load them through Tag Manager after consent and after the page loads, and use click-to-load facades for maps and videos.

5. Fonts

Self-host fonts, limit yourself to two weights, use font-display: swap, and preload only the main heading font. A fallback font with matching metrics reduces layout shift.

6. CSS and JavaScript

Defer non-critical JavaScript, remove unused CSS where your setup allows it, and avoid scripts that block rendering in the head.

7. Caching, CDN and hosting

Page caching and a CDN (for example Cloudflare) cut server response time. If your time to first byte is still slow, the hosting plan may be the bottleneck.

8. Layout shifts

Reserve space for images, embeds, ads and cookie banners. Avoid inserting content above what is already visible.

Keep it fast

Speed slips when new plugins and tags are added. Check Search Console monthly and test before installing anything new. If you want us to handle it, see WordPress development or request a free audit.