
If your site is slow on phones, the first thing to check is the photos. According to HTTP Archive’s 2025 Web Almanac, which analyzes millions of sites, the typical home page weighs 2.6 MB on mobile, and 911 KB of that is images: more than a third.
Also, on 68% of mobile pages the largest element visible on load is an image, according to the 2024 edition. That element sets the LCP, one of the Core Web Vitals Google uses to measure your page’s experience.
The good news: it’s one of the easiest things to improve. These are the steps, from most to least impact.
1. Use the width that’s actually displayed
A photo taken on a phone can be 4000 px wide. If your site shows it in an 800 px space, the browser downloads five times more width than it needs, and shrinks it to display it.
The rule from web.dev, Google’s web development site, is to prepare the image at twice the width it’s displayed at, so it looks sharp on high-density screens: a photo that takes up 400 px needs 800 px. As a reference:
- Full-width photo: 1920 px is usually enough.
- Photo inside text or a card: 1280 px or less.
- Logos and icons: better as SVG, which looks good at any size.
2. Convert photos to WebP or AVIF
These are formats designed for the web that, at similar quality, usually weigh much less than JPG or PNG. And compatibility is no longer an excuse: according to Can I use, AVIF works in browsers that account for 96.7% of global usage.
Even so, they’re still a minority. In 2024, only 12% of images on mobile sites were WebP and 1% AVIF, against 32% JPG and 28% PNG.
3. Compress, but look at the result
Compressing means lowering quality a little to save a lot of weight. For photos, start at a quality of 80 and compare with the original: if you can’t see the difference, try a bit lower.
With our free image compressor you choose quality and maximum width, see how much you save and download the photos as WebP. They’re processed in your browser: nothing is uploaded to a server.
4. Don’t delay the main image
Lazy loading (loading="lazy") makes images further down download only when the person gets close to them. It’s a very good practice, except for the main image: web.dev is blunt that you should never apply it to the LCP image, because it delays it.
And it’s a common mistake: almost one in ten main images is lazy-loaded, according to the Web Almanac. The hero image, instead, should be given priority with fetchpriority="high".
5. Set the width and height
If an image has no width and height in the code, the browser doesn’t know how much space to reserve, and when it arrives, it pushes the text down. That jump is what another Core Web Vital, CLS, measures. Only 32% of mobile images had both attributes in 2024.
6. Offer several sizes
With srcset, the site offers the same photo in several widths and the browser chooses: the phone downloads the small one, the computer the big one. In 2024, 42% of mobile pages used it. Many platforms and tools do this automatically; on this very site, for example, team photos are generated as AVIF, WebP and JPG in several sizes.
7. Measure before and after
Run the speed test before changing anything and again afterwards. That way you know how much you really improved, and if something’s still pending, the report tells you which image is too heavy.
One more detail: alt text
It doesn’t make the page load faster, but it helps: alt text (alt) describes the image for people using screen readers and helps Google understand what it shows. “Chocolate cake with strawberries” works; “IMG_2034” doesn’t.
If your site is still slow after optimizing the photos, the problem may be elsewhere. In websites we explain how we build them to load fast from day one.