Why is my online store slow? The usual causes, and what to fix first

TL;DR

• • Two kinds of slow: a slow answer (a white screen) and a heavy page (photos that crawl in).
• • Test like a buyer: Wi-Fi off, from your Instagram bio link, on the product page you advertise.
• • Five usual causes: huge photos, too many add-ons, a slow answer from the server, a video at the top, and too many products on one page.
• • Four of the five you can fix today, free, without a developer.
• • The answer itself is down to your platform. On SitesPlaced, Starter and up answer in about 75 ms instead of about 330 ms (measured 28 September 2026).

Two kinds of slow: the answer and the load

When a shopper taps your link, their phone asks the server where your store lives for that page. The server has to find your products, prices and stock, put the page together and send it back. The time until that reply starts arriving is the answer time. Until then, the shopper sees a blank screen, perhaps with a thin progress bar creeping across the top.

Once the page has answered, the phone reads it and starts fetching everything it names: product photos, fonts, any video, any chat widget or tracking tag. That is the load. It is why a page can show its words quickly and still have grey boxes where the photos should be.

Think of calling a shop. The answer is how long the phone rings before someone picks up. The load is how long the conversation takes. A caller who hears it ring and ring hangs up before they learn anything about what you sell. (Tools such as Google’s PageSpeed Insights call the answer time “time to first byte”. It is the same thing.)

How to check your store on your phone (two minutes)

1. Turn off Wi-Fi so you are on mobile data, like most of your buyers.
2. Open Instagram, go to your own profile and tap the link in your bio. Instagram opens links inside its own browser, and that is where many of your shoppers first see your store. For WhatsApp buyers, send the link to a friend and ask them to tap it.
3. Count, roughly. How long until anything appears? How long until the first product photo and price? How long until you can tap Add to cart?
4. Now open a product page you have shared in a story or an ad, and count again.
5. Trust the first try. A second visit is often quicker because the phone kept some files from the first. A new shopper only ever gets the first visit.

For a second opinion, paste your store link into Google’s free PageSpeed Insights and look at the mobile result. Don’t chase the score. Look at two things: whether it flags a slow server response (that is the answer) and which images it says are too large (that is the load).

What you see, and what it usually means

The five usual causes

1. Huge photos straight from the phone

A photo from a modern phone camera is far bigger than a phone screen needs, and photos are most of what a store page weighs. SitesPlaced resizes the photos you upload to the size the page needs before a shopper downloads them, so nobody is sent the full original. You still decide how many photos sit on a page and how busy they are. Crop tight, put one clear photo first on each product, and avoid collages and screenshots with text baked in. For better photos in the first place, see how to take better product photos.

2. Too many add-ons and tracking tags

Every chat widget, popup tool, review widget and tracking tag is extra code the phone has to download and run. One or two are fine. On platforms with an app store, sellers often end up with a stack of them, each added for one reason and never removed. On SitesPlaced the popups and other sales boosters are built in and stay off until you switch them on, and extra tracking tags only go in if you paste them in yourself (custom head code, on Starter and up). Keep only the tags you actually look at.

3. A slow answer from the server

Before a page can answer, the server has to build it: look up products, prices and stock, and assemble the page. If it builds every page fresh for every visitor, every visitor waits for the build. Distance matters too, because every trip between the phone and a far-away server takes time. This is the one cause you can’t fix by editing your store. It depends on the platform and, on SitesPlaced, on your plan. More on that below.

4. A video as the first thing on the page

A video background looks lovely on a laptop on office Wi-Fi. On mobile data it is usually the heaviest thing on the page, and until it arrives the shopper may see a blank or frozen frame where your headline should be. Use a strong photo for the first screen. Put the video lower down, or keep it on Instagram, where people expect to watch.

5. Too many products on one page

A page that lists everything you sell is bigger before it even starts, and it keeps asking for photos as the shopper scrolls. Send people to a category instead. On SitesPlaced every category has its own link, like yourbrand.com/sarees. Keep the home page to a few short rows, such as bestsellers and new arrivals, and link your ads to the exact product.

What you can fix today, for free

• • Replace your three worst product photos with clean, cropped ones.
• • Swap a video first screen for a photo.
• • Hide home-page sections you don’t need. In the SitesPlaced editor, the eye icon hides a section in one tap.
• • Use one banner, not five.
• • Link ads and stories to the product or category, not the home page.
• • Remove any tracking tag or widget you added and never check.
• • Test again on mobile data, from your bio link.

None of this costs anything or needs a developer, and it helps with more than speed: a page with fewer, better things on it is easier to buy from. If your store is quick but still not selling, the reason is usually elsewhere. See why your online store is not getting sales.

What a paid plan changes, and what it doesn’t

On the free plan, most store pages are built fresh when a shopper asks for them, because a small store’s pages aren’t visited often enough for a ready copy to still be there. On every paid plan, Starter (₹199/month) and up, SitesPlaced keeps a ready copy of each store page close to your shoppers, so the page answers without waiting for a build.

We measured it on 28 September 2026 on live paid stores. A page answered in about 75 ms instead of about 330 ms. A millisecond (ms) is a thousandth of a second, so that is under a tenth of a second against about a third. Those are the middle of the measurements; store by store, it ranged from 2.3× to 5.5× faster. That is why we say store pages answer about 4× faster on a paid plan.

Your changes still show at once. Every edit, price change or stock change clears the ready copy, so the next shopper gets the new page. Cart, account and order-tracking pages are never kept at all, because each is built for one shopper. And there is nothing to switch on: it runs for every paid store.

What it doesn’t do: it speeds up the answer, not the photos. A heavy page on a paid plan still has heavy photos, so do the free fixes too. The two together are what a shopper feels. How it works, and how we measured it, is in our announcement.

Frequently asked questions