Huge images, slow site
Your homepage weighs more than the software that flew Apollo.
Nine slow sites out of ten share one diagnosis: images uploaded straight from a phone or a designer's export — three, six, twelve megabytes each — shipped to every visitor at full weight. It's the most common performance disease on the web, and the most completely curable.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
A modern phone photo is a print-quality file: 4000+ pixels wide, several megabytes. Your visitor's screen slot for it might be 800 pixels and deserve 80 kilobytes — a fortyfold difference paid on every image, every visit, every cellular connection. Multiply by a gallery and the 'fast host' you're paying for is irrelevant: the site is slow at the delivery layer, hauling freight nobody can see.
The cure has four gears, and real optimization uses all of them. Right-sizing: serving dimensions that match display, not the camera. Modern formats: WebP/AVIF carrying the same visual quality at a fraction of JPEG's weight. Honest compression: tuned to be invisible — the 'compressed look' owners fear comes from crude settings, not from compression itself. And delivery: lazy loading below the fold plus CDN serving. Done together, a 15MB page routinely becomes a 1.5MB page that looks pixel-identical — which is why this fix has the most dramatic before/after numbers in the shop.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
Camera-roll uploads
Full-resolution phone photos placed straight into pages — the innocent habit behind most multi-megabyte sites.
Themes ignoring responsive sizes
WordPress generates smaller copies; plenty of themes ship the original anyway, or size images with CSS while sending full freight.
Decorative backgrounds at print weight
The hero background nobody looks at closely, costing more than the rest of the page combined.
No modern-format pipeline
Everything served as decade-old JPEG/PNG when WebP/AVIF would halve it — free savings, unclaimed.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Weigh your homepage
PageSpeed Insights or the browser's Network tab, look at total transfer. Over ~3MB, images are near-certainly the anchor; over 8MB, they're the whole story.
- 2
Find your five heaviest images
Network tab, sort by size. The top five usually carry half the total — and name exactly where the first surgery goes.
- 3
Check what format you're serving
Same tab: .jpg and .png everywhere means the modern-format gear was never engaged. That alone is often a 40–60% cut.
Stop and call when…
- The fix needs a pipeline, not a one-time crunch — new uploads must optimize automatically or the disease returns
- Existing libraries need bulk conversion with originals preserved — a job with backups and rollback, not a plugin's 'optimize all' button on faith
- Quality is sacred (photographers, portfolios) — tuning compression per image class is craft work
From there it’s our job: same-day look, flat quote, and the $679 flat repair covers most cases of exactly this.
Site Speed Tune-Up — buy it now, skip the hunt.
Images, scripts, and caching tuned — measurably faster inside 48 hours of starting.
Covers one site: image optimization, script cleanup, caching configuration, and a before/after PageSpeed report. Platform-level rebuilds quoted separately if the site needs more.
Questions we hear a lot.
Will compression make my photos look cheap?
Done right, you cannot see it — that's the actual test we use: side-by-side at real display sizes. The 'crunchy' look comes from crude bulk tools at aggressive settings. Professional optimization targets the sweet spot where files shrink 70–90% and eyes detect nothing, and keeps originals untouched as insurance.
My host is fast — why is the site still slow?
Because hosting speed and page weight are different bottlenecks. A fast server hands off a 12MB page quickly; the visitor's connection still has to carry 12MB, and on a phone connection that's seconds of white screen. Image weight is a delivery problem — it follows your visitors everywhere, whatever you pay the host.
What does the $679 tune-up include for images?
The full four gears: bulk conversion to modern formats with originals kept, right-sizing against your actual templates, tuned compression, lazy loading, CDN delivery where the stack supports it — and an automatic pipeline so tomorrow's uploads get the same treatment. Measured with before/after PageSpeed reports, per our standard.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Same site, a tenth the weight. Measured.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.