Small-business homepage image weight
Origin images from 19,522 small-business homepages re-encoded in PicPerf's analyzer: median payload 0.88 MB, median remaining 40.5%, median 16 images. Untreated census, not field RUM.
By Alex MacArthur, builder of PicPerf · Published
Headline (2026-09-07): across 19,522 unique small-business homepages, the median page carried 0.88 MB of origin images. After this encode recipe, the median remaining size was 40.5% of the original bytes. The median page loaded 16 images. These are origin images re-encoded in PicPerf's analyzer. Not field RUM, and not a product before-and-after.
Image weight at a glance
One row per unique URL, latest analysis kept. PicPerf page image analyses (crawl + encode). Latest analysis per unique URL.
| Metric | n | p25 | Median | p75 |
|---|---|---|---|---|
| Image payload (MB) | 19,522 | 0.33 | 0.88 | 2.2 |
| Remaining bytes (MB) | 19,522 | 0.14 | 0.31 | 0.61 |
| Remaining (% of original) | 19,522 | 22.5% | 40.5% | 60.3% |
| Image count | 19,522 | 8 | 16 | 26 |
Remaining-size buckets
Share of URLs by remaining bytes after this encode recipe, plus the share of pages carrying 1 MB or more of origin images.
| Remaining | URLs | Share |
|---|---|---|
| < 50% | 12,154 | 62.3% |
| 50–89% | 6,425 | 32.9% |
| ≥ 90% | 943 | 4.8% |
| ≥ 1 MB original payload | 9,032 | 46.3% |
Outreach vs public analyzer
Some URLs come from PicPerf's outreach pipeline; the rest come from people who ran the public image analyzer. Promo jobs cap at 15 images per analysis.
| Source | n | Median remaining | Median payload | Median images |
|---|---|---|---|---|
| Outreach (promo) | 4,969 | 38.7% | 1.01 MB | 16 |
| Public analyzer | 14,553 | 41% | 0.84 MB | 16 |
By original format
Every analyzed image by the content type served on the origin. Median original size is per image; median remaining is per image after this encode recipe.
| Format | Images | Share | Median size | Median remaining |
|---|---|---|---|---|
| PNG | 115,010 | 29.8% | 14.6 KB | 41% |
| JPEG | 96,199 | 24.9% | 56.8 KB | 47.1% |
| WEBP | 82,110 | 21.3% | 27.3 KB | 79.3% |
| SVG | 54,127 | 14% | 2.8 KB | 98.3% |
| AVIF | 22,848 | 5.9% | 5.1 KB | 59.2% |
| OTHER | 10,945 | 2.8% | 25.9 KB | 60.3% |
| GIF | 4,343 | 1.1% | 8.6 KB | 62.2% |
Methodology
- Each analysis crawls a homepage's images and re-encodes them with PicPerf's image pipeline (modern output format when smaller, optional downscale to the analysis width).
- Duplicate URLs keep the latest analysis only.
- Outreach (promo) jobs cap at 15 images per analysis; the public analyzer does not.
- The encode recipe includes an optional resize (promo jobs often cap width at 1100px), so remaining bytes reflect resizing plus re-encoding, not the encoder alone.
- The encoder was not constant over 2024–2026: the output format at analysis time varied (WebP, AVIF, and JXL historically).
- This dataset includes no per-site URL list.
Machine-readable tables: JSON and CSV. Page-speed lab baselines for a different homepage sample are a separate dataset: small-business homepage lab performance.
What this does not claim
- Not the whole web. This is a convenience sample of sites PicPerf analyzed. It is complementary to HTTP Archive, not a replacement.
- Not field data. These are re-encoded origin bytes, not CrUX or RUM.
- Not the HTTP Archive byte index. Different sample, different recipe.
- Not live PicPerf CDN traffic. Nothing here measures production
image_requests. - Not Turbulence HTML rewrites. This dataset belongs to PicPerf Images, not the full-site product. Paired before-and-after product results live at Turbulence performance research.
- Remaining ratio is not “Lighthouse wastedBytes.” Lighthouse image audits estimate per-page waste under their own assumptions; this is a straight re-encode census.
Frequently Asked Questions
Related Guides
- PicPerf Turbulence performance research Lab before-and-after results from about 500 public sites run through Turbulence.
- Small-business homepage lab performance Untreated PageSpeed Insights lab baselines from 12,536 homepages: median LCP 9.2s.
- Best frontend performance tools The stack that makes a site faster, finds why it is slow, and measures real users.
- Best image CDN How to pick an image CDN: drop-in prefix, full media suite, Cloudflare add-on, or cheap Optimizer.
Prefix image URLs or upload originals. AVIF/WebP when smaller, resizing, and a 1-year CDN cache.
Start a 14-day Image Trial