How image optimisation works
Images are usually the heaviest thing on a page, and optimising them means pulling four separate levers rather than running one plugin.
The first is dimensions. A photo straight from a phone camera is far wider than any column it will sit in, and shrinking it with CSS does not shrink the download — the visitor still pays for every pixel their screen will never show. The second is format: newer formats store the same picture in a smaller file, so the choice of format alone changes the weight. The third is compression, discarding detail the eye does not notice. The fourth is delivery: sending a smaller file to a phone than to a desktop, and postponing images that sit far below the first screen.
Alt text belongs here too. It is not a speed lever, but it is how a screen reader and an image search engine understand what the picture shows.
Why image optimisation matters
On most business websites the largest visible element is a photograph, which means the picture decides when the page appears to have loaded. Fix the images and the headline speed number usually follows without touching a line of code.
It also costs your visitors money. In Nepal, and across much of the region a Nepali business sells into, a large share of traffic arrives on mobile data with a finite bundle. An oversized hero image spends someone’s data on pixels their screen discards. A slow, expensive page on a phone is a page people leave.
Common mistakes with image optimisation
Uploading straight from the camera is the most common by far, and no amount of caching rescues it. Close behind is over-compression: pushing quality down until skies band, edges blur and a product photo stops looking like the product, which costs sales far more than a fraction of a second saves.
Then there is the plugin assumption — installing an optimiser and treating the job as done, when the tool is compressing an image that was the wrong size to begin with. And lazy loading applied indiscriminately, including to the hero, which delays exactly the image the visitor is waiting for.
How to act on it
Work in the order the levers actually bite. Export at the width the image will really display, choose a modern format such as WebP or AVIF with a fallback, compress until you can see the loss and then step back one notch, and only then think about delivery. Add descriptive alt text as you upload, while you still remember what the picture shows.
Then set a rule for whoever adds content next, because this is a habit problem more than a technical one. A maximum upload width, a required alt text field and a shared export preset will keep a site fast for years; a one-off clean-up will not survive the next batch of product photos.
