Most small business owners blame slow websites on hosting, plugins or “too much code”. In practice, the heaviest thing on the average page is far more ordinary: photos. Product shots, hero banners, team pictures and blog headers quietly make up the largest single share of what a visitor has to download before your page feels ready.
That weight has a price. It drags down Core Web Vitals, it pushes impatient mobile visitors back to the search results, and it hands a speed advantage to competitors who simply resized their images. The good news is that image weight is also the cheapest performance problem to fix. You do not need a developer or a new website, only a better habit before you hit upload.
The web keeps getting heavier, and images lead the way
The median mobile home page now weighs about 2.6 MB, according to the HTTP Archive Web Almanac 2025. Back in July 2015 the same median page was just 845 KB. That is roughly a threefold increase in ten years, while mobile connections in many places did not get three times faster.
Images are the single biggest category in that total:
| Median home page (2025) | Total weight | Images | Image share |
| Mobile | 2,559 KB | 911 KB | about 36% |
| Desktop | 2,862 KB | 1,059 KB | about 37% |
The median hides the real problem. At the 90th percentile, pages load around 6.3 MB of images on mobile and 6.9 MB on desktop. Those are usually not huge media sites. Very often they are ordinary business pages where someone uploaded a 5 MB photo straight from a phone or camera and let the browser shrink it on screen.
Core Web Vitals: where images decide the score
Google measures page experience through three Core Web Vitals. The one images affect most is Largest Contentful Paint (LCP): the time until the biggest visible element on screen has loaded. Google asks for LCP within 2.5 seconds. Its documentation says good Core Web Vitals align with “what our core ranking systems seek to reward”.
Here is why that matters for image weight. According to the Web Almanac 2025 performance chapter, the LCP element is an image on 76% of mobile pages and 85% of desktop pages. In other words, on most websites the LCP score is mostly a question of how fast one photo arrives.
The same report shows how many sites still struggle:
- Only 62% of mobile pages reach a good LCP, compared with 74% on desktop.
- Only 48% of mobile websites pass all three Core Web Vitals.
- About 16% to 17% of pages still lazy load their LCP image, which delays the very element Google is timing.
- JPG remains the most common LCP image format at 57%, while WebP sits at 11% and AVIF below 1%.
To be fair, Core Web Vitals are not a magic ranking switch. A fast page with weak content will not outrank a slow page that answers the question better. But when two pages are similarly relevant, a slow hero image is an easy way to lose the tie, and the ranking effect is only half of the cost.
The conversion cost nobody sees in analytics
Rankings bring visitors to the door. Speed decides whether they walk in. Two widely cited studies show how quickly that decision is made.
In the Milliseconds Make Millions study by Deloitte and 55, commissioned by Google, a 0.1 second improvement in mobile site speed lifted retail conversion rates by 8.4%. Retail shoppers also spent 9.2% more, and travel sites saw booking rates improve by 10%.
Portent’s analysis of over 100 million page views found a steep drop for ecommerce sites as load time grew:
| Page load time | Average ecommerce conversion rate |
| 1 second | 3.05% |
| 2 seconds | 1.68% |
| 3 seconds | 1.12% |
| 4 seconds | 0.67% |
For B2B lead generation sites, pages that loaded in 1 second converted about three times better than pages that took 5 seconds.
The tricky part is that this loss is invisible. Your analytics shows the visitors who stayed, not the ones who gave up while a 4 MB banner was still loading over a weak mobile signal. You simply see a conversion rate that is lower than it should be and never learn why.
Why small businesses feel it most
Large brands have performance teams, image CDNs and build pipelines that resize every upload automatically. A local bakery, a boutique or a two person agency usually has none of that. The website runs on a page builder or a shared hosting plan, and the person adding content is the owner, late in the evening, uploading photos straight from a phone.
A modern phone camera saves photos around 4000 pixels wide, often 3 MB to 6 MB each. A typical content area on a website displays images at 800 to 1600 pixels wide. Every oversized upload makes the visitor download several times more data than the screen can show.
Small sites also have less margin for error. They compete for local and niche searches where the top results are often separated by small differences. They rely heavily on mobile traffic from Maps, social media and messaging apps. And they rarely have the budget to win back lost visitors with ads. Shaving a few seconds off a product page is one of the few SEO improvements that costs almost nothing.
Five fixes that cut image weight without hurting quality
You do not need to rebuild your website. Most of the gains come from what happens to a photo before it is uploaded.
- Resize before you upload. Match the image to the largest size it will actually be shown at. A full width hero rarely needs more than 1600 to 2000 pixels; a blog image or product thumbnail can often be 800 to 1200 pixels. Resizing a phone photo from 4000 pixels to 1600 pixels removes most of its weight on its own.
- Compress every image. For photos, a JPG or WebP quality setting around 70% to 80% is usually indistinguishable from the original on screen while being a fraction of the size. If you do not have editing software, a free image compressor in the browser lets you set the quality with a slider, compress several files in one go and see how many kilobytes you saved before you download.
- Choose a modern format. WebP files are typically much smaller than JPG at similar visual quality, and every major browser supports them. Keep PNG for logos, icons and graphics with sharp edges or transparency, not for photos.
- Never lazy load the main image. Lazy loading is great for images further down the page, but it slows down the hero image that Google uses to measure LCP. Load the first visible image normally, and if your platform allows it, mark it with fetchpriority=”high”.
- Set width and height. Declaring image dimensions lets the browser reserve space before the file arrives, which prevents layout shifts and protects your CLS score.
A 20 minute image audit for your website
You can find your heaviest problems in one sitting:
- Run your home page and your top product or service page through Google PageSpeed Insights and note the LCP time on mobile.
- Check which element is flagged as the LCP element. If it is an image, start there.
- Open the Core Web Vitals report in Google Search Console to see which groups of URLs are marked as poor or needing improvement.
- Look for any image over 300 KB on a regular page and resize or compress it.
- Replace large PNG photos with JPG or WebP versions.
- Make sure the hero image is not lazy loaded.
- Retest after a few days of real visitor data and compare the numbers.
Repeat the audit every few months, or every time you redesign a page or upload a new batch of product photos.
Lighter pages, better business
Page weight sounds like a technical metric, but for a small business it translates directly into rankings, leads and sales. Images make up more than a third of the average page and decide the LCP score on most websites, so they are the first place to look.
The fix is not glamorous. Resize, compress, pick the right format and let the main image load first. Build that into your routine every time you publish, and your website will feel faster to visitors and to Google without spending a cent on new hosting.
