How to Make Your Website Faster: A Simple Guide to Core Web Vitals
A slow website loses visitors and customers. This beginner-friendly guide explains Core Web Vitals (LCP, INP and CLS), how to test your site for free, and 15 practical fixes that make any website faster.

In this article (8 sections)ShowHide
- Why website speed matters
- What are Core Web Vitals?
- LCP: how fast the main content shows
- INP: how fast the page responds
- CLS: whether the page jumps around
- How to test your website speed for free
- 15 practical fixes to make your website faster
- Images (usually the biggest win)
- Code and scripts
- Server and hosting
- Layout and experience
- Fixes for popular platforms
- A simple 30-minute speed routine
- Common myths about website speed
- Quick answers
People don't wait for slow websites. If your page takes too long to show, they press back and open the next result, often your competitor's. Google notices this too, which is why it measures website speed with three scores called Core Web Vitals.
The good news: you don't need to be a programmer to understand them, and most fixes are simple. This guide explains Core Web Vitals in plain words, shows you how to test your website for free, and gives you 15 practical fixes that work for WordPress, custom websites and online shops.
Why website speed matters
- Visitors leave slow pages. Every extra second of waiting means more people give up, especially on mobile data.
- Speed affects sales. A faster checkout and faster product pages mean fewer abandoned carts.
- Google uses it. Page experience, including Core Web Vitals, is one of the signals Google uses. Great content still matters most, but when two pages are equally useful, the faster one has an edge.
- Mobile users are the majority. Most visitors use phones, often on slower connections, so a site that feels fine on office Wi-Fi may feel slow to customers.
What are Core Web Vitals?
Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors. Each one answers a simple question.
| Metric | The question it answers | Good | Needs work | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast does the main content appear? | 2.5 s or less | up to 4 s | over 4 s |
| INP (Interaction to Next Paint) | How quickly does the page react when I tap or click? | 200 ms or less | up to 500 ms | over 500 ms |
| CLS (Cumulative Layout Shift) | Does the page jump around while loading? | 0.1 or less | up to 0.25 | over 0.25 |
Google looks at what most of your real visitors experience (the 75th percentile), not just your own fast computer.
LCP: how fast the main content shows
Largest Contentful Paint measures when the biggest thing on the screen, usually the main image, banner or headline, finishes loading. If your homepage banner takes five seconds, visitors stare at a half-empty page for five seconds.
Common causes of slow LCP: huge images, slow hosting, too many scripts loading first, and fonts or sliders that block the page.
INP: how fast the page responds
Interaction to Next Paint measures the delay between a visitor's action, such as tapping a menu, a button or an "Add to cart", and the page visibly responding. It replaced an older metric called FID in 2024 because it measures every interaction, not just the first.
Common causes of poor INP: too much JavaScript, heavy plugins, chat widgets, tracking scripts and large page builders keeping the browser busy.
CLS: whether the page jumps around
Cumulative Layout Shift measures unexpected movement. You've seen it: you go to tap a link, an ad or image loads above it, and you tap the wrong thing. That's frustrating, and on a checkout page it can cost a sale.
Common causes of high CLS: images without set sizes, ads and banners that appear late, cookie notices that push content down, and web fonts that swap in late.
How to test your website speed for free
You don't need paid tools. Start with these:
- PageSpeed Insights (pagespeed.web.dev): enter your page address. The top part shows real visitor data (if your site has enough traffic), and the lower part is a lab test with a list of suggestions.
- Google Search Console: the Core Web Vitals report groups your pages into Good, Needs improvement and Poor, for mobile and desktop separately.
- Chrome DevTools Lighthouse: right-click a page, choose Inspect, open the Lighthouse tab and run a report. Useful for testing changes before you publish them.
Tips for testing:
- Always check mobile results first. They're usually worse, and they matter most.
- Test several important pages, not just the homepage: a product page, a blog post, your contact page.
- Run each test two or three times. Results vary a little each run.
- Real visitor data updates slowly (it covers about the last 28 days), so give fixes time to show.
15 practical fixes to make your website faster
Images (usually the biggest win)
- Resize images before uploading. A photo straight from a phone can be several megabytes. A banner rarely needs to be wider than about 1600 pixels.
- Use modern formats. WebP and AVIF images are much smaller than JPG and PNG at the same quality.
- Lazy-load images below the fold. Images further down the page should load only when the visitor scrolls near them.
- Don't lazy-load the main image. The top banner or product photo should load first. Lazy-loading it makes LCP worse.
- Always set image width and height. This lets the browser reserve the space, which stops the page jumping (better CLS).
Code and scripts
- Remove what you don't use. Every unused plugin, slider, font and tracking script adds weight. Review them every few months.
- Delay non-essential scripts. Chat widgets, social feeds and some tracking can load after the page is ready.
- Minify and combine files. Removing spaces and comments from CSS and JavaScript makes files smaller. Most caching plugins and modern frameworks do this automatically.
- Limit web fonts. Use one or two font families and only the weights you need. Self-hosting fonts and using
font-display: swaphelps text appear quickly.
Server and hosting
- Turn on caching. Page caching serves a ready-made copy of your page instead of building it for every visitor. On WordPress, use a caching plugin your host supports.
- Use a CDN. A content delivery network stores copies of your images and files on servers around the world, closer to your visitors.
- Choose decent hosting. If your server takes more than about a second to respond, no amount of image work will fully fix it. See our guide to shared hosting vs VPS vs cloud hosting.
- Keep software updated. Newer versions of PHP, Node.js, WordPress and frameworks are often faster, and they're safer too.
Layout and experience
- Reserve space for ads, banners and embeds. Give them a fixed-size box so content doesn't jump when they load.
- Keep the top of the page simple. A clear headline, one main image and a button load faster and convert better than a heavy auto-playing slider.
Fixes for popular platforms
WordPress
- Use a lightweight theme instead of a heavy multipurpose one.
- Install one good caching plugin, not several that fight each other.
- Use an image optimisation plugin that converts to WebP.
- Check plugins one by one: a single badly written plugin can slow the whole site.
Custom sites (React, Next.js, Laravel)
- Use the framework's built-in image component or helpers for resizing and lazy-loading.
- Split large JavaScript bundles so each page loads only the code it needs.
- Render important content on the server so it appears before JavaScript finishes.
- Cache pages that don't change often, and refresh them when content is updated.
Online shops
- Compress product photos and use the same image size across the catalogue.
- Keep checkout pages free of extra scripts and pop-ups.
- Show prices and the "Add to cart" button quickly, before reviews and recommendations load.
A simple 30-minute speed routine
Do this once a month:
- Run PageSpeed Insights on your 3 most important pages, on mobile.
- Note the LCP, INP and CLS results in a simple sheet.
- Fix the top suggestion on each page, usually images or an unused script.
- Check Search Console for any pages moved to "Poor".
- Remove one plugin or script you no longer need.
Small, regular improvements beat one big rebuild every few years.
Common myths about website speed
- "A score of 100 is required." No. The lab score is a guide. What matters most is that real visitors get Good Core Web Vitals.
- "Speed only matters for big sites." Small businesses benefit the most, because each lost visitor is a bigger share of their customers.
- "More plugins make it better." Often the opposite. Each one adds code to every page.
- "My site is fast on my computer, so it's fine." Your visitors use different phones and networks. Test on mobile.
Quick answers
What is a good page load time? Aim for the main content to appear within 2.5 seconds on mobile (a good LCP), and for the page to respond to taps within 200 milliseconds.
Do Core Web Vitals affect Google ranking? They're part of Google's page experience signals. They won't beat better content, but they can help when pages are otherwise similar, and they improve conversions either way.
Why is my mobile score lower than desktop? Phones have slower processors and often slower connections, so heavy images and scripts hurt more on mobile.
Can I improve speed without a developer? Yes. Resizing images, removing unused plugins and turning on caching fix most problems on most sites.
Want a faster website without the guesswork? Contact our team for a speed check, or read about getting a professional website for your business.


