A visitor does not experience a load time, they experience a sequence: nothing, then something, then something usable. A page that shows readable content in half a second and finishes in three feels faster than one that shows nothing for two seconds and finishes in two and a half, even though the second is technically quicker.

The three moments that matter

Loading is not one event. From the visitor's side there are three, and they are noticed in order.

Something appears

The first moment anything is drawn. Until then the visitor is looking at a blank screen with no evidence that anything is happening, and blank screens feel far longer than they are. This is where most impatience is generated.

The main thing appears

Usually the headline and the large image at the top. This is the moment the page reads as arrived, and it is the one that most closely matches what a person would call the load time.

It responds

The page looks ready and taps do nothing, because the device is still processing. This is the most annoying of the three because it breaks a promise the page has already made by appearing.

Optimising the total and ignoring the sequence produces a page that scores well and feels slow, which is a common and frustrating outcome.

Why a slower page can feel faster

Because perception is about progress rather than duration.

A page that renders text immediately and fills in images afterwards gives the visitor something to read while the rest arrives. They start engaging at half a second. A page that waits until everything is ready before showing anything leaves them looking at nothing for two seconds, then presents a complete page. The second may finish sooner and it feels worse, because two seconds of nothing is longer than three seconds of something.

This is why the order things load in matters as much as how much there is to load.

What actually makes it slow

For a small business site the causes are consistent and there are not many of them.

What the visitor is comparing against

Not a benchmark. The other two tabs they have open.

Someone choosing a contractor opens three sites from a results page. All three are loading at once. The one that shows something first gets read, and the other two get closed before they finish. That comparison is happening constantly and it is invisible from your side.

It is also why testing your own site in isolation, on a good connection, tells you very little. Your browser already holds a copy of everything, so you are measuring a repeat visit while your customer is having a first one.

The test that reflects reality

Open your site in a private browsing window, on an actual phone, with wifi turned off so it uses mobile data.

That single test removes the two advantages you have over your visitors, which are a cached copy and a strong connection. It takes a minute, it requires nothing to be installed, and it is regularly the moment a business discovers the site it is proud of is not the site people are seeing.

Do it somewhere with a weak signal too, such as a basement or a parkade, because that is where a good share of urgent enquiries originate.

What is worth fixing first

What it is worth

Speed is not a vanity number. A visitor who leaves before the page appears is indistinguishable in your analytics from someone who never arrived, which means the cost is invisible and continuous.

For a business where the phone rings because of the website, this is one of the few improvements that is a one-time cost applying permanently to every visitor afterwards. It is also, unusually, work whose benefit does not decay, provided nobody adds another widget without checking what it costs.


Frequently asked questions

What actually makes a website feel fast?

The order things happen in. Showing readable content quickly matters more than finishing quickly, because a blank screen feels far longer than a partly loaded page.

Why does my site feel slow when the score is good?

Scores are composites and can improve without the experience changing. A page can finish quickly while showing nothing for the first two seconds, which is what the visitor notices.

What is usually the cause of a slow small business site?

Images, in most cases, typically eighty percent or more of the weight and sized far larger than they are displayed. After that, too many separate requests, third-party scripts, and fonts.

How should I test my own site speed?

In a private browsing window on an actual phone with wifi turned off. That removes your cached copy and your strong connection, which are the two advantages you have over your visitors.

Does speed really affect enquiries?

Someone who leaves before the page appears looks identical in analytics to someone who never arrived, so the cost is invisible and continuous. People comparing three sites read whichever shows something first.

What should I fix first?

Resize and compress the images, then remove third-party scripts nobody is using. Both are straightforward, neither changes how the site looks, and together they resolve most of the problem on most sites.

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.

Site feeling sluggish on a phone?

We test on real devices over real mobile connections and fix what that reveals, starting with the images.

Start a Conversation