Before a browser can render anything it has to wait for the server's first response. That delay sits in front of everything else, so a slow server makes every subsequent optimisation less effective. It is also the one part of page speed that a site owner cannot fix by editing the site.

The delay that comes first

A request arrives, the server does whatever work is needed, and then starts sending. Everything else, images, scripts, fonts, and rendering, happens after that.

The measurement is time to first byte, and on a well-configured server it is a small fraction of a second. On a poor one it can be a second or more before the browser has anything at all to work with.

That matters disproportionately because it delays the start rather than the end. Compressing images improves the middle of the load; a slow server delays the entire sequence, including the moment anything first appears.

What the server is actually doing in that time

Nothing, for a static file

A plain HTML page is read from disk and sent. This is why hand-built static sites are fast almost regardless of hosting: there is no work to be slow at.

Building the page, for a content system

Running code, querying a database several times, assembling the output, then sending it. Every plugin adds to that work, and it happens on every request unless something is caching the result.

This is where most server-side slowness on small business sites comes from.

Waiting on something else

Where the page calls an external service while building, the server waits for that service. A slow third party then makes your page slow, and the delay appears to be yours.

What makes hosting slow

Caching, which is the largest single fix

Building the same page from scratch for every visitor is wasted work when the page has not changed.

Caching stores the assembled result and serves that instead, which turns a page build into reading a file. On a content-managed site this frequently reduces server response time by most of it, and it is usually available either in the hosting panel or as a plugin.

The trade is that changes may not appear immediately, which is the source of the familiar experience where an edit is invisible until the cache is cleared. Understanding that is the price of the speed.

The language version, which is free

Newer versions of the language most content systems run on have been meaningfully faster than older ones, and hosts generally let you switch in the control panel.

Sites left on a version from several years ago are paying a speed penalty for nothing. The caveat is that a very old site may depend on something removed in a newer version, which is why the change belongs on a staging copy first.

It is also a security matter, since unsupported versions stop receiving fixes, which makes this worth checking regardless of speed.

How to tell whether hosting is your problem

Run a speed test and look at the server response time specifically rather than the overall score.

If that figure is small and the page is still slow, the problem is in the page: images, scripts, fonts. Optimising hosting will change little.

If that figure is large, everything else is being delayed behind it, and page-level work will have limited effect until it improves. That is the case where a hosting change or a caching layer is the actual fix.

Testing at different times of day is worth doing, since shared hosting problems appear under load and disappear when you happen to check at eight in the morning.

When to move rather than optimise

Caching, a newer language version, and removing unused plugins recover most of what is recoverable on a given plan.

Where response times remain poor after those, or where slowness correlates with your busy periods, the account has outgrown the plan and the answer is more resources rather than more tuning.

That is a straightforward decision once the numbers are known, which is why measuring the server response separately matters before spending anything, and it follows the same diagnostic order as testing your site speed for the first time.

The honest summary

For most small business sites, images are the larger problem and hosting is the one that limits how much fixing images can achieve.

Do the image work first, because it is free and it always helps. Then measure the server response, because that is what determines whether the remaining slowness is something you can fix by editing the site at all.

Frequently asked questions

How does hosting affect page speed?

The server's first response happens before anything else, so a slow server delays the entire sequence including the moment anything appears. It is the one part a site owner cannot fix by editing the site.

What is time to first byte?

How long the server takes to start responding to a request. On a well-configured server it is a small fraction of a second; on a poor one it can exceed a second before the browser has anything.

Why are static sites faster?

There is no work to be slow at. A plain HTML page is read from disk and sent, while a content system runs code and queries a database on every request unless something is caching the result.

What is the biggest server-side improvement?

Caching. Storing the assembled page and serving that instead of rebuilding it for every visitor frequently removes most of the server response time on a content-managed site.

Does the language version matter?

Yes. Newer versions have been meaningfully faster, and sites left on an old one pay that penalty for nothing. It is also a security matter, since unsupported versions stop receiving fixes.

How do I know if hosting is my problem?

Run a speed test and look at the server response time specifically. If it is small and the page is still slow, the problem is images and scripts rather than the server.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Optimised the images and the site is still slow?

We measure the server response separately, so you know whether the remaining problem is something you can fix by editing the site at all.

Start a Conversation