Perception is governed by when readable content appears, whether the layout stays still, and whether taps respond immediately. A site can be measurably slower than a competitor and feel faster if it handles those three well.

The distinction that matters

Measured speed is how long everything takes. Perceived speed is how long it feels, and the two can differ substantially.

A page showing readable content in one second and finishing at four feels fast. A page showing nothing until three and a half seconds then appearing complete feels slow, despite finishing sooner.

The visitor is not timing anything. They are waiting for a signal that something is happening, and the absence of that signal is what feels like slowness.

Show something immediately

The single largest lever.

Whatever appears first should be useful: a heading, the first paragraph, the phone number. A page whose text arrives before its images is doing this correctly, even though it looks unfinished for a moment.

The common mistake is the reverse, where a page holds everything back until a large hero image or a web font has loaded, producing a blank screen while the content sits ready.

Text should never wait for an image, and it should not wait indefinitely for a font either, which is a setting rather than a rebuild.

Stop the layout moving

The failure that produces the most frustration per second of delay.

Content appears, the visitor starts reading or reaches to tap, an image finishes loading above it, and everything jumps down. They tap the wrong thing.

The cause is almost always an element with no reserved space: images without dimensions, embedded content, advertisements, and banners that insert themselves after the page has rendered.

Reserving the space in advance means the layout is correct from the first paint and nothing moves. This is one of the highest-return fixes available and it changes no content at all.

Load what is visible first

Anything below the fold can wait.

Deferring images further down the page until they are approached means the visible portion arrives sooner. On an image-heavy page that is the difference between a fast first impression and a slow one.

The caution is not to defer the image at the top, which is the one thing that should load immediately. Applying lazy loading indiscriminately, including to the hero image, makes the first impression worse rather than better.

Respond to taps instantly

The interaction side of perception, and it is separate from loading.

When somebody taps a button, something should change within a moment: a colour shift, a spinner, a disabled state. Without it they assume the tap missed and tap again, which on a form produces duplicate submissions.

The response does not have to mean the work is finished. It has to acknowledge that the tap registered, which is what the visitor is actually waiting for.

The same applies to navigation. A menu that opens instantly feels fast even on a slow site, and one that hesitates feels broken.

Placeholders and progress

Worth using judiciously rather than everywhere.

A grey block in the shape of the content that is coming reads better than empty space, because it signals that something is arriving and where it will be. That works well for lists and galleries.

What works less well is a spinner in the middle of an empty page, which communicates waiting without communicating progress. A visitor watching a spinner has nothing to read.

Where content is genuinely slow to arrive, showing part of it is better than showing none, since something to read makes the remaining wait shorter subjectively.

Anticipating the next page

A technique worth knowing and using sparingly.

Browsers can begin fetching a page before it is requested, which makes a click feel instant. Applied to the one or two pages most visitors go to next, such as the contact page from a service page, it is genuinely effective.

Applied broadly it downloads pages nobody visits, consuming the visitor's data and your bandwidth to make a small number of navigations faster.

How to judge it

Not by the overall score, which averages things a visitor experiences separately.

Watch the page load on a phone on mobile data with the cache cleared, and note two moments: when you could read something, and when you could tap the phone number without the layout moving.

Those two moments are what the visitor experiences as speed. A site that gets both under a couple of seconds feels fast regardless of what happens afterwards, and the underlying causes of actual slowness are covered in what slowness actually costs you.

Frequently asked questions

What is the difference between measured and perceived speed?

Measured speed is how long everything takes; perceived speed is when something useful appears. A page readable at one second and finished at four feels faster than one blank until three.

What is the single largest lever?

Showing readable content immediately. Text should never wait for an image, and it should not wait indefinitely for a web font either.

Why does layout shift matter so much?

A visitor reaches to tap, an image loads above, and the page jumps. They tap the wrong thing, which is more frustrating than the delay itself.

How is layout shift fixed?

By reserving space in advance for images, embeds, advertisements, and banners. It changes no content and is one of the highest-return fixes available.

What about lazy loading?

Defer images below the fold, but never the hero image at the top. Applying it indiscriminately makes the first impression worse rather than better.

Why acknowledge taps immediately?

Without a visible response people assume the tap missed and tap again, which on a form produces duplicate submissions. The response need not mean the work is finished.

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 that measures acceptably and still feels slow?

We fix the two moments visitors actually notice: when text appears and whether the page moves under their thumb.

Start a Conversation