When your website is slow, it is almost always the images, not the hosting. A single unoptimised photo straight off a phone or a camera can be heavier than an entire well-built page. Before you pay to upgrade your hosting, which is where most people jump, check the images. Nine times out of ten, that is the whole story.
Hosting gets blamed because it is the thing you pay a monthly bill for, so it feels like the lever. But upgrading hosting to fix an image problem is like buying a bigger van to move a piano you have not taken off its packing crate. The weight is the problem, not the engine.
How can you check in two minutes, without any tools?
You do not need a testing tool for the first look. You need your own phone on mobile data, not office WiFi.
- 1.Turn off WiFi on your phone so you are on mobile data, the way most of your customers actually visit.
- 2.Open your site fresh, ideally in a private tab so nothing is cached.
- 3.Watch what loads slowly. If the text appears fast and the images crawl in afterwards, you have your answer.
Office WiFi hides the problem, because it is fast enough to drag heavy images through without you noticing. Your customer on mobile data in a moving auto does not have that luxury. Test the way they browse.
What are the four real causes, in order of how common they are?
Slowness has a predictable order. Fix them top to bottom and stop when the site is fast, which is usually after the first one.
- Image weight, by a huge margin. Full-resolution photos served at full size to a phone that only needs a fraction of it.
- Video, when it autoplays and is not compressed or streamed properly.
- Too many third-party scripts, every chat widget, pixel and analytics tag adding to the load.
- Hosting, genuinely last. It matters, but it is rarely the cause of a site that feels slow.
Notice hosting is fourth, not first. That order is deliberate, because it is the order the problems actually occur in, not the order people assume.
What are the numbers that actually fix it?
Fixing images is not guesswork. It is a set of limits applied to every asset before it goes live. These are the ones we build in.
- A cap on image resolution, around 20 megapixels, so a photo is never larger than any screen can use
- Video capped at 720p for web, which is sharp on a phone and a fraction of the weight of 1080p or 4K
- Video compressed at a sensible quality level rather than shipped raw, cutting file size dramatically with no visible difference
- Faststart on video, so it begins playing while it is still downloading instead of after
This matters most where the images are the product. A fashion storefront like Laxakaar lives on large, rich product photography, and that is exactly the kind of site where uncontrolled image weight quietly kills the experience on mobile. Getting the discipline right means the imagery stays beautiful and the page still loads before a customer gives up.
Why does this have to be a build step, not a habit?
Because habits fail. You can tell everyone to compress images before uploading, and it will work for a month, and then a busy week will pass and someone will upload a 12 megabyte photo straight off a camera because it was faster. The only reliable fix is a build that will not let that happen: images are optimised automatically on the way in, so a human being having a bad day cannot slow the site down.
Which symptom points to which cause?
Text loads fast, images crawl in after
Image weight. The most common case by far, and a build-time optimisation fixes it.
The page hangs before anything appears
Usually too many third-party scripts loading before the content, or an autoplay video. Audit the widgets.
Everything is uniformly slow, even light pages
This is the rare case where hosting or the platform is genuinely the bottleneck, and worth checking only after the first two are ruled out.
What this means for you
Before you spend on hosting, check your images on your own phone on mobile data. That two-minute test will tell you more than any invoice upgrade. And insist that image and video optimisation is built into the site, not left to good intentions, because good intentions do not survive a busy week. Our web development builds bake this in, so the site stays fast without anyone having to remember.
Site feeling slow?
Tell us what your visitors experience and we will tell you the likely cause, usually before we have even opened a testing tool.
Book a free call