Customer Impact

Website & Development

Improve website speed: a practical page load checklist

Copy for AI

To improve website speed, measure first, then fix the heaviest items before the fine-tuning.

The heavy items are your server, your images, your scripts and your third-party tools. Fonts and caching come after that.

The verdict: random tinkering rarely wins anything lasting. Work the checklist below from top to bottom and load time usually drops considerably.

Want to know how to read the scores? That’s in Core Web Vitals.

This article is about the work underneath: what you change to make your website faster.

Here’s the order of work in one picture:

ORDER OF WORK Work from heavy to light 1 Measure baseline 2 Server hosting & caching 3 Images compression 4 Fonts self-hosted 5 Scripts clean up 6 External third-party Measure first, tackle the heaviest items and finish with the fine-tuning.

Why does speed matter for a B2B website?

Because speed is a revenue factor, not a technical bonus.

Every extra second of load time costs you visitors who leave before they see your offer. In B2B, that means lost leads.

A slow site also undermines trust. If the first impression stutters, a prospect starts doubting the rest.

Google counts it too

Speed plays a part in how Google assesses your pages.

But the real argument is simpler: a visitor who quickly finds what they need stays longer and converts more often.

Our piece on page speed, SEO and conversion goes deeper into that link.

So speed is a lever for a website that generates leads, not a goal in itself.

How do you measure your load time before you start?

With three free tools, before you touch anything.

Without a baseline, you won’t know afterwards whether you fixed anything. Measure first, then tinker.

The three tools

Each one shows a different side of speed:

  • PageSpeed Insights: your scores plus concrete bottlenecks, heaviest first
  • Lighthouse: built into Chrome’s developer tools, handy for repeated tests
  • Google Search Console: how your whole site performs with real visitors

More on the Chrome tool in Google Lighthouse explained.

What “good” means in numbers

Search Console’s Core Web Vitals report uses Chrome UX Report field data.

It rates a page as good at these thresholds:

  • LCP: 2.5 seconds or less
  • INP: 200 ms or less
  • CLS: 0.1 or less

Our explainer on what INP is covers that responsiveness metric.

Here’s what field data looks like for our own site in PageSpeed Insights:

PageSpeed Insights field data for customerimpact.be on mobile: LCP 1.9 s good, CLS 0.13 needs improvement, the baseline you note before you improve website speed PageSpeed Insights field data for customerimpact.be on mobile, October 2026. LCP passes at 1.9 s; CLS at 0.13 still needs work.

So even a fast site can miss one threshold.

Ours loads fine but still shifts too much.

Test on mobile and write it down

Always test on mobile. That’s where the experience is toughest and traffic is often largest.

Note your starting values, so you can measure every change against the baseline.

Read the report as a to-do list

PageSpeed Insights and Lighthouse name their findings. Each one points to a section below:

What the report saysWhere to start
Reduce initial server response timeServer and hosting
Properly size images, serve images in next-gen formatsImages and assets
Ensure text remains visible during webfont loadFonts
Reduce unused JavaScript, eliminate render-blocking resourcesScripts and code
Reduce the impact of third-party codeThird-party tools

For example, say the report flags oversized images and unused JavaScript. Then you skip the hosting debate and start with those two.

The heaviest finding goes first.

How do you speed up your server and hosting?

Start here if your hosting lags, because tricks on top can’t fix a slow foundation.

Your server decides how fast the first byte reaches the visitor. Our guide to improving TTFB covers that first byte in detail.

The server checklist

Go through these four points:

  • Hosting that matches your traffic: cheap shared hosting gets slow at peaks
  • A CDN: copies of your site on servers close to your visitors
  • Server-side compression: Brotli or Gzip sends files in compact form
  • Caching: browsers store static files, so returning visitors skip the download

Why each point matters

Hosting: shared hosting splits capacity with many other sites. For a B2B site that must bring in leads, reliable speed beats saving a few euros a month.

Our guide to choosing web hosting compares the options.

CDN: a content delivery network mainly helps if your audience is spread out geographically.

Compression: modern browsers widely support both Brotli and Gzip. You can often switch them on with one setting.

Caching: set it once and every returning visitor benefits.

Watch out: with long cache times, give changed files a new name or version. Otherwise visitors keep seeing the old CSS after a redesign.

How CDN and caching work together is in CDN and caching.

Whichever platform you use

This layer is usually the first place where serious gains sit.

For example, say every page shows a slow server response in the report, even plain text pages. Then images aren’t your first problem; the server is.

Running WordPress? Our checklist to speed up a WordPress site has the platform-specific steps.

Want it set up properly on a new or rebuilt site? See how we handle professional website development.

How do you optimise images and assets?

Compress, convert and resize them, because images are usually the heaviest item.

A homepage full of uncompressed photos loads slowly, however good your server is. So this is often where the fastest gain sits.

The image checklist

Work through these five steps:

  1. Compress every image before upload. Many sites show visuals far larger than needed.
  2. Use modern formats such as WebP or AVIF, with a JPEG or PNG fallback.
  3. Scale to the right dimensions. Don’t put a 3000 pixel photo in a 600 pixel slot.
  4. Set up responsive images, so mobile visitors get a lighter version.
  5. Lazy load images below the fold with loading="lazy".

