Smart Web Support logo Smart Web SupportPlain answers for keeping a small business website running
Site Speed

Homepage Image Weight and How to Cut 11 MB Down to 1 MB

A tailoring shop in Dhanmondi asked me last year why customers kept saying the website never opened. On the shop's own WiFi it opened in two seconds, which is why nobody believed there was a problem.

A laptop network panel listing large image files beside a phone showing a slow loading shop homepage

A tailoring shop in Dhanmondi asked me last year why customers kept saying the website never opened. On the shop's own WiFi it opened in two seconds, which is why nobody believed there was a problem. I loaded the homepage on a throttled connection from my phone, the kind of speed you actually get on a crowded 3G cell at six in the evening, and watched it take 41 seconds. The page was 11.4 MB. Of that, 10.8 MB was pictures.

Nothing was broken. Nobody had installed a bad plugin. Somebody had simply uploaded photographs straight off a phone into a slider, six of them, each around 1.8 MB, and then added a logo saved as a PNG at 480 KB because that was the file the designer sent. This is the single most common performance problem I see in small shop websites, and it is also the cheapest one to fix. An afternoon of careful work took that homepage to 940 KB and the same throttled test to 4.6 seconds.

Find out where the weight actually sits

Guessing wastes a morning. Open the homepage in Chrome, press F12, go to the Network tab, tick Disable cache, reload, then sort by the Size column. The browser will tell you exactly which files cost what. Look at the total at the bottom of the panel too, because that number is the honest one.

In nine years of doing this for clinics, tailors and small shops, the weight has landed in the same four places almost every time. Hero sliders, because each slide is a full size photograph and most of them are never seen. Gallery or product thumbnails that are full resolution images scaled down by CSS, so the visitor downloads 4000 pixels wide to display 320. Logos exported as PNG when they are flat shapes that belong in SVG. And background images in theme sections, which are easy to forget because they are set in the page builder rather than the media library.

Check the pixel dimensions, not just the file size. In the Network panel, hover a file and it shows the intrinsic size. A photograph that is 4032 by 3024, straight from a phone camera, is around 4 MB and is being displayed in a box perhaps 600 pixels wide. You are sending roughly forty times the data the screen can use.

The three changes that do nearly all the work

Resize first, before anything clever. Decide the widest size each image slot ever needs to be, then resize the file itself to that. For a full width hero on a shop site, 1600 pixels wide is plenty, and 1920 if the design really is edge to edge on large monitors. Product thumbnails rarely need more than 800. Resizing a 4032 pixel photograph to 1600 typically cuts the file by 80 to 85 percent before you touch quality at all.

Then choose a format and a quality setting. WebP at quality 72 to 78 looks indistinguishable from the original for photographs of fabric, food, faces and rooms, and lands somewhere between 25 and 45 percent smaller than a JPEG at the same visual quality. AVIF goes smaller still, often another 20 percent, with slower encoding and more support quirks in old phone browsers. For flat graphics, logos, icons and line drawings, SVG is a different category of win: that 480 KB PNG logo became a 9 KB SVG and got sharper on high density screens.

Third, tell the browser the sizes. Every image tag should carry width and height attributes so the browser reserves the right space and the page stops jumping while it loads. Add loading="lazy" to everything below the first screenful, and leave it off the hero image, because lazy loading the thing the visitor is looking at makes the page feel slower. WordPress generates a srcset of multiple sizes automatically if your images are uploaded large enough and your theme uses the standard functions; the common failure is a page builder that hardcodes one source and ignores all of it.

Where the usual advice gets it wrong

The standard answer in every forum is to install a compression plugin and let it handle the problem. I have installed plenty of them and I still do on sites where several people upload photos, but treating the plugin as the fix is how shops end up with a 6 MB homepage and a green optimisation badge in the dashboard.

A compression plugin does one job well, which is re-encoding files to a smaller byte size. It does not decide that your hero slider has six slides when one would sell more. It usually does not change the pixel dimensions of what is already uploaded unless you set a maximum width and run a bulk job, and a lot of owners never find that setting. And it cannot do anything about a background image set in a builder module that never passed through the media library.

The other claim worth arguing with is that converting everything to WebP is the main event. On the tailor's site, converting the original 1.8 MB phone photographs to WebP without resizing took the page from 11.4 MB to about 7 MB. Useful, and nowhere near enough. Resizing those same files to 1600 pixels wide as plain JPEG got the page to roughly 1.6 MB. Doing both got it under 1 MB. The order matters because resizing removes data the visitor can never see, while format conversion only encodes the same picture more efficiently.

Something I cannot settle for you: whether to drop the slider entirely. I think most shop sliders are decoration that costs money, and two clients kept theirs anyway and are doing fine. What I will say is that if you keep it, three slides is the ceiling, and only the first one should load before the visitor scrolls.

An hour of work, in order

This is the sequence I run on a client homepage. It assumes WordPress, though the logic holds anywhere.

  1. Record the starting numbers: total page weight and load time on a throttled mobile profile, so you can prove the change later.
  2. List every image on the homepage with its file size and pixel dimensions from the Network panel, including background images from the builder.
  3. Decide the maximum display width for each slot, then resize the source files to that width in any editor that does batches.
  4. Export photographs as WebP at quality 75, and re-export flat logos and icons as SVG.
  5. Replace the files in the media library rather than uploading duplicates, so you do not leave the old ones serving on other pages.
  6. Add width and height attributes everywhere, set lazy loading below the fold, and leave the hero eager.
  7. Clear the cache, including the one at your CDN if you have one, then re-run the same throttled test and write both numbers down.

Step seven catches more mistakes than any of the others. Caching layers are very good at serving you the old page while you congratulate yourself, which is also why speed work should be measured the way a page waterfall shows it rather than by a single score. If the page is still heavy after all of this, the remaining weight is usually fonts and scripts rather than pictures, and that is a different afternoon.

One last thing about who you are optimising for. The tailor's customers were mostly on mid range Android phones on mobile data, which is the common case across the whole small business web here, and the same reasoning that applies to lightweight sites for budget phones applies to a shop homepage. Test on the connection your customers have, not the one in your office.

FAQ

How small should a homepage be?

Under 1 MB total is a realistic target for a small business site with photographs, and under 500 KB is achievable if the design is simple. The figure that matters more is how long the largest image takes to appear on a throttled mobile connection. Aim to have the hero visible inside about 2.5 seconds.

Will resizing images hurt how the site looks?

Not if you resize to the widest size the slot actually uses and then double it only for genuinely high density displays. The mistake that does hurt is resizing too far and then letting CSS stretch the file back up, which looks soft. Check on a large monitor before you call the job done.

Should I convert images that already load fast?

Probably leave them. Re-encoding a 60 KB thumbnail saves maybe 20 KB and costs you a visual check. Spend the effort on the handful of files over 300 KB, which on most shop homepages account for the great majority of the weight.

Does a CDN remove the need for this?

No. A CDN shortens the distance the file travels and caches it closer to the visitor, which helps, but an 11 MB page delivered quickly is still 11 MB of mobile data. Fix the files first, then add the CDN, and you get both benefits instead of paying for one to hide the other.

FK
Farzana Kabir

Farzana has looked after WordPress sites for clinics, tailors and small shops in Dhaka for nine years, and writes about the upkeep jobs owners skip until something breaks.

More posts by Farzana

More from the blog

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto