Improve website speed: a practical page load checklist

The best way to improve website speed is to follow a fixed order: measure your load time first, then tackle the heaviest items (your server, your images, your scripts and your third-party tools) and only after that check the fine-tuning such as fonts and caching. Anyone who starts tinkering at random rarely wins anything lasting. Anyone who works the checklist below from top to bottom usually sees load time drop considerably. In this article you get that full checklist, split up per component, separate from the measurement figures themselves.

Want to know how to interpret those figures? You can read that in Core Web Vitals. This article is about the work underneath: what you change concretely to load faster.

Why does speed matter for a B2B website?

A fast site is not a technical bonus but a revenue factor. Every extra second of load time costs you visitors who drop off before they see your offer, and in B2B that means lost leads. A slow site also undermines trust: if the first impression stutters, a prospect starts doubting the rest.

Speed also counts in how Google assesses your pages. But the real argument is simpler: a visitor who quickly finds what they are looking for stays longer and converts more often. Speed is therefore a lever for a website that generates leads, not a goal in itself.

How do you measure your load time before you start?

Never start optimising without a baseline, otherwise you will not know afterwards whether you actually fixed anything. Measure first, then tinker.

Three free tools are enough:

• PageSpeed Insights. Paste in your URL and you get your scores plus a list of concrete bottlenecks, with the heaviest items at the top.
• Lighthouse. Built into Chrome (a tab under the developer tools) and handy for testing repeatedly while you work. More on this in Google Lighthouse explained.
• Google Search Console. Shows how your whole site performs with real visitors, not only in a lab test.

Always test on mobile, because that is where the experience is toughest and the traffic is often largest. Note down your starting values, so you can measure every intervention against the baseline.

How do you speed up your server and hosting?

Your server determines how fast the first byte reaches the visitor, and you cannot optimise that foundation away with tricks layered on top. If your hosting is lagging behind, that is where you start.

Go through these points:

• Choose hosting that matches your traffic. Cheap shared hosting splits capacity with many other sites and gets slow at peak moments. For a B2B site that has to bring in leads, reliable speed weighs more heavily than a few euros a month.
• Set up a CDN. A content delivery network keeps copies of your site on servers around the world, so visitors get the version closest to them. That mainly helps if your audience is spread out geographically.
• Enable server-side compression. With Brotli or Gzip your server sends files in compact form. Both are widely supported by modern browsers and can often be switched on with a single setting.
• Use caching. Let the browser store static files locally, so returning visitors do not download them all over again every time.

Whichever platform you use, this layer is usually the first place where serious gains sit. Want that set up properly on a new or rebuilt site? Then take a look at how we handle your professional website development.

How do you optimise images and assets?

On most sites images are by far the heaviest item, so this is often where the fastest gain is. A homepage full of uncompressed photos loads slowly, however good your server is.

The checklist for your visuals:

• Compress every image before you upload it. Many sites display visuals that are far larger than needed.
• Use modern formats such as WebP or AVIF. They deliver comparable quality at a smaller file size and are widely supported by now. Keep a classic JPEG or PNG as a fallback for the last few percent of visitors.
• Scale images to the right dimensions. Do not show a photo that is 3000 pixels wide in a slot of 600 pixels. Deliver the size you actually need.
• Set up responsive images so mobile visitors get a lighter version than desktop users.
• Lazy load images below the fold with the loading="lazy" attribute. The browser then only fetches them when the visitor is nearly there, instead of loading everything at once.

Also give images fixed dimensions, so the page does not jump around while loading. That keeps your layout stable and your visitor calm.

How do you reduce the impact of fonts?

Typefaces look small but can keep your text invisible until the font has loaded. A few targeted interventions remove that brake.

• Limit the number of fonts and weights. Every extra typeface and every extra weight is a separate file. Two fonts and a handful of weights are usually more than enough.
• Host your fonts yourself instead of fetching them from an external service every time. That saves a connection to another domain.
• Use modern font files such as WOFF2, which are more compact than older formats.
• Set font-display: swap. The browser then immediately shows a system typeface and switches to your own font as soon as it is ready, instead of hiding the text.

That way your text stays readable straight away, even while the font is still coming in.

How do you keep scripts and code light?

Heavy JavaScript and CSS make the browser work before the visitor can do anything, and that feels slow, even if the page is already there visually. Less code, loaded more intelligently, is the goal here.

• Remove code you do not use. Old plugins, unused libraries and leftovers from previous projects pile on needless weight. A headless or modern setup helps limit that ballast.
• Minify your files. Stripping out spaces and comments makes JavaScript and CSS smaller without changing how they work.
• Defer what is not needed straight away. Load scripts that are not needed above the fold later, with defer or async, so they do not block the page from painting.
• Bundle sensibly. Too many separate files means too many separate requests. Bundles that are too large load slowly. Find the balance.

A lot of this work happens under the bonnet and calls for a developer who knows what to leave out. It pays off, because heavy scripts are often the silent reason why a seemingly simple page still feels slow.

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

External scripts are the most underestimated brake on a B2B site, because every tracker, chat widget or embed loads code from another domain that you have no control over. They creep in unnoticed, one tool at a time.

What you can do:

• Take stock of what is really running. Analytics, ad pixels, chatbots, embedded videos, A/B testing tools: add them all up and ask yourself for each one whether it is worth its weight.
• Cut what nobody uses. Many sites still drag along tracking from campaigns that ended long ago.
• Only load heavy embeds on interaction. Show an image with a play button, for example, instead of a full video player that loads immediately.
• Hold every new tool up to the light critically. Every marketing tool that gets added costs a bit of speed. Weigh that against what it delivers.

This is the point where honest trade-offs count most: a tool that produces no demonstrable leads but does slow down your site costs you customers, on balance.

The short summary

Improving website speed is not a matter of a miracle cure but of a checklist you work through in the right order. Measure first with PageSpeed Insights or Lighthouse. Then tackle the heaviest items: a solid server with compression and caching, compressed images in modern formats, light fonts, cleaned-up scripts and only the third-party tools that are worth their weight. Work from heavy to light and measure after every intervention against your baseline.

The goal stays the same as with everything we build: not a fast site for the sake of speed, but a site that holds visitors until they get in touch. Speed is a lever for leads, not a badge for the technician. Want to know how this fits into a site that has to carry your entire growth? Then read our guide to B2B website development.

Is your site lagging behind and this list does not fix it? We map out what is slowing your site down and solve it at the root.

Plan your free intake