- Resize images to the size they are shown on the page.
- Compress photos to a quality of about 75–85.
- Use WebP for website photos, and SVG or PNG for logos.
- Always set image width and height to prevent layout shift.
- Fix your largest above-the-fold image first.
When a website loads slowly on a phone, the cause is very often images: photos uploaded straight from a camera or phone, several megabytes each. The good news is that this is one of the easiest speed problems to fix.
Why image size matters
- Speed: every image has to be downloaded, so big files mean slow pages on mobile data.
- Core Web Vitals: the largest image near the top of the page often decides your Largest Contentful Paint. Google recommends 2.5 seconds or less.
- Enquiries: visitors who wait too long often leave before contacting you.
The 4-step workflow
1. Resize
Make the image roughly the size it is displayed at, or up to twice that for sharp phone screens. A blog image shown 800 pixels wide does not need to be 4000 pixels wide. Use the image resizer.
2. Choose the right format
| Image | Format |
|---|---|
| Photos | WebP (or JPG) |
| Logos and icons | SVG, or PNG/WebP with transparency |
| Screenshots with text | PNG or high-quality WebP |
Convert photos with the JPG to WebP converter.
3. Compress
Start at a quality of about 80 using the image compressor. If you cannot see a difference at normal size, try a little lower.
4. Upload correctly
- Use descriptive file names, such as
bhubaneswar-cafe-interior.webp. - Add helpful alt text.
- Set the image
widthandheightso the page does not jump while loading. - Lazy-load images below the fold, but not the main image at the top.
Sensible size targets
| Image | Width | Target file size |
|---|---|---|
| Full-width banner | 1600–2000 px | Under about 200 KB |
| Blog or content image | 1000–1200 px | Under about 100 KB |
| Thumbnail | 400–600 px | Under about 50 KB |
These are practical guidelines, not strict rules. Very detailed images may need a little more.
Fixing an existing website
- Test your homepage with Google PageSpeed Insights and note the largest images it flags.
- Fix the biggest image at the top of the page first.
- Then fix images on your most visited pages.
- For WordPress sites with many images, an image optimisation plugin can process them in bulk.
Mistakes to avoid
- Uploading images bigger than needed and relying on the browser to shrink them.
- Re-compressing the same JPG again and again.
- Using a heavy image slider with many large photos at the top of the page.
- Removing width and height attributes, which causes layout shift.
How to find your heaviest images
- Open your page in Google Chrome on a computer.
- Right-click and choose Inspect, then open the Network tab.
- Select the Img filter and reload the page.
- Click the Size column to sort the images, largest first.
The top few images are where you will get the biggest improvement. Google PageSpeed Insights also lists images it thinks are too large under its suggestions.
Responsive images in brief
Websites can offer several sizes of the same image and let the browser pick the right one for each screen, using the srcset attribute. WordPress does this automatically for images in your content. On a custom site, ask your developer to set it up, so phones download a smaller version than desktops.
Do not forget the top of the page
Lazy loading delays images until the visitor scrolls near them, which is great for images further down the page. The main image at the top, often your Largest Contentful Paint, should not be lazy loaded, because you want it to appear as early as possible.
Quick wins checklist
- Replace any image over 500 KB with a resized, compressed version.
- Convert large photos to WebP.
- Swap a heavy homepage slider for one strong image.
- Use SVG for logos and icons.
- Add width and height to every image tag.
Want a fast, professionally built site? Talk to our website design team.


