PageSpeed Insights Core Web Vitals report on a phone, showing how to improve website speed

How to Improve Website Speed: 9 Steps (2026 Guide)

•8 min read

How to improve website speed comes down to one habit: measure what your real visitors experience, fix the biggest bottleneck, and measure again. The short answer: find out which metric is failing (main content loading, response to taps and clicks, or layout jumping around), then fix images, third-party scripts and server caching first. This guide walks you through 9 steps, the order to do them in, and the mistakes that waste the most time.

We build and maintain business websites and online stores, and the fixes that matter are rarely exciting. They usually live in three or four places. If you have a big sales push coming up, like Black Friday on Friday, November 27, now is the time to check, not the morning of the sale.

Why is my website so slow?

On most business sites, slowness is not one bug. It is layers that piled up over the years. These are the causes we run into most often when auditing a site:

  • Oversized images: photos uploaded straight from a camera or a designer's export, never resized or compressed.
  • Third-party scripts: chat widgets, ad pixels, heatmaps, review widgets and tags nobody remembers adding.
  • Heavy themes and page builders: they ship code for features the page never uses.
  • Too many plugins or apps: each one adds requests, stylesheets and database queries.
  • A slow or poorly configured server: no caching, no compression, or a shared plan that chokes under traffic.
  • Web fonts and video downloading before the visitor sees anything useful.

How to check your website speed the right way

Measure before you change anything. Google's free PageSpeed Insights shows two kinds of results that are easy to mix up. Field data comes from real Chrome users; lab data is a one-off simulation. Field data tells you what customers actually experience. Lab data helps you diagnose why.

Low-traffic sites may not have field data yet. In that case, work from lab results, but always test the mobile version, because that is where problems usually hide. To see the whole site instead of one URL at a time, open the Core Web Vitals report in Google Search Console, which groups pages that share the same issue.

The three metrics that matter: Core Web Vitals

Google sums up page experience in three metrics, documented on web.dev, where it also publishes the thresholds it considers "good." Here is what each one measures and where it usually breaks:

MetricWhat it measuresUsual cause when it failsFirst fix to try
LCP (Largest Contentful Paint)How long until the main content appearsHeavy hero image, slow server, render-blocking CSSCompress and preload the hero image; turn on caching
INP (Interaction to Next Paint)How quickly the page responds to clicks and tapsToo much JavaScript, third-party scriptsRemove or delay non-essential scripts
CLS (Cumulative Layout Shift)How much the layout moves while loadingImages and banners without set dimensions, swapping fontsReserve fixed space for images, ads and notices

How to improve website speed in 9 steps

Order matters. Start with what weighs the most and carries the least risk, and re-test after each step so you know what actually helped.

  1. Pick the pages that make money. Do not optimize everything at once. Start with the homepage, top category and product pages, the cart, checkout and your lead form.
  2. Optimize images. Resize to the size they are actually displayed, compress, and use modern formats such as WebP or AVIF. On almost any site, this is the best return for the effort.
  3. Lazy-load what is below the fold. Images and videos further down the page can load as the visitor scrolls. One important exception: never lazy-load the hero image at the top, because it hurts LCP.
  4. Audit third-party scripts. List every tag, who asked for it, and whether anyone still uses it. Remove the dead weight and load the rest after the main content.
  5. Turn on caching and compression. Page caching on the server, browser caching for static files and text compression. With many hosts this is a setting, not a development project.
  6. Use a CDN. A content delivery network serves your files from a location close to each visitor. It helps most if you sell across regions or countries, say the US and Latin America.
  7. Cut unused plugins, apps and code. Uninstall what adds nothing, and check whether your theme or page builder loads styles and scripts on pages that do not need them.
  8. Tame fonts and keep the layout stable. Limit font families and weights, and set width and height on images, banners and cookie notices so nothing jumps.
  9. Look at the server and database. If the server is slow to respond even with caching on, the problem is the hosting, slow queries or the architecture. Plugins will not fix that.

Optimizing images: the highest-return fix

If you only have one afternoon, spend it on images. Online stores often grow their catalog for years with photos from different suppliers, each a different size. An automatic step that resizes and converts images on upload keeps the problem from coming back.

Three practical rules: serve different sizes for different screens (the srcset attribute), never use a huge file to show a thumbnail, and skip the five-slide homepage carousel, since most visitors only ever see the first slide.

Plugin, hosting or rebuild? When the foundation is the problem

At some point, tuning stops paying off. If you have worked through the steps above and the site is still slow, the limit is usually the platform or how the site was built. This comparison helps you decide what to do next:

SituationWhat usually worksTrade-off
Simple site with heavy images and many pluginsCleanup, image optimization and cachingQuick to do, but takes discipline to keep it lean
Growing traffic on shared hostingMove to dedicated resources plus a CDNHigher monthly cost; the move needs planning
Theme or page builder generating bloated codeRebuild on a lightweight theme or custom front endUpfront investment, full control over performance
Store or portal with complex logic and integrationsReview architecture, queries and background jobsNeeds a technical team that understands the business

If you are in the last two rows, talk to a team that does website design and development with performance built in from day one. And if the slowdown comes from syncing with your ERP, inventory or invoicing, the answer is often custom software that moves that work out of the page your customers load.

Common mistakes when speeding up a website

  • Chasing a perfect PageSpeed score. The lab score is a guide, not the goal. What counts is your real users' field data getting better.
  • Testing only on desktop over office Wi-Fi. Your customers are on phones, often on cellular data.
  • Stacking three optimization plugins. They conflict with each other and can break the cart or forms.
  • Deferring all JavaScript without testing. You can end up with dead buy buttons, payments or chat.
  • Making changes in production the day before a sale. Leave time, and test the full purchase flow.

Website speed checklist before a high-traffic sale

  • Tested the homepage, category, product, cart and checkout pages on mobile.
  • New banners and product images are compressed and have set dimensions.
  • Removed or delayed third-party tags the campaign does not need.
  • Caching and CDN are on, and the cart is confirmed not to be cached by mistake.
  • Ran a full test purchase after the changes.
  • Know exactly who to call if the site slows down during the sale.

Frequently asked questions

What is a good page load speed?

Google sets "good" thresholds for each Core Web Vitals metric and publishes them on web.dev. In practice, the goal is for most of your real visitors, measured on mobile, to land inside those thresholds on the pages that drive revenue.

Does website speed affect Google rankings?

Yes, as one signal among many. Google Search Central says its ranking systems take Core Web Vitals into account, though relevant content still matters more. A fast site also sells better, because fewer people leave before they see the offer.

Why does PageSpeed Insights give me a different score every time?

Lab data is generated on the spot and shifts with network conditions, server load and whichever scripts loaded during that run. Run several tests and lean on field data, which is far more stable.

How much does it cost to speed up a website?

It depends on where the bottleneck is. Image and caching work is a contained job; switching platforms or rebuilding is a project. Start with a diagnosis, and if you want us to look at your site, get in touch.

Comments

No comments yet. Be the first to share what you think.

Leave a comment

It is never published.