In this article
- What the score actually measures
- LCP: the main content is slow to appear
- Heavy images and outdated formats
- Render-blocking JavaScript and CSS
- Unused code
- Slow server, TTFB and caching
- Fonts that delay or shift text
- CLS: the page “jumps”
- INP: the page doesn’t respond to clicks
- Don’t want to chase every warning yourself?
You opened PageSpeed Insights, entered your site, and saw a red score. The worry hits immediately: are customers leaving before the page loads? Is Google “punishing” you and keeping you out of the results?
That concern is fair. Every second of delay costs you visitors and, often, sales. But the tool throws dozens of warnings at once, and it’s easy to get lost or to chase a perfect 100 for no good reason.
The score isn’t a school grade. It’s a signal about the visitor’s experience. If you understand what it measures and fix the most common issues, the site opens faster. For overall WordPress optimization, see our guide How do I make WordPress faster?. Here we focus on the tool itself: what the numbers mean and how to fix the findings.
What the score actually measures
PageSpeed Insights shows two things:
- Field data: real measurements from Chrome users, when enough data is available. This is also what Google looks at for page experience.
- Lab data: a simulated load, usually on a mobile device with a slower network. This is where the 0–100 score and the list of “errors” come from.
Always check the mobile version first. That’s usually where most visitors are, and that’s where problems show up first.
More important than the score are the Core Web Vitals, the three experience metrics Google uses (web.dev):
- LCP (Largest Contentful Paint): how quickly the main content appears, usually the large image or the heading. Target: within 2.5 seconds.
- INP (Interaction to Next Paint): how quickly the page responds to a click or keypress. Target: within 200 ms.
- CLS (Cumulative Layout Shift): how much the page “jumps” while it loads. Target: 0.1 or less.
You don’t need 100 out of 100. A consistently green result on the Core Web Vitals, especially in real user data, matters more than a perfect lab score.
LCP: the main content is slow to appear
If LCP is red, the page is slow to show what the visitor expects first. The usual causes are a heavy image at the top, a slow server (high TTFB, Time to First Byte), or CSS and JavaScript that block rendering.
Find which element counts as LCP (the tool shows it). Reduce its weight, give it priority with preload, and do not lazy-load it. If TTFB is high, the problem starts with the server or caching, not only with the image.
Heavy images and outdated formats
The image warning shows up on almost every site that hasn’t been set up properly.
- Convert images to WebP or AVIF. They’re smaller than JPEG and PNG, with the same visual quality.
- Upload each image at the size it is displayed. A 4000px photo in an 800px slot delays loading for no reason.
- Lazy-load images further down the page, not the main LCP image.
Render-blocking JavaScript and CSS
The “Eliminate render-blocking resources” warning means the page waits to download CSS or JavaScript before showing anything. Load quickly only the CSS for the first screen. For scripts that aren’t needed immediately (cookie banner, chatbot, analytics), use defer or delay. Don’t load plugins on every page if you only use them on one.
Change one setting at a time, especially on an e-shop: some optimizations “break” menus, forms, or the cart.
Unused code
“Reduce unused JavaScript” and “Reduce unused CSS” mean you’re downloading files that this particular page doesn’t use. The usual culprits are heavy themes, page builders, and plugins that load everything everywhere. Remove what you don’t need and limit files per page, where your caching plugin allows it.
Slow server, TTFB and caching
If the server is slow to respond, compressing an image isn’t enough. You need fast hosting, close to your audience, with modern PHP and server-level caching. Enable page cache, so pages are served ready-made. A CDN helps visitors from other countries and takes load off the server. Set proper caching for static files too (images, CSS, JS).
Without a stable, fast server, the rest of the fixes improve the score a little and then stall.
Fonts that delay or shift text
Custom fonts often slow down text and cause layout shifts. Use font-display: swap, so a fallback font shows immediately. Keep only the fonts and weights you actually use, preload only the main one for the first screen, and host them on your own site to cut down on external requests.
CLS: the page “jumps”
Layout shift frustrates the user and lowers the score. Common causes are images, videos, or ads without a set width and height, fonts that change size when they load, or banners and cookie notices that push the content down. Set dimensions on images and embeds, and reserve stable space for anything that appears after the initial load.
INP: the page doesn’t respond to clicks
If the visitor taps a button and nothing happens for a while, the usual cause is heavy JavaScript: too many scripts at once, or themes and builders that keep running in the background. Reduce and delay anything that isn’t needed for the first click, and check the cart, filters, and menus on mobile in particular.
Don’t want to chase every warning yourself?
Fixing PageSpeed Insights issues isn’t a setting you apply once. It’s the right hosting, the right caching, and regular checks, every time the site changes.
At SmartHost we host and maintain WordPress sites every day. We can measure your site, fix the issues PageSpeed Insights reports, and keep the speed consistent, so you can focus on your business.
Want help with PageSpeed Insights? Get in touch with us at smarthost.gr.
