How to speed up a slow business website without a rebuild

A buyer opens your site on a phone in a godown or a shop, sees white space, and goes back to the search results. You never learn that the visit happened. The causes are often dull: photographs nobody shrank, three font families, plugins nobody remembers installing, and a hosting plan shared with too many sites. Fix them in that order, testing on a mid-range phone on mobile data. Stop when the page opens before a patient visitor would give up. Many sites do not need a rebuild.

First, see what your buyer sees

Your office broadband and your laptop hide the problem. Take a phone that is two or three years old, switch off Wi-Fi, and open your home page and your busiest service page. Count slowly. If the main heading and the phone number are not readable by the time you reach five, you have a problem worth fixing.

Then run the page through a free speed testing tool and note two things only: the largest item on screen (usually a hero photograph) and the list of files it loads. You are not chasing a score. You are looking for the one or two files that weigh most.

Write the result in a small note: date, page, how long it felt, heaviest file. For example: "3 Mar, home page, about nine seconds on mobile data, a 5 MB hero photograph." You will want that line later to prove the work did something.

Which fix first? A rule of thumb by symptom

Images, the usual first suspect

A photograph straight from a phone can run to several megabytes. On a page that shows eight of them, the visitor downloads a small film. Three habits cover most of it.

Resize before you upload. A picture shown 600 pixels wide does not need to be 4,000 pixels wide. Compress it with any free tool. Use a modern format where your site software supports it, and keep the old one as a fallback.

Do not load everything at once. Pictures far down the page can wait until the visitor scrolls. Many site builders have a setting for this, called lazy loading.

Remove slide shows. A rotating banner with five large photographs loads all five. One strong picture and a clear heading are lighter.

Fonts, scripts, plugins and hosting

Fonts are the quiet offender. Every family and every weight is a separate file. A site using three families in four weights asks the phone for twelve files before the heading looks right. Pick one family, two weights, and host them on your own site if you can.

Plugins come next. Each one adds code, and some add it to every page whether it is needed or not. Open your plugin list and ask of each: what would stop working if this went? If you cannot answer, take a backup, switch it off on a copy of the site, and see.

Chat widgets, heat map tools and several analytics tags also slow the first view. Keep the ones you read; remove the rest.

When the problem is hosting

If a nearly empty page still takes a long time to begin loading, the server is the bottleneck. Shared plans put many sites on one machine, and yours can suffer when a neighbour is busy. A server far from your buyers adds delay too: a site served from another continent to buyers in Madurai makes every file take longer to arrive.

Ask your host three plain questions. Where is my site stored? Is it on shared space or its own? Is there page caching switched on? The answers decide whether a plan change helps. The note on what to ask before paying for hosting goes through the rest, and website hosting and security covers a move if one is needed.

A crockery seller in Khurja

An invented example. A seller of ceramic tableware in Khurja has a WordPress site that hotel and restaurant buyers open from Lucknow and Delhi, mostly on phones. The owner's brother-in-law uploaded sixty product photographs straight from a phone. The home page also has a video background, a chat tool nobody answers and two sliders.

The owner's first move is to pay for a bigger hosting plan, at ₹6,000 more for the year. Nothing changes, because the host was never the slow part. A test of the plain contact page shows it opens at once, so the server is fine and the home page is heavy.

So the work goes in order: photographs resized to the width they are shown at, the video replaced with one still picture of the factory floor, the second slider and the chat tool deleted, fonts cut to one family. The same phone now opens the home page in a few seconds, though the product gallery is still slower than the rest because it holds sixty pictures. The bigger plan was money wasted; had the contact page also been slow, that would have been evidence to take to the host.

Keeping it fast afterwards

Speed decays. Someone uploads a large banner for Diwali, a plugin is added for a campaign, and the old numbers return. Give one person the job of checking the home page on a phone each time the site changes, and keep the note you made at the start for comparison. Send photographs to whoever uploads with a rule: resized, compressed, named plainly.

A new design will not fix this on its own: a rebuilt site loaded with the same images and scripts will be slow too.

Start with the heaviest photograph

Open your home page on the old phone this week, write the one-line note, and shrink the single heaviest photograph. Then test again. Do the other fixes yourself in the order above, removing plugins only with a backup in hand, and ask the host the three questions only if plain pages stay slow. A page that opens quickly matters because every ad, listing and message in your marketing points at it. If you would rather have someone test every page after the change, website speed and performance optimisation covers that, and you can tell us what you need.