Almost every conversation about a new website starts with how it looks. Understandable: that's the part you can see. But the first thing a visitor experiences isn't your design — it's the wait. Anyone tapping a link while queuing at a checkout, or in a car with poor reception, sees a blank screen first. What happens next decides whether the design gets a chance at all.
A beautiful site that's slow is an expensive site
Design and speed are often framed as a trade-off: you can make an impression, or you can load fast. In practice it works the other way around. A site that opens slowly never shows its design to the people quickest to click away — and those are exactly the visitors you didn't have yet.
Every second of waiting costs you visitors who had already arrived. They clicked your ad, they found you in Google, they were on your doorstep. That's the most expensive traffic you have. Handing it over to a loading bar wastes the effort that got them there.
What happens in the first few seconds
Visitors decide remarkably fast whether a site feels trustworthy. That judgement doesn't start with your colours or your typography, but with a simple question: is anything happening? A white screen for three seconds feels longer than it is, certainly on a phone away from wifi.
An important detail: it isn't only about total load time, but about when the screen becomes usable. A page where the text is there but the buttons don't respond yet, or where content jumps the moment an image loads, feels broken — even if the meter says everything finished within two seconds.
Google measures speed — and counts it
Google publishes three metrics under the name Core Web Vitals, with public thresholds for what counts as 'good'. They measure precisely the things a visitor feels:
- LCP (Largest Contentful Paint): how quickly the largest element appears — good is 2.5 seconds or less
- INP (Interaction to Next Paint): how quickly the page responds when you click or tap — good is 200 milliseconds or less
- CLS (Cumulative Layout Shift): how much content jumps around while loading — good is 0.1 or lower
- You can measure them yourself with PageSpeed Insights or the Lighthouse tab in Chrome — free, no account needed
Where the delay usually comes from
It's almost never one big problem. It's a stack of small things that clog the pipe together. In the sites we take over, we keep meeting the same suspects:
- Photos straight from the camera or the photographer — megabytes where kilobytes would do
- A carousel or video header that has to load fully before the visitor sees anything
- Tracking scripts and chat widgets you added once and never removed
- Seven different typefaces and weights, three of which you actually use
- Plugins that each drag along their own slice of code, even on pages where they do nothing
- Cheap shared hosting with a hundred other sites on the same server
Speed and beauty aren't opposites
This is where the thinking goes wrong. A fast site isn't a bare site. It's a site where every choice has a reason: this image carries weight, so it's allowed to be heavy — and that animation adds nothing, so it goes. That is exactly what good design is.
In practice that discipline makes the design better, not poorer. Less distraction, more calm, a clearer path to what you want people to do. That's why we build statically wherever we can: pages that are already finished before the visitor asks for them, with motion that only starts once it's genuinely in view.
How to tackle it without rebuilding everything
You don't need to start a new site to make a difference. This order delivers results fastest:
Speed is one of the few improvements that works in several places at once: more visitors who stay, a better experience for the ones already there, and a signal Google weighs in how you get found.
Want to know where your site stands? Our free website audit looks at speed, findability and usability — and hands you a concrete list of what's worth fixing first. No obligations, and no need to commit to a new site.
- Measure first. Run PageSpeed Insights on your three most important pages, mobile and desktop.
- Fix the images. Compressing them and sizing them correctly is often the biggest win for the least effort.
- Clear out. Every script, plugin and typeface you can't justify can go.
- Look at your hosting. If the server takes hundreds of milliseconds before anything leaves at all, front-end optimisation only gets you halfway.
- Measure again, and record the result. Next time you change something, you'll see immediately whether you moved forward or back.