Why a slow website loses customers, and how to fix it

A customer taps your link from a WhatsApp message, waits, sees a white screen, and goes back to the search results. You never find out it happened. There is no error log for “person got bored,” which is why slow websites stay slow for years while the owner wonders why enquiries dried up.

Speed is one of the few website problems you can diagnose yourself in a couple of minutes, without knowing any code. Here is what actually causes it, in plain terms, and what to do about each one.

What a slow site actually costs you

Three things, roughly.

First, people leave. Mobile users on a patchy 4G connection in a tier-2 city are not going to wait eight seconds for your product page. They will hit back and click the next result, which is often your competitor.

Second, the ones who stay convert worse. A sluggish checkout or enquiry form feels broken even when it works. People abandon halfway because they are not sure the submit button did anything.

Third, Google notices. Page experience is one signal among many, and it will not rescue a site with thin content or lift you above a much stronger competitor. But when two businesses are otherwise similar, the faster one tends to win the position. And if you are running ads, a slow landing page quietly raises what you pay per click, because ad platforms score landing page experience too.

The frustrating part is that speed problems are rarely exotic. In most sites we look at, it comes down to four causes, often all four at once.

Cause 1: Images that were never resized

This is the single most common reason an Indian small business website is slow, and it is almost always accidental.

Someone photographs the shop, the product, the team. The camera or phone produces a file that is several thousand pixels wide and several megabytes in size. That file gets uploaded directly into the website. The browser shrinks it visually to fit a 400-pixel-wide slot on screen, but it still downloads the entire original file first.

Put eight of those on a homepage and you have a page that weighs more than a small mobile app. On office WiFi it feels fine. On a phone outside, it crawls.

The fix is boring and effective:

• Resize images to roughly the size they are actually displayed at. A product thumbnail does not need to be 4000 pixels wide.
• Compress them. Most photos can drop a large share of their file size with no visible difference.
• Use modern formats like WebP, which your developer can enable site-wide.
• Turn on lazy loading, so images further down the page only load when someone scrolls to them.

If you do nothing else from this article, do this one. It often halves load time on its own.

Cause 2: Page builders and the plugin pile

Many WordPress sites are built with a visual page builder. Builders are genuinely useful. They let a non-technical person edit content without calling anyone. The cost is that they generate a lot of extra code behind every section, and they load their own stylesheets and scripts on every page, including pages that do not use those features.

Then the plugins stack up. A slider plugin. A contact form. A chat widget. A popup for the newsletter. A social feed. A security plugin. An SEO plugin. A backup plugin. Two analytics tools because someone added Google Analytics and someone else added a heatmap tool. A review widget. Each one seemed small.

Every plugin that adds something to the front end also adds files the browser must fetch and run. Twenty plugins can mean dozens of extra requests on every single page load.

You do not need to become an expert here. You just need to ask your developer for a list of active plugins and, for each one, what it does and whether you still use it. Anything that is not earning its place should go. A homepage slider that nobody clicks past the first slide is a common candidate.

If the site is old and has been patched by three different agencies over the years, a rebuild on a clean, lighter foundation is sometimes cheaper than continuing to untangle it. That is a judgement call, and a decent web design and development team should be willing to tell you honestly which one your site needs.

Cause 3: Hosting that costs less than your monthly chai budget

Shared hosting is fine for a lot of small business sites. Cheap oversold shared hosting is not.

Here is what “oversold” means in practice. The hosting company puts a large number of websites on a single server. Each site is promised resources that, added together, exceed what the machine actually has. Most of the time this works, because most sites are idle. When several sites on that server get busy at once, everyone slows down, including yours, and there is nothing wrong with your site at all.

Symptoms of a hosting problem rather than a site problem:

• The site is slow at certain times of day and fine at others.
• The admin dashboard is slow to load even though the public pages look simple.
• The very first byte takes a long time to arrive, before any images or design load.
• The site occasionally times out entirely for a few minutes.

