Images are usually the heaviest part of a web page. A single unoptimised phone photo can weigh 4–8 MB – more than the rest of the page put together. Compressing images is the easiest way to make your website faster, improve Core Web Vitals and save mobile data for your visitors. Here is how to do it without making your images look worse.
Page Contents
The 3 things that make an image heavy
- Pixel size. A 4000 × 3000 photo shown at 800 px wide wastes about 95% of its pixels.
- Format. PNG is great for logos and screenshots but huge for photos.
- Quality setting. JPG and WebP at 100% quality are much larger than at 75–85%, with almost no visible difference.
Fix all three and a 5 MB photo often becomes 100–200 KB.
Step 1: Resize to the size you actually need
Find the largest width the image is shown at on your site and double it for sharp high-resolution screens:
| Where the image is shown | Typical display width | Upload width |
|---|---|---|
| Full-width hero banner | 1200–1440 px | 1920–2560 px |
| Blog post content image | 700–800 px | 1400–1600 px |
| Product thumbnail | 300–400 px | 600–800 px |
| Logo in header | 150–250 px | 300–500 px (or SVG) |
Use our Image Resizer or the “Max width” option in the compressor.
Step 2: Choose the right format
- WebP – the best default for websites. Usually 25–35% smaller than JPG at the same quality, supports transparency and works in all modern browsers.
- JPG – photos where WebP is not accepted (some email tools and older systems).
- PNG – screenshots with sharp text, and graphics that need transparency when WebP is not possible.
- SVG – logos and icons made of shapes; tiny and sharp at any size.
- AVIF – even smaller than WebP; support is growing, but check your platform first.
Read more in our guide to PNG vs JPG vs WebP.
Step 3: Pick the right quality
For JPG and WebP, a quality of 70–85% looks the same as the original to most people. Go lower for small thumbnails and backgrounds, higher for photography portfolios. Always compare before and after at the size the image is shown.
How much can you save?
| Starting image | After resize + WebP at 75% |
|---|---|
| 4032 × 3024 phone photo, 4.8 MB JPG | 1600 px wide, about 150–250 KB |
| 2560 px PNG screenshot, 2.1 MB | 1600 px WebP, about 120–300 KB |
| 1000 px product photo, 600 KB JPG | 1000 px WebP, about 60–100 KB |
Exact results depend on the image – detailed photos compress less than flat graphics.
Other image speed tips
- Lazy-load images below the fold (
loading="lazy"). WordPress does this automatically. - Do not lazy-load the main hero image – it should load first.
- Set width and height on images so the page does not jump while loading (better CLS).
- Use responsive images (
srcset) so phones download smaller versions; WordPress creates these for you. - Remove metadata – camera data and GPS location add size and can reveal where a photo was taken. Re-saving through a compressor removes it.
WordPress users
WordPress resizes uploads into several sizes and adds srcset automatically, but it does not shrink the original much. Compress images before uploading, or use an image optimisation plugin. Then test your site with our Website Checker.
FAQ
How do I compress an image without losing quality?
Resize it to the size you need, save it as WebP or JPG at 75–85% quality, and compare with the original at normal viewing size.
What is the best image format for websites?
WebP for most images, SVG for logos and icons, and PNG only when you need lossless quality.
What size should website images be in KB?
Aim for under 200 KB for large images and under 100 KB for content images. Thumbnails can be 20–50 KB.
Does compressing images help SEO?
Yes, indirectly. Faster pages improve Core Web Vitals and user experience, which are part of how Google evaluates pages.
Are my images uploaded when I compress them?
Not with our tool – compression happens in your browser.
Need a website or app for your business? Talk to Techpass Master – we design and build websites and apps for clients worldwide.