WebP and AVIF deliver comparable quality at a smaller file size and are widely supported by now. Keep the classic fallback for the last few percent of visitors.

For example, say your team page shows eight portraits straight from a camera. Resizing and compressing them often beats any server upgrade.

Our guide to optimising images for your website covers formats and tools.

Watch out with lazy loading

Lazy loading means the browser only fetches an image when the visitor is nearly there.

web.dev’s lazy-loading guide notes it works in all major browsers. But it warns: never lazy-load images that are in view on load, especially your LCP image.

That’s usually the hero. But not always, as our own article page shows:

PageSpeed Insights LCP breakdown for our largest contentful paint article: the LCP element is the H1 heading, time to first byte 0 ms, element render delay 2,370 ms PageSpeed Insights for our own largest contentful paint article, October 2026. The H1 in the first screen is the LCP element.

Here the largest element is a heading, not an image. So check which element it is before you change anything.

Give images fixed dimensions

Set width and height on every image, so the page doesn’t jump while loading.

That keeps your layout stable and your visitor calm. Layout shift is exactly what keeps our own mobile pages out of the green:

Google Search Console Core Web Vitals report for customerimpact.be on mobile: 349 URLs need improvement because of a CLS issue above 0.1, layout shift to fix when you improve website speed Our own Search Console, Core Web Vitals on mobile, October 2026. Layout shift, not load speed, keeps 349 mobile URLs out of the green.

How to find and fix those shifts is in our guide to cumulative layout shift.

How do you reduce the impact of fonts?

Load fewer, lighter fonts, and never hide text while they load.

Typefaces look small, but they can keep your text invisible until the font arrives. A few targeted changes remove that brake.

The font checklist

Four changes cover most sites:

  • Fewer fonts and weights: every extra weight is a separate file
  • Self-hosted fonts: saves a connection to another domain
  • WOFF2 files: more compact than older formats
  • font-display: swap: text shows straight away in a fallback font

Two fonts and a handful of weights are usually more than enough.

For example, a site that loads one family in six weights fetches six font files. Most pages only use two of them.

How swap works

Per MDN, font-display: swap gives the font “an extremely small block period and an infinite swap period”.

In plain terms: the browser shows a fallback typeface almost at once. It switches to your own font as soon as it’s ready, instead of hiding the text.

So your text stays readable, even while the font is still loading.

How do you keep scripts and code light?

Ship less JavaScript and CSS, and load the rest later.

Heavy code makes the browser work before the visitor can do anything. That feels slow, even when the page already looks ready.

The code checklist

Four habits keep the weight down:

  • Remove unused code: old plugins, unused libraries, leftovers from earlier projects
  • Minify your files: strip spaces and comments without changing behaviour
  • Defer what can wait: load non-critical scripts with defer or async
  • Bundle sensibly: too many files means too many requests

On bundling, find the balance. Bundles that are too large load slowly too.

A headless or modern setup helps limit the ballast. On WordPress, plugins are the usual suspect; see too many WordPress plugins.

Why this needs a developer

A lot of this work happens under the bonnet. It calls for a developer who knows what to leave out.

It pays off.

Heavy scripts are often the silent reason a simple page still feels slow.

How do you limit the damage from third-party tools?

Count what’s running, then cut every tool that doesn’t earn its weight.

External scripts are the most underestimated brake on a B2B site. Every tracker, chat widget or embed loads code from a domain you don’t control.

They creep in one tool at a time.

For example, a chat widget from a trade show campaign, or a heatmap tool nobody has opened in a year.

The third-party checklist

Four moves keep them in check:

  1. Take stock of what really runs: analytics, ad pixels, chatbots, videos, A/B testing tools.
  2. Cut what nobody uses: many sites still drag along tracking from campaigns that ended long ago.
  3. Load heavy embeds on interaction: show an image with a play button instead of a full video player.
  4. Question every new tool: each marketing tool costs a bit of speed.

Quick check: the free cookie scanner lists the tags and cookies that load on your page, a fast way to start that inventory.

Weigh the trade-off honestly

This is where honest trade-offs count most.

A tool that produces no demonstrable leads but slows your site costs you customers, on balance.

The short summary

Improving website speed isn’t a miracle cure. It’s a checklist you work through in the right order.

Measure first with PageSpeed Insights or Lighthouse. Then tackle the heavy items:

  • a solid server with compression and caching
  • compressed images in modern formats
  • light fonts and cleaned-up scripts
  • only the third-party tools worth their weight

Work from heavy to light, and measure every change against your baseline. Our guide to improving Core Web Vitals helps with that last step.

Speed serves leads

The goal stays the same as with everything we build: a site that holds visitors until they get in touch.

Speed is a lever for leads, not a badge for the technician. How it fits a site that carries your growth is in our guide to B2B website development.

Is your site still slow after this list? We map out what’s slowing it down and fix it at the root.

Contact us

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.