Section 1
Why images dominate page weight
Understand the problem and the fix is obvious. A modern service site is visually rich, hero images, team photos, portfolio shots, background images, icons. Each one is a file the visitor must download, and photographs are large files. When those files are uploaded straight from a camera or a stock site at full resolution, a single hero image can weigh more than the entire rest of the page combined. Multiply that across a gallery and a homepage, and images become the overwhelming majority of what makes your site slow, 60–70% of the weight (1), all of it downloading before the visitor can comfortably use the page. The reason this is the best problem to have is that images are also the easiest weight to remove without losing anything. A properly optimized image looks identical to the human eye while weighing a fraction as much. You're not cutting content or features; you're removing invisible bloat. That's why image optimization delivers the rare combination of large impact and low effort. Your slow website probably isn't a coding problem. It's a few enormous photographs that look exactly the same at a tenth of the file size. The biggest speed win on most service sites is also the one that requires the least technical skill to claim.
Section 2
The image optimization playbook
Five techniques, in order of impact-to-effort, that together can cut page weight dramatically. 1, Compress every image. The highest-return, lowest-effort move. Compression reduces file size while preserving visual quality, and most images can be compressed substantially with no perceptible difference. Free tools (TinyPNG, Squoosh, and built-in features in most modern site builders) do this in seconds. The move: run every image on your site through compression. This alone often delivers the bulk of the gain. 2, Use modern formats (WebP or AVIF). Older formats (JPEG, PNG) are far larger than modern ones. WebP and AVIF deliver the same visual quality at much smaller file sizes, and they're now widely supported. Most modern builders (Webflow, Framer, and others) can serve these automatically. The move: convert or serve images as WebP/AVIF rather than legacy JPEG/PNG. 3, Size images correctly (don't scale down in the browser). A common, costly mistake: uploading a 4000-pixel-wide image and letting the browser shrink it to display at 800 pixels. The visitor still downloads the full 4000-pixel file. The move: resize images to roughly the dimensions they'll actually display at before uploading them. A team photo shown at 400px wide should not be a 3000px file. 4, Lazy-load below-the-fold images. Lazy loading means images further down the page only load as the visitor scrolls toward them, rather than all at once on arrival. This speeds up the critical first load, the part that determines whether a visitor stays. The move: enable lazy loading (most builders have a setting or do it by default) for images below the fold. 5, Be ruthless about whether you need the image at all. The fastest image is the one you don't load. Decorative background images, redundant gallery shots, and "filler" stock photography add weight while adding little. The move: audit your images and remove the ones that don't earn their weight, and as the conversion and authenticity pieces argue, generic stock photography often hurts trust anyway, so cutting it is a double win.
Section 3
The playbook, in one view
Worked together, these five can reduce your page weight by up to 70% (1), which, given that images are 60–70% of the problem (1), can transform a slow site into a fast one. And because speed drives conversion and revenue, this unglamorous afternoon of compressing and resizing photos can produce a conversion lift worth far more than the time it took. It's the rare optimization that is simultaneously the most impactful, the easiest, and the cheapest, which is exactly why it should be the first thing a founder does about a slow site, before assuming the problem is something that requires a developer and a rebuild.
Section 4
Execute This With AI
Here is a workflow to plan your image optimization with any capable AI model. Step 1, Diagnose. Run your site through Google PageSpeed Insights and look for image-related opportunities ("properly size images," "serve images in next-gen formats," "efficiently encode images," "defer offscreen images"). List your heaviest pages and your biggest images. Step 2, Run the optimization prompt: You are a web-performance advisor helping a non-technical founder optimize images, the cause of 60–70% of page weight, fixable for up to a 70% weight reduction. Apply five techniques: compress, use WebP/AVIF, size correctly before upload, lazy-load below-fold, and remove unneeded images. My platform: [Webflow/Framer/WordPress/Squarespace/other]. My PageSpeed image opportunities: [PASTE the image-related items]. My biggest images / image-heavy pages: [DESCRIBE]. Do five things: 1. Tell me which of the five techniques will help most on MY platform, and how to do each one specifically (note built-in features my platform has). 2. Give me the exact free tools to compress and convert images. 3. Tell me the correct dimensions to resize my main images (hero, team, gallery) based on how they display. 4. Identify which images I could remove entirely (esp. generic stock). 5. Estimate the rough page-weight reduction I could achieve and what it means for speed. Be specific to my platform; keep it non-technical. Step 3, Re-measure. "After I optimize images, what should my PageSpeed scores show, and how do I confirm the images are now served compressed and in modern formats?" Tools and expected output. Google PageSpeed Insights (diagnosis), free compression tools (TinyPNG, Squoosh), your site builder's image settings, plus any frontier chat model. Expect platform-specific instructions, the right tools, correct dimensions, removal candidates, and a weight-reduction estimate. The QA discipline: verify the result by re-running PageSpeed and checking that the image opportunities have cleared, and confirm on a real phone that the optimized images still look sharp, since the goal is invisible weight reduction, not visibly degraded photos. The model plans the optimization; your eyes and the re-test confirm it worked. The most common cause of a slow service website is also the easiest to fix and the one founders are least likely to suspect: the images. They're 60–70% of your page weight, they're usually uploaded far larger than they need to be, and they can be cut by up to 70% with free tools in an afternoon, no developer, no rebuild, no loss of quality the eye can see. Before you assume your slow site needs an expensive technical overhaul, compress the photos. It's the biggest speed win available, hiding in plain sight, costing nothing but an hour of unglamorous work that converts directly into faster pages and more booked calls.
Section 5
Keep reading
Keep reading in the Performance & Core Web Vitals cluster and across the library: [Core Web Vitals in the INP Era: What Changed and Why It Matters](/blog/core-web-vitals-in-the-inp-era-what-changed-and-why-it-matters), [Images Are 60-70% of Your Page Weight: A Non-Technical Fix Guide](/blog/images-are-60-70-of-your-page-weight-a-non-technical-fix-guide), [The Performance Cost of Animation (and How to Keep Motion From Slowing the Sale)](/blog/the-performance-cost-of-animation-and-how-to-keep-motion-from-slowing-the-sale). Also relevant: [Speed-to-Lead: Why Page Speed and Reply Speed Are the Same Conversion Lever](/blog/speed-to-lead-why-page-speed-and-reply-speed-are-the-same-conversion-lever), [The Service-Business Website Priority Stack: What to Fix First When Everything Needs Work](/blog/the-service-business-website-priority-stack-what-to-fix-first-when-everything-needs-work), [Image and Media Optimization: The Cheapest Website Speed Win Available](/blog/image-media-optimization).