The 3-second test: how slow sites lose emergency call-outs
An emergency search is the least patient moment on the internet. We timed ten Bristol trade sites on a throttled mobile connection: the fastest was 1.2 seconds to a usable page, the slowest 7.4. Both were competing for the same 9pm call-out.
Key takeaways
- Emergency searchers commonly open three results and ring whichever loads first.
- The usual culprits are page builders, carousels, web fonts and third-party chat widgets.
- A phone number in the header as real text beats any click-to-call plugin.
- Getting under two seconds on a small trade site is a rebuild, not an optimisation plugin.
What we measured
Ten Bristol trade sites, chosen from the first page of results for emergency searches in BS1 to BS16. Each loaded five times on a simulated 4G connection on a mid-range Android handset, measuring time until the phone number was visible and tappable. We used the median.
Four sites came in under three seconds. Three took between three and five. Three took longer than five seconds, and one of those never displayed a phone number above the fold at all on a 375px screen.
Where the seconds go
- Page builders shipping 400KB of CSS and JavaScript to render a heading and a button.
- A full-width hero carousel of three images, none of which the customer looks at.
- Two or three web font families loading before any text appears.
- A live chat widget that loads before the page content and is never staffed at 9pm.
- Uncompressed photographs straight off a phone, at 4MB each.
What actually fixes it
On a WordPress site with a page builder, the honest answer is usually a rebuild. You can win a second back with caching and image compression, but the builder itself is the cost. A static site built on Astro ships almost no JavaScript, and the sites SEO Bristol builds land between 0.9 and 1.4 seconds without any optimisation work at all.
Whatever the stack, two rules hold. Put the phone number in the header as plain text, not inside an image or a widget. And let the text render before the fonts finish loading, so the page is usable while it is still arriving.
Questions people ask
Is a fast site actually a ranking factor?
A modest one. The bigger effect is that people ring you instead of bouncing back to the results page, which Google also notices.
Can I test this myself?
Yes. PageSpeed Insights, mobile tab, and look at Largest Contentful Paint. Anything over 2.5 seconds is costing you calls.
Do I need to lose the chat widget?
If nobody answers it out of hours, yes. An unanswered chat box is worse than none.
Fast sites, built to rank from day one. Web design from £99 a month, hosted on your own Netlify account, by a Bristol SEO agency that builds for search first.
See web design