Skip to content
Web Devil Studios, home
Menu

Technical

Why is my website slow, and does it matter for leads?

By Nate Sargeant

Most slow sites are slow for three reasons: uncompressed images, too many third-party scripts, and a heavy theme or page builder. It matters for leads because a page taking more than three seconds to become usable on mobile loses visitors who already clicked, before anyone reads a word.

Speed is the rare website problem that is fully measurable, has known causes, and is usually fixable without a rebuild. It is also the one most often dismissed, because the site feels fine to the person who owns it, loading from cache, on a desktop, on office wifi.

Your visitors are not having that experience.

How do I actually measure it?

Not by loading the site and deciding it feels quick. Use a tool that simulates a real mobile visitor.

Run the page through Lighthouse, in Chrome’s developer tools under the Lighthouse tab, set to Mobile. It will simulate a slower connection and a slower processor, which is what most of your traffic actually has.

The number that matters most is Largest Contentful Paint, which is how long until the biggest visible thing on screen has rendered. Under 2.5 seconds is considered good. Above 4 seconds is a problem worth money.

Two other numbers worth reading: Cumulative Layout Shift, which measures whether content jumps around as it loads, and Total Blocking Time, which measures how long the page is unresponsive to taps. A page that visibly reflows while someone is trying to tap a button is losing people who intended to convert.

What makes small business sites slow?

Three causes account for the overwhelming majority.

Uncompressed images. The most common by a wide margin. A photo straight off a phone or a stock library is often four or five megabytes. Displayed at 800 pixels wide it needs a small fraction of that. Ten such images on a homepage is tens of megabytes of transfer for a page that should weigh well under one. Resizing and converting to a modern format like WebP or AVIF routinely cuts image weight by most of its size with no visible difference.

Third-party scripts. Analytics, a chat widget, a heatmap tool, a review carousel, two tracking pixels, a font loader. Each is a separate connection to someone else’s server, and several of them block rendering until they finish. The chat widget nobody has answered in eight months is a common find, and removing it is free.

Heavy themes and page builders. A theme built to do everything loads the CSS and JavaScript for everything, including the parts you never used. Page builders often add several hundred kilobytes before your content exists. This is the hardest of the three to fix without rebuilding, which is why it is worth knowing about before choosing a platform rather than after.

Does it really cost leads?

Yes, and the loss is invisible, which is what makes it dangerous.

Someone who leaves because a page did not load does not appear in your inbox, does not fill in a form, and does not remember the visit. There is no signal. The only trace is in analytics, as a bounce that looks like disinterest rather than a technical failure.

It compounds with paid traffic. You paid for that click. If the page has not rendered before they give up, you paid for nothing. It happens most on mobile connections, which is where most ad traffic comes from.

Speed also affects search rankings, but that is the smaller effect and it gets quoted more than it deserves. The direct loss of visitors who already arrived is the bigger cost by some distance.

What should I fix first?

In order of impact per unit of effort:

  1. Compress and resize every image. Largest win, lowest risk, no rebuild. Serve images at the size they display, in WebP or AVIF.
  2. Remove third-party scripts you are not using. Audit what loads. Delete the chat widget, the abandoned heatmap tool, the second analytics package.
  3. Defer what remains. Analytics and tracking do not need to load before content. Anything non-essential should load after the page renders.
  4. Set explicit width and height on images. Costs nothing and eliminates most layout shift.
  5. Check hosting. Cheap shared hosting can add hundreds of milliseconds to every request before your site does anything at all.

Steps one and two solve most cases. If the site is still slow after both, the platform itself is usually the cause, and that is a rebuild conversation rather than an optimization one.

How fast is fast enough?

Fast enough that nobody notices. Under 2.5 seconds to Largest Contentful Paint on a mobile connection is a reasonable target for a small business site, and well under that is achievable for a site that is mostly text and images.

It is worth saying that speed is a floor, not a differentiator. Nobody books a call because a site loaded in 1.2 seconds instead of 2.4. They just do not leave. Speed buys you the chance to be judged on the offer, which is where the actual decision gets made. That is why the way we build lead generation sites treats performance as a build requirement rather than something to fix afterwards, once the cause is already structural.

Next step

Want this looked at properly for your business? Book a strategy call. Thirty minutes, no pitch, and you leave with a plan either way.

Related questions