A good website should never make you fight the page.

You notice the delay before you know its name

You tap a button and nothing appears to happen. You try again. Then the page changes twice. Or you start reading a paragraph and a late-loading picture pushes it out of place.

You do not need a technical vocabulary to recognise the frustration. A page that reacts predictably lets you focus on why you visited. An unpredictable one asks you to manage the interface as well as your task.

Google’s web guidance includes a measure called Interaction to Next Paint, or INP, for responsiveness to interactions such as taps, clicks, and keyboard input. It is useful evidence, but it does not describe the entire experience or prove that scrolling feels good.

Source: web.dev ↗

A lesson from this portfolio

This website uses 3D scenes and animation. During its recent refinement, scrolling could feel inconsistent around particular elements. Some of the work was about deciding which effects needed to keep running and which could pause out of view.

Another change replaced an internally scrolling testimonial with an excerpt and a “Read more” control. The longer text expands in the page, so a visitor does not have to navigate a miniature scroll area inside the main one.

The aim was to preserve the character of the site while making ordinary actions easier. That is a useful design question for a small business website as well as an animated portfolio.

Try a five-minute visitor check

Pick one real reason someone would visit. For a cafe, that might be finding today’s opening hours. For a consultant, it could be understanding the service and sending an enquiry.

Open the site on your phone and attempt that task without using your knowledge of where everything lives. Better still, watch someone who has not used the site before.

• Can the visitor read the main information without zooming?
• Does scrolling continue naturally over images, cards, and videos?
• Do buttons give a clear response after one tap?
• Does the content stay in place while the page finishes loading?
• Is it obvious when the task is complete?

Describe the moment that felt wrong

“Make it faster” is difficult to act on. “After I tap Send, nothing changes for several seconds, so I am unsure whether the enquiry went through” gives a developer a concrete problem to investigate.

Include the device, browser, page, and steps when you can. A short recording can show behaviour that is hard to explain in words.

Visual polish and practical usability belong together. The most satisfying improvement is often a moment of friction the visitor no longer has to think about.