The fastest way to improve website loading speed is to measure your slowest pages, then fix the biggest problems first. On many sites, that means compressing large images, reducing JavaScript and third-party scripts, caching content, and improving slow server responses.
Speed can affect your results as well as your visitors' experience. In a Vodafone A/B test published by web.dev, an optimized landing page with a 31% better Largest Contentful Paint produced 8% more sales. That's one company's result, so yours may differ.
Google also says its ranking systems use Core Web Vitals. Good scores don't guarantee good rankings, though, so speed should support helpful content rather than replace it.
Measure your speed first
Start with PageSpeed Insights, which can show both real-user data and a controlled test of the page. Test your homepage and your most important pages, such as product, service, or landing pages, on mobile as well as desktop.
These are the three Core Web Vitals to watch. Google's targets are measured at the 75th percentile of real visits:
Metric | What it measures | Good | Poor |
|---|---|---|---|
Largest Contentful Paint (LCP) | How quickly the main content appears | 2.5 seconds or less | Over 4 seconds |
Interaction to Next Paint (INP) | How quickly the page responds | 200 milliseconds or less | Over 500 milliseconds |
Cumulative Layout Shift (CLS) | How much the layout moves unexpectedly | 0.1 or less | Over 0.25 |
Real-user data shows what visitors actually experience, so use it to judge results where it's available. Lab test scores are most useful for finding the cause of a problem. Don't chase a perfect score of 100 if your real-user numbers are already good.
8 practical ways to speed up your website
1. Optimize your images
Images are often the heaviest part of a page. Figures from the 2025 Web Almanac, as reported by MS Logic, put images at about 911 KB of a median 2.56 MB mobile home page.
Resize images to the size they actually display.
Compress them, and use modern formats such as WebP or AVIF.
Set a width and height to help prevent layout shifts.
2. Load images in the right order
Chrome's guidance recommends giving your main hero image high priority and lazy loading standard images further down the page. Never lazy load the image that's likely to be your LCP element, because that can delay your main content.
3. Reduce JavaScript
The 2025 Web Almanac, as summarized by CSS-Tricks, reported 697 KB of JavaScript on the median mobile page. Too much JavaScript can slow loading and make a page feel unresponsive.
Remove code, plugins, and features you no longer use.
Load scripts only on the pages that need them.
Break long-running tasks into smaller pieces if you have a developer.
4. Audit third-party scripts
Analytics tools, chat widgets, ad tags, and social media embeds all add extra work. List every script on your site, remove anything you don't need, and delay non-essential tools until after the main content loads.
5. Use caching
Caching stores copies of files or pages so they don't have to be rebuilt or downloaded on every visit. Set browser caching for files that rarely change, and use page caching if your content management system builds pages on request.
6. Use a content delivery network
A content delivery network (CDN) serves files from locations closer to your visitors. This is especially useful if your audience is spread across countries such as the USA, UK, and Australia.
7. Improve your hosting and server response
If your server is slow, every later step starts late. Check your database and plugins for slow processes, keep your software up to date, and consider better hosting if your server regularly struggles.
8. Optimize fonts and prevent layout shifts
Use fewer font families and weights, and host them efficiently. To reduce unexpected movement, reserve space for images, ads, and embeds before they load.
What to fix first
Match the fix to the metric that's failing:
Problem | Start with |
|---|---|
Slow LCP | Hero image, server response, render-blocking files |
Poor INP | JavaScript, third-party scripts, long-running tasks |
High CLS | Image dimensions, ads, embeds, banners, fonts |
Then follow this simple process:
Record your current numbers. Save the results for your most important pages.
Make one change at a time. This shows you what actually helped.
Test on a staging site if you can. Performance changes can break menus, forms, or tracking.
Recheck after release. Lab scores update right away, but real-user data can take weeks to reflect a change.
Monitor regularly. New plugins, images, and scripts can slow a site down again.
Common mistakes to avoid
Testing only the homepage: forms, product pages, and search results may be slower.
Ignoring mobile: a page can feel fast on your office computer but slow on a mid-range phone.
Installing several speed plugins: overlapping tools can conflict with each other.
Lazy loading everything: this can delay the content visitors see first.
Chasing a score over the experience: focus on real pages and real-user results.
You don't need to rebuild your site to see progress. Start by compressing your largest images and removing scripts you don't need, then measure again.
Sources
Chrome for Developers. Optimize image priority.
CSS-Tricks, via Frontend Feeds. HTTP Archive 2025 Web Almanac.
Google Search Central. Understanding page experience in Google Search results.
Google Search Central. The role of page experience in creating helpful content. April 2023.
MS Logic. Image optimization, citing the Web Almanac.
PageSpeed Insights. Test your page.
Specification.website. Core Web Vitals (LCP, INP, CLS), citing web.dev.
web.dev. Vodafone: A 31% improvement in LCP increased sales by 8%. March 2021.
