What gets measured
Google rates the loading experience through the Core Web Vitals. Three values matter most:
| Value | What it measures | Target |
|---|---|---|
| LCP | When the largest visible content appears | under 2.5 s |
| CLS | How much the layout jumps while loading | under 0.1 |
| INP | How fast the page reacts to a tap | under 200 ms |
The most important one for perceived speed is LCP: the time until the big image or the headline at the top is visible. If that sits at 5 or 6 seconds, the whole page feels sluggish, no matter how fast the rest loads afterwards.
The most common brakes
On local websites, especially on WordPress and website builders, it is almost always the same points:
- Images that are too large. A photo 4000 pixels wide that is displayed at 400 pixels on a phone wastes load time. The most common single reason for a poor LCP.
- Too many fonts. A theme happily loads the whole font family with all weights and italics, although only three cuts are actually used.
- Render-blocking CSS and JavaScript. Scripts that have to be loaded before anything appears at all, often from plugins and sliders.
- No caching. Without a cache, the server rebuilds every page on every request.
- Sliders and heavy plugins. An image slider on the home page looks smart and is often the single biggest brake.
What actually helps
- Serve images in the right size, compress them in a modern format (WebP or AVIF) and only load what is outside the visible area when it is needed (lazy loading).
- Reduce fonts to the cuts you really use and host them locally.
- Remove unused CSS and JavaScript or load it with a delay.
- Turn on caching, on WordPress via a cache plugin, on a website builder usually built in.
- Skip a real image slider if it is not strictly necessary.
The good part: for all of this you usually do not have to rebuild your website. In most cases the right settings and a few targeted changes are enough.
Measure, do not guess
Measure the current state with Google PageSpeed Insights, always the mobile value. Measure again after every change instead of guessing. That way you see which change really made a difference, and where there is still room.
The usual brakes, and the quick wins
| Brake | Quick win |
|---|---|
| Huge, uncompressed images | Resize and compress; serve modern formats (WebP) |
| Too many plugins or trackers | Remove what you do not use; defer the rest |
| No caching | Turn on a caching plugin or host-level cache |
| Heavy page builder | Trim unused sections; avoid stacking effects |
What the three numbers actually mean
Google grades the experience with three Core Web Vitals: LCP (how fast the main content appears), INP (how quickly the page reacts when you tap) and CLS (whether things jump around as it loads). On mobile, LCP is usually the one that hurts, and a large hero image is usually the culprit. The full plain-language version is in our Core Web Vitals guide.
Measure before you optimise
Do not guess. Run your page through Google PageSpeed Insights on mobile; it names the exact files and scripts holding you back, in order. Fix the biggest one first, measure again, repeat. Two or three targeted fixes usually move the needle more than a full rebuild.