For image file size SEO, aim for roughly 50-150 KB for ordinary content photos and 150-300 KB for a large hero image. These are working targets, not Google rules. Resize to the space the image occupies, compress it sensibly and test the mobile page. You want sharp photographs, not enormous downloads.
How big should website image files be?
There isn't one correct file size for every website image. A tiny team headshot and a full-width photograph of your latest building project have different jobs. Giving both the same limit makes no sense.
Use these ranges as starting points for the version delivered to the visitor, not necessarily the original stored in your media library.
| Image use | Practical file size target | What to check |
|---|---|---|
| Small thumbnail or team headshot | 20-60 KB | Faces and small details remain clear |
| Standard image within page content | 50-150 KB | It looks sharp at its displayed size |
| Large hero or banner photograph | 150-300 KB | It loads promptly on mobile |
| Detailed product photograph | 100-250 KB for the normal page view | Buyers can see useful product detail |
Those are recommendations, not pass-or-fail thresholds. A detailed photograph may need more data. A simple image may need much less.
Product zoom images can be larger, provided you don't download every full-resolution version before anyone asks to see it.
Also look at the total. Twelve individually reasonable 150 KB photographs still add up to 1.8 MB before scripts, fonts or anything else. A sensible per-image size doesn't automatically produce a lightweight page.
Image file size SEO starts with the right pixel dimensions
File size measures how much data an image contains, usually in KB or MB. Pixel dimensions describe its width and height, such as 1,200 × 800 pixels. They're related, but they aren't interchangeable.
A photograph can have large dimensions and a modest file size after compression. Another can have smaller dimensions but weigh much more because of its format, detail or export settings.
The first question is how large the image actually appears on your website. If a photograph sits in a column 600 pixels wide, serving a 5,000-pixel-wide original is usually unnecessary.
High-density screens complicate this slightly. A 600-pixel-wide display area might benefit from a 1,200-pixel-wide image on a screen with a device pixel ratio of two. That doesn't mean every visitor needs the largest version.
Your website should offer appropriately sized alternatives so the browser can choose. We'll cover that shortly.
Changing the displayed width with CSS doesn't necessarily reduce the download. You can make a 4 MB photograph look tiny on the page while still making the visitor download all 4 MB. The browser hasn't been impressed by your clever shrinking trick. It's still carrying the same load.
Why heavy images matter to rankings and enquiries
The point of image file size SEO is to remove unnecessary downloading, not collect a perfect score for its own sake. Heavy photographs can delay the content someone needs to decide whether to contact you.
Imagine a homeowner opening your roofing page outside on a patchy mobile connection. They want evidence of your work and a phone number. Making them wait for a massive decorative banner gets in the way of both.
Google says its ranking systems use Core Web Vitals alongside other signals. Good scores don't guarantee good rankings, and an oversized photograph doesn't trigger a special image-size penalty.
One relevant measure is Largest Contentful Paint (LCP). It measures when the largest visible image or text block appears. On many service pages, that's the main photograph near the top.
A good LCP is 2.5 seconds or less, assessed at the 75th percentile of visits, separately for mobile and desktop. Image weight can affect it, but so can slow hosting, delayed image discovery and other page resources.
Don't turn this into “smaller pictures equal more customers”. Faster loading removes an obstacle. Your offer, content and credibility still have to do the selling.
Measure the images visitors actually download
Start your image file size SEO checks with a page that matters commercially: your main service page, a popular product or the landing page receiving paid traffic. Don't spend the afternoon shaving kilobytes off an obscure blog nobody visits.
Run that URL through PageSpeed Insights. Check the mobile results, the reported LCP element and any image-related recommendations. Where real-user data is available, distinguish it from the simulated test results.
Then check the actual downloads in your browser:
- Open the Network panel: In Chrome, open Developer Tools, select Network and filter the requests to images.
- Reload without cached files: Disable the cache while Developer Tools is open, then reload so previous downloads don't hide the problem.
- Inspect the biggest requests: Check the transferred sizes, file types and requested image URLs. Compare the image dimensions with how large it appears on the page.
Your media library isn't the final authority. A plugin might serve a smaller WebP version, or your page builder might request the enormous original despite smaller alternatives being available.
If image downloads look reasonable but the page remains slow, the bottleneck may be elsewhere. Our technical SEO service looks beyond individual files to the technical issues affecting how your website performs and can be found.
Compress images without turning your work into mush
Good image file size SEO preserves the detail people need to judge your business. A builder's project photograph should show the finish. A product photograph should show the material. If compression destroys that evidence, you've overdone it.
Start with a copy of the original. Keep the full-quality source somewhere safe rather than repeatedly overwriting it with increasingly compressed versions.
A sensible export process is:
- Crop for the intended position: Remove areas that won't appear in the finished layout.
- Resize to an appropriate resolution: Don't export thousands of unnecessary pixels.
- Choose a suitable format: WebP or AVIF can work well for photographs, depending on your website's support and delivery setup.
- Adjust compression and compare: Inspect the result at the size customers will actually see, particularly around text, faces and fine detail.
Tools such as Squoosh let you compare exports before committing. Your CMS or image plugin may also handle conversion and compression.
Format choice matters, but this isn't another format comparison. Our guide to WebP, JPEG and PNG covers that decision separately.
For illustration, replacing a 4 MB upload with a good-looking 250 KB delivered image cuts that image's weight by about 94%. That's useful. Reducing it further until your craftsmanship looks like porridge isn't.
Serve smaller versions to mobile visitors
Responsive delivery is where image file size SEO stops being an upload task and becomes a website task. One carefully compressed desktop image isn't necessarily the best download for a small phone screen.
Modern websites can provide several versions through srcset. The accompanying sizes information tells the browser how much layout space the image is expected to occupy, helping it choose an appropriate file.
You don't need to write this code yourself. You do need to know whether your website is using it properly.
For example, a photograph might have 480-, 960- and 1,600-pixel-wide versions. A visitor's browser can choose based on the layout, screen density and available candidates. The smallest version isn't always the correct choice, but neither is the largest.
Poor configuration can undermine the whole setup. If the website tells the browser an image fills the entire screen when it actually sits in a narrow column, the browser may select more pixels than necessary.
Check a real phone as well as your desktop preview. Confirm that important details remain visible and inspect which file is requested. A page that looks mobile-friendly can still download desktop-sized assets. That's the bit a visual website review can easily miss.
Load the right images at the right time
An image halfway down a long page usually doesn't need to download before the visitor has seen your opening content. Lazy loading lets suitable off-screen images wait until they're approaching the visible area.
Your main above-the-fold image is different. If it's responsible for LCP, delaying it with lazy loading can make the page feel slower, even when the file itself is reasonably small.
Google's guidance on optimising LCP explains why early discovery and appropriate loading priority matter. In practice, your important opening image should be available promptly, not hidden behind unnecessary scripts or delayed by a blanket loading setting.
Don't give every photograph high priority. If everything is urgent, you've told the browser nothing useful.
Include image width and height information, or otherwise reserve the correct space in the layout. This helps prevent text and buttons jumping about as photographs appear. That concerns layout stability, not file compression, but customers experience both problems together.
For image file size SEO, the aim is a light, promptly available main image and sensible loading for everything below it. A page with less total downloading can still perform badly if it delays the one photograph the visitor needs first.
Stop your CMS quietly undoing the work
WordPress usually creates multiple image sizes when you upload a photograph. That doesn't guarantee your theme or page builder uses the right one.
A block may be set to “Full size”. A gallery may request original files. A background image may bypass the responsive behaviour available to a normal image element.
Check these common problems:
- Oversized selections: Page blocks use the original upload rather than an appropriately sized variant.
- Conflicting optimisation tools: Several plugins or services process images, making it harder to identify what visitors actually receive.
- Unnecessary gallery downloads: Full-resolution images load immediately, even though visitors haven't opened the gallery or zoom view.
Before bulk processing a library, take a backup and test representative pages. Check product galleries, banners and mobile layouts, not just one convenient photograph on the homepage.
After changes, clear the relevant caches and test again. Otherwise, you may be measuring old files while wondering why nothing has improved.
Our WordPress SEO service is relevant when the problem sits in how the website is configured rather than in the photograph itself. With image file size SEO, a decent export is only half the job: the site still has to serve it correctly.
Fix the worst pages first, then prove the difference
You don't need to rebuild the entire image library this week. Start where a faster page could help someone buy, enquire or book.
Prioritise pages with large visible photographs, heavy galleries or obvious delays on mobile. If your main service page downloads a 6 MB banner, deal with that before debating whether a tiny icon could be two kilobytes smaller.
Record a baseline before changing anything. Note the delivered image sizes, the main performance issues and what the page looks like on a phone. Then optimise one representative page and compare it under similar testing conditions.
Run more than one performance test. Simulated results vary, so a single higher score isn't proof of a permanent improvement. Where real-user data is available, it takes time for changes to be reflected in the reporting window.
Keep checking business outcomes too. Faster pages are useful, but they don't repair a missing phone number, weak product information or a contact form that doesn't bloody work.
The sensible endpoint for image file size SEO is straightforward: appropriate dimensions, manageable downloads, clear photographs and no unnecessary loading delays. Once those are in place, move on to the next thing standing between your website and a customer.
Frequently Asked Questions
Does Google have a maximum image file size for SEO? Google doesn't publish a universal maximum file size that determines whether an ordinary website image ranks well. Large files can contribute to slow loading, which affects usability and can affect Core Web Vitals. Judge the delivered image by its purpose, visible quality and effect on the page, rather than an invented Google limit.
Is 100 KB the best size for every website image? No. Around 100 KB can be a useful target for an ordinary content photograph, but a small thumbnail may need much less and a detailed hero image may need more. Several 100 KB images also add up. Check the whole page and don't sacrifice important visual detail just to hit one number.
Should I resize images before uploading them to WordPress? Usually, yes, if your originals are far larger than the website needs. Keep the originals separately, then upload sensibly sized copies. WordPress can generate smaller variants, but your theme or page builder must request them correctly. Resizing first reduces unnecessary bulk without replacing the need to check responsive image delivery.
Will compressing images improve my Google rankings? It can improve loading performance when oversized images are a genuine bottleneck. That supports user experience and may improve relevant Core Web Vitals, but higher rankings aren't guaranteed. Image file size SEO is supporting work, not a replacement for relevant pages, useful content or a business people have reason to trust.
Should every image use lazy loading? No. Images below the initial visible area are often suitable for lazy loading. Your main above-the-fold image generally shouldn't be delayed, especially if it's the page's LCP element. Check how the page actually loads rather than applying the same setting to everything. Important opening content should appear promptly.
