News
Articles on branding, websites and marketing.
Here's the short answer: the main content of your page should be visible within roughly one to two and a half seconds on an ordinary mobile connection. Under a second feels instant. Around two to three seconds is fine. Most visitors won't notice or care. Beyond that, patience drains fast, and somewhere past the five-second mark you're losing a meaningful chunk of visitors before they've seen a single word you wrote.
Those are honest ranges, not laboratory precision: connection, device and expectation all vary. But the pattern holds everywhere we look: people don't consciously time your website. They just feel it. A fast site feels professional before it says anything. A slow one feels broken, and visitors quietly assume the business behind it might be too.
What do users actually tolerate?
Think about your own behaviour. When a page hangs, you don't note the elapsed seconds. You flick back to the search results and tap the next one. Your customers do exactly the same, and on a phone (where most local searching now happens) they do it faster.
Google's own Core Web Vitals framework (the measurements it uses to judge page experience) points the same way. Its "good" threshold for the largest piece of content appearing is 2.5 seconds. Not because 2.6 seconds is a disaster, but because that's roughly where real users stop feeling that a page is responsive. The goal isn't a perfect score. It's staying below the threshold where people start leaving.
Test your own site free in 60 seconds
Don't take anyone's word for it, including ours. Here's the whole test:
- Go to PageSpeed Insights (pagespeed.web.dev), Google's own free tool.
- Paste in your homepage address and run it.
- Look at the mobile result first. That's how most of your customers see you, and it's almost always the worse of the two.
- Check two things: whether you pass the Core Web Vitals assessment (data from real visitors, where available), and the diagnostic suggestions underneath, which usually name the culprits for you.
Run your most important service page too, not just the homepage. Then, if you're feeling brave, run your biggest competitor. This is either reassuring or motivating, and both are useful.
Why is your website slow? The real culprits, ranked
Nearly every slow small business site we're asked to look at suffers from some mix of the same four problems. In rough order of how often we see them cause real damage:
1. Slow server response
Before your page can even begin loading, the server has to answer. On cheap, overcrowded shared hosting, or a CMS grinding through dozens of database queries to assemble each page, that first response alone can eat a second or more. No amount of front-end tinkering can claw that back. If the server is slow, everything is slow.
2. Oversized images and video
The most common self-inflicted wound. A photo comes off a phone at 4,000 pixels wide and several megabytes, gets uploaded straight into the site, and is then displayed 400 pixels wide. Multiply by a homepage full of them, plus an autoplaying background video, and you're asking mobile visitors to download the equivalent of a small album before they can read your headline.
3. Uncompressed, bloated pages
Every page is made of code, and that code should travel compressed and trimmed. Many sites ship uncompressed files, unminified code and generous helpings of markup their page builder generated and nobody ever looks at. Each individual sin is small. Together they double or triple what every visitor has to download.
4. Plugin and script bloat
Chat widgets, pop-up tools, three analytics packages, a fonts service, a slider plugin from 2019. Each one adds requests and script that the browser must fetch and execute, often before the page becomes usable. Sites accumulate these the way kitchen drawers accumulate mystery keys, and nobody ever audits them. This is a big part of why we build client sites on our own CMS: no plugin ecosystem, no third-party bloat we didn't choose, and pages that only carry what they need.
What's fixable in an afternoon vs what needs a rebuild
The good news: some of the biggest wins are also the easiest.
Fixable in an afternoon
- Compress and resize your images. Free tools (Squoosh, TinyPNG) shrink most photos by 70-90% with no visible difference. Often the single biggest win available.
- Cull the plugins and scripts. Deactivate anything you can't justify. If you don't know what it does, that's your answer.
- Turn on compression and caching. Usually a hosting setting or a well-configured caching layer. Ten minutes, real gains.
- Remove autoplaying video from the top of the page, or make it load only when needed.
Probably needs professional help, or a rebuild
- A slow server that stays slow after caching. Moving to decent hosting helps; sometimes the platform itself is the anchor.
- A theme or page builder generating bloated code on every page. You can't trim what the tool keeps regenerating.
- A site that fails Core Web Vitals across the board despite the afternoon fixes. At that point you're paying to patch something that wants replacing, and a rebuild usually fixes the dated design and clunky admin at the same time.
And once a site is fast, it needs to stay that way. Speed decays: new images get uploaded uncompressed, another widget sneaks in, software drifts out of date. It's exactly the kind of thing we watch on our care plans, because a site that was fast at launch and slow within a year is depressingly normal.
Common questions
Does website speed affect my Google rankings?
Yes, though it is one factor among many. Google uses its Core Web Vitals measurements as a ranking signal, and slow sites also suffer indirectly: visitors leave faster, engage less and convert less, all of which feeds back into how your site performs in search. Speed will not rescue thin content, but slowness will quietly tax everything else you do.
What is a good PageSpeed Insights score?
Treat the field data (the Core Web Vitals assessment) as the real verdict and the 0-100 lab score as a diagnostic. Passing the Core Web Vitals assessment matters more than chasing a perfect 100. As a rough guide, a mobile lab score in the 80s or 90s with passing field data means you are in good shape; below 50 usually means something structural is wrong.
Will a caching plugin fix my slow WordPress site?
It often helps, and it is a reasonable first step. But caching hides slowness rather than removing it, and it cannot fix oversized images, a cheap overloaded server or a theme dragging in a dozen scripts. If your site is only fast when the cache is warm, the underlying problem is still there.
How much does page speed actually matter for a small local business?
More than most owners assume, because the effect is invisible. Nobody rings you to say your site was slow so they called someone else. They just do it. On mobile connections, where most local searches happen, a slow site loses people before it has said a word. Speed is the cheapest credibility you can buy.
Is it worth rebuilding a site just for speed?
Rarely for speed alone. But slow sites are usually old sites, and the same rebuild that fixes performance typically fixes dated design, poor mobile layouts and creaky content management at the same time. If your site is more than four or five years old and testing badly, a rebuild is usually better value than paying someone to keep patching it.
Want a site that's fast and stays fast?
We're Bare Creative, a husband-and-wife studio in Somerset. We build sites on our own lean CMS, so speed is designed in rather than bolted on, and we stay around after launch to keep it that way. Run your site through PageSpeed Insights, and if the results make you wince, send them our way. We'll tell you honestly what's an afternoon's work and what isn't.