More insights.
Subscribe to our newsletter.
Deep dives into design thinking, creative process, and the intersection of business and aesthetics.
Someone in Limerick needs an electrician before the weekend. They search on their phone, tap the first business in the map results and get a white screen while a slow page thinks about it. Before it loads they're back on the results, ringing the next name on the list. That was a local lead, and the business will never know it had one.
Most businesses file website speed under IT. For a local service business it's a sales problem. You paid for that visibility, through search work or advertising, and then kept the door locked while the customer stood outside it.
What a slow page costs you
The often-quoted figure here is Amazon's finding that 100 milliseconds of added load time cost it about 1% of sales. A local firm isn't Amazon, and nobody should read that number across to a builder's website. The behaviour behind it does carry over. A slow site feels broken and a bit careless, and visitors tend to assume the way your website treats them is the way you'll treat them: a page that lags suggests replies and delivery that lag as well.
Your search visibility suffers too. Google counts page experience, loading speed included, among the signals it uses to rank pages, and a poor mobile experience gives it one more reason to put a competitor above you in the local results. It's rarely the only reason a site slips, but it's one you can fix.
Where the weight usually comes from
Most slow-loading sites are slow for dull reasons: the platform they were built on, and the way they've been looked after since launch.
Older sites often run on heavy, general-purpose themes packed with features nobody uses. Over the years plugins pile up on top for analytics, forms, pop-ups, sliders and chat. Many load their own scripts and stylesheets on every page whether it needs them or not, and the browser has to work through all of it before it can show anything useful. Add a few uncompressed photos straight from a phone and a sluggish page becomes a properly slow one.
Test it on a phone, then fix what you find
Start by meeting the site the way your customers do: on your own phone, on mobile data rather than the office wifi, arriving from a Google search rather than a bookmark. If you find yourself waiting, so are they. For the technical detail on how quickly your main content appears, Google's web.dev guidance on optimising Largest Contentful Paint is a good place to start. Most of the fixes are housekeeping, with no developer needed:
Compress your images, the most common offender. Convert JPEGs and PNGs to WebP and run them through a compressor, aiming for under about 200KB each.
Remove plugins you don't need. Go through the active plugins in your CMS, and if one isn't doing a job you can name, such as security or cookie consent, delete it.
Cut scripts nobody uses. Heatmaps and heavy tracking code slow the page while it renders. If no one is looking at that data to make decisions, take the script off.
Look hard at your hosting. Cheap shared hosting puts your site on a crowded server, and if the server itself is slow, no amount of image compression will save you. A good managed host, or a rebuild on a leaner setup, is sometimes the only real fix. It's also the expensive end, so do the other three first and measure again.
A fast site won't win you work on its own, but when two local firms look equally capable, the one whose page opens straight away tends to get the call. Once you've made the changes, repeat the phone test whenever someone adds a plugin, a tracking script or a new banner image, because sites rarely get slow all at once.
Related Brainstorm services and work
Website and technical SEO services · Technology website design · Request a performance review
Updated 24 September 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.
Someone in Limerick needs an electrician before the weekend. They search on their phone, tap the first business in the map results and get a white screen while a slow page thinks about it. Before it loads they're back on the results, ringing the next name on the list. That was a local lead, and the business will never know it had one.
Most businesses file website speed under IT. For a local service business it's a sales problem. You paid for that visibility, through search work or advertising, and then kept the door locked while the customer stood outside it.
What a slow page costs you
The often-quoted figure here is Amazon's finding that 100 milliseconds of added load time cost it about 1% of sales. A local firm isn't Amazon, and nobody should read that number across to a builder's website. The behaviour behind it does carry over. A slow site feels broken and a bit careless, and visitors tend to assume the way your website treats them is the way you'll treat them: a page that lags suggests replies and delivery that lag as well.
Your search visibility suffers too. Google counts page experience, loading speed included, among the signals it uses to rank pages, and a poor mobile experience gives it one more reason to put a competitor above you in the local results. It's rarely the only reason a site slips, but it's one you can fix.
Where the weight usually comes from
Most slow-loading sites are slow for dull reasons: the platform they were built on, and the way they've been looked after since launch.
Older sites often run on heavy, general-purpose themes packed with features nobody uses. Over the years plugins pile up on top for analytics, forms, pop-ups, sliders and chat. Many load their own scripts and stylesheets on every page whether it needs them or not, and the browser has to work through all of it before it can show anything useful. Add a few uncompressed photos straight from a phone and a sluggish page becomes a properly slow one.
Test it on a phone, then fix what you find
Start by meeting the site the way your customers do: on your own phone, on mobile data rather than the office wifi, arriving from a Google search rather than a bookmark. If you find yourself waiting, so are they. For the technical detail on how quickly your main content appears, Google's web.dev guidance on optimising Largest Contentful Paint is a good place to start. Most of the fixes are housekeeping, with no developer needed:
Compress your images, the most common offender. Convert JPEGs and PNGs to WebP and run them through a compressor, aiming for under about 200KB each.
Remove plugins you don't need. Go through the active plugins in your CMS, and if one isn't doing a job you can name, such as security or cookie consent, delete it.
Cut scripts nobody uses. Heatmaps and heavy tracking code slow the page while it renders. If no one is looking at that data to make decisions, take the script off.
Look hard at your hosting. Cheap shared hosting puts your site on a crowded server, and if the server itself is slow, no amount of image compression will save you. A good managed host, or a rebuild on a leaner setup, is sometimes the only real fix. It's also the expensive end, so do the other three first and measure again.
A fast site won't win you work on its own, but when two local firms look equally capable, the one whose page opens straight away tends to get the call. Once you've made the changes, repeat the phone test whenever someone adds a plugin, a tracking script or a new banner image, because sites rarely get slow all at once.
Related Brainstorm services and work
Website and technical SEO services · Technology website design · Request a performance review
Updated 24 September 2026. Dave Curtin, founder and Creative Director of Brainstorm, leads website strategy, brand direction and technical delivery for Brainstorm clients.