Another hosting issue specific to Indian businesses: server location. If your customers are in Pune and your server is in a data centre in another continent, every request makes a long round trip. For a site serving mostly Indian traffic, a server in India or nearby, or a CDN that caches your content closer to visitors, makes a measurable difference.

Moving to better hosting is usually the cheapest meaningful speed upgrade available, and it does not require touching your site’s design at all.

Cause 4: No caching

Caching means storing a ready-made copy of a page instead of rebuilding it from scratch for every visitor.

Without caching, every time someone opens your About page, the server queries the database, assembles the page, applies the theme, runs the plugins, and produces the HTML. It does this again for the next visitor, and the next, even though the page has not changed in months.

With caching, the server builds the page once and serves the saved copy to everyone until you update it. For a typical business website where content changes weekly at most, this is an enormous saving for almost no effort.

There are a few layers of caching, and you want them all working:

• Page caching on the server or via a plugin.
• Browser caching, so returning visitors do not re-download your logo and fonts every time.
• A CDN, which keeps copies of your files on servers in multiple cities so the content travels a shorter distance.

If your developer says caching is already enabled, ask them to confirm it is actually working. A cache plugin that is installed but misconfigured is common.

Core Web Vitals, without the jargon

Google publishes three measurements that describe how a page feels to a real person. You will hear vendors throw the names around. Here is what they mean.

Largest Contentful Paint (LCP) answers: how long until the main thing appears? Usually the hero image or the headline. Google considers under 2.5 seconds good. If your LCP is poor, the culprit is almost always a giant unoptimised hero image or a slow server.

Interaction to Next Paint (INP) answers: when someone taps something, how quickly does the page respond? Under 200 milliseconds is good. Poor INP usually means too much JavaScript running, which points back to plugins and third-party widgets.

Cumulative Layout Shift (CLS) answers: does the page jump around while it loads? You have experienced this. You go to tap a link, an ad or image loads above it, everything shifts down, and you tap the wrong thing. Google wants this score under 0.1. Fixing it usually means telling the browser in advance how much space each image and embed will occupy.

That is the whole thing. Three questions: does it appear fast, does it respond fast, does it stay still.

How to check your site in two minutes

Open a browser and search for PageSpeed Insights. It is Google’s free tool. Paste your homepage URL and run it.

Read the mobile tab, not desktop. Most of your traffic is on phones, and mobile scores are always harsher because the test simulates a mid-range phone on a slower connection. That is closer to your actual customer than your office desktop is.

Two things to look at:

The top section may show field data, which is real measurement from actual Chrome users who visited your site. If it appears, it is the most honest number you have. If it does not appear, your site may not get enough traffic for Google to have collected it, which is not a problem in itself.

Below that is lab data and a list of opportunities. Ignore the overall score out of 100 for a moment. Read the opportunities list. It will say things like “properly size images” or “reduce unused JavaScript” and tell you roughly how much time each fix would save. That list is your conversation starter with whoever maintains your site.

Do the same test on your two or three most important pages, not just the homepage. The page you run ads to matters more than the homepage nobody visits.

Also test a competitor’s site. It is a useful reality check in both directions.

What to ask your developer

Take the PageSpeed report and ask four questions:

1. Are our images resized and compressed, and is WebP enabled?
2. Which plugins are active, and which can we remove?
3. What are our hosting specs, and is the server located in India?
4. Is page caching, browser caching, and a CDN all switched on?

You do not need to evaluate the technical answers. You need to see that the person has answers and a plan with an order of operations. If the response is vague or the only suggestion is a full redesign without explaining why, get a second opinion.

Speed work also affects the return on everything else you spend. A faster landing page makes your ad budget go further, which is why it is worth sorting out before scaling up any digital marketing push rather than after.

Where to start

Run the PageSpeed test today. Look at mobile, read the opportunities list, and resize your images. That one step, done properly, solves more slow websites than anything else on this page.

If the report points at hosting or a tangle of plugins and you would rather not manage it yourself, get in touch with Spier Infotech and we will look at what your site is actually doing and tell you which of the four causes applies. Usually it is two of them, and usually the fix is smaller than people expect.