How to Speed Up a WordPress Site: A Beginner's Guide to PageSpeed Insights
Google PageSpeed Insights grades your site on Core Web Vitals — the same signals that influence your search ranking. This guide explains LCP, CLS, and TBT in plain English for WordPress owners, and shows you what to do about each.
Why PageSpeed matters for WordPress
A slow site loses visitors and search rank. Google uses Core Web Vitals as a ranking signal, and WordPress sites are particularly prone to bloat: heavy themes, unoptimized images, and stacks of plugins each add render-blocking work. The good news — these problems have well-known fixes, and most of them can be automated.
LCP — Largest Contentful Paint
What it is: How long it takes for the largest visible element (usually your hero image or headline) to render.
Why WordPress sites struggle: WordPress themes often serve full-size, uncompressed hero images and load them after multiple CSS and font files block the render.
How Velocify fixes it: Velocify auto-compresses and serves WebP/AVIF, preloads the LCP image, and inlines critical CSS so the hero paints on the first frame.
CLS — Cumulative Layout Shift
What it is: A score for how much the page jumps around as it loads. High CLS makes users miss-tap and bounce.
Why WordPress sites struggle: Ad slots, embedded videos, and images without explicit width/height push content down as they load — the #1 cause of CLS on WordPress.
How Velocify fixes it: Velocify reserves space for images, ads, and embeds by injecting width/height and aspect-ratio so nothing shifts after paint.
TBT — Total Blocking Time
What it is: How long the main thread is frozen by JavaScript before the page becomes interactive.
Why WordPress sites struggle: Plugin JavaScript (analytics, chat widgets, page builders) stacks up and blocks the browser long after the page looks ready.
How Velocify fixes it: Velocify defers non-critical scripts, removes unused JS from page-builders, and lazy-loads third-party widgets until the user interacts.
FCP — First Contentful Paint
What it is: When the user sees the first pixel of content — a sign the page is alive.
Why WordPress sites struggle: Slow shared hosting and render-blocking CSS push FCP into the 3–5s range, even on a 'fast' theme.
How Velocify fixes it: Velocify enables HTTP/2 push for critical assets and edge-caches the HTML so the first byte arrives in under 200ms.
How to read your PageSpeed score
- 90–100 (green): Healthy. Maintain it.
- 50–89 (orange): Needs work. Usually fixable with caching and image optimization alone.
- 0–49 (red): Failing. Plugins or theme are blocking the main thread — start there.
Always check the mobile tab first. Google uses mobile scores for ranking, and most WordPress sites score 20–30 points lower on mobile than desktop.
A 5-minute speed checklist for WordPress
- Compress every image — convert to WebP, keep originals under 200KB.
- Enable a page-cache plugin (or use a host that ships one).
- Defer JavaScript that isn't needed for the first paint.
- Preload your hero image and brand font.
- Audit plugins — remove anything you haven't used in 30 days.
Skip the checklist — let Velocify do it
Velocify scans your WordPress site, identifies every PageSpeed issue, and applies the fixes automatically. No code, no plugins to configure — just a faster site.
Run a free speed scanFAQ
What is a good PageSpeed Insights score for WordPress?
Aim for 90+ on mobile. 50–89 needs work; below 50 is failing and almost always fixable with caching, image optimization, and reducing render-blocking assets.
How do I speed up a WordPress site?
Compress and lazy-load images, enable page caching, minify and defer JavaScript, preload your hero image, and remove unused plugins. Velocify automates all of this.
What's the difference between LCP, CLS, and TBT?
LCP measures how fast the largest element paints. CLS measures unexpected layout shifts. TBT measures how long the main thread is blocked by JavaScript before the page is interactive.