The verdict in three sentences
On a Senegalese website, images make up 60 to 70 % of a page's weight and are the number-one cause of slowness on 3G. Converting to WebP saves ~30 % of weight and AVIF up to 50 % at equivalent visual quality. Combined with lazy loading and responsive sizes, these formats cut an LCP from 4.5 s to under 2.5 s on mobile.
Why images kill speed on 3G
An average 3G connection in Dakar often caps between 1 and 3 Mbps in practice. A homepage loaded with unoptimized photos easily weighs 3 to 5 MB: at that rate, full rendering exceeds 8 seconds, and half of visitors leave before it finishes. Every megabyte saved translates directly into seconds gained and data preserved for the user.
The 2026 order-of-magnitude target: a page under 1.5 MB, an LCP under 2.5 s, and images served at the size actually displayed (not a 4000 px photo shrunk in CSS to 400 px).
JPEG, WebP, AVIF: the comparison
| Format | Relative weight (typical photo) | Reduction vs JPEG | Browser support | Speed gain |
|---|---|---|---|---|
| JPEG | 320 KB | baseline | 100 % | baseline |
| PNG | 780 KB | +140 % (heavier) | 100 % | negative |
| WebP | 220 KB | ~30 % | ~97 % | good |
| AVIF | 160 KB | ~50 % | ~92 % | excellent |
| AVIF + responsive | 60–90 KB | ~75 % | ~92 % | maximal |
Recommended strategy: serve AVIF first, with a WebP fallback, and a final JPEG fallback via the tag. No visitor is left out, and 92 % receive the lightest format.
Lazy loading and responsive sizes
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
| Technique | Effect | Effort | Typical gain |
|---|---|---|---|
loading="lazy" | Loads only visible images | Very low | -40 % initial data |
Responsive srcset | Serves the right size per screen | Low | -50 % on mobile |
| AVIF/WebP compression | Reduces weight per image | Medium | -30 to -50 % |
| CDN + image cache | Delivery closer to user | Medium | -100 to -150 ms latency |
| Explicit dimensions | Avoids layout shift (CLS) | Very low | Better Core Web Vitals |
Mini case study
Awa runs a fashion boutique in Dakar. Her collection page shows 20 JPEG photos of 300 KB each, i.e. 6 MB on load. On 3G (2 Mbps), full rendering takes ~24 s. After converting to responsive AVIF (average 80 KB) and lazy-loading the 12 off-screen images: only 8 images load initially, i.e. 640 KB, rendered in ~3 s. Result: LCP more than halved, and a visitor who stays instead of fleeing.
FAQ
Is AVIF compatible enough in 2026? Yes, roughly 92 % of browsers support it. With a WebP then JPEG fallback in a tag, 100 % of visitors see the image and the vast majority receive the lightest version.
Will I lose visual quality? No. At correct settings AVIF offers quality equivalent to JPEG for ~50 % of the weight. The difference is invisible to the eye on a standard product photo.
Do I have to reconvert all my images manually? No. Next.js and most modern CMS automatically convert to WebP/AVIF and generate responsive sizes. On a Kolonell site, it's built in by default.
What SEO gain is there? Speed is a Google ranking factor. An LCP going from 4.5 s to under 2.5 s improves Core Web Vitals and can lift conversion rates by 10 to 20 % depending on traffic.
Let's talk about your project. We audit your image weight and deliver an AVIF/WebP-optimized site that's fast even on 3G. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.

