Section 1
Why images are the biggest lever
Images dominate page weight (60-70% is typical) because photos and graphics are simply large files compared to text and code (1), so they're usually the largest single contributor to how long your page takes to load, and the largest opportunity to speed it up. The reason image optimization is such a good win is the combination: high impact (they're the heaviest thing) and high accessibility (the fixes are mostly simple and non-technical). Unoptimized images, uploaded straight from a camera or phone at full resolution, in inefficient formats, bloat your pages needlessly, and the fixes (right-sizing, compressing, modern formats, lazy loading) recover a lot of speed for little effort. So for a non-technical owner looking for the biggest performance win they can actually execute themselves, images are almost always the answer. The principle: images are usually 60-70% of page weight, making them the biggest and most accessible performance lever for a non-technical owner. (This applies the performance research cited across this library.) Your slowest pages are usually slow because of their images, the heaviest thing you put on a page, often more than half its total weight. That's bad news and good news: bad because unoptimized images are quietly dragging your speed down, good because fixing them is mostly simple, free, and entirely doable without a developer. The biggest performance win on your site is probably sitting in your image folder.
Section 2
The non-technical image fixes
1, Right-size your images. Don't upload a 4000-pixel-wide camera image to display at 800 pixels, resize images to roughly the size they'll actually display. This alone often cuts image weight dramatically. (Free tools and most site builders can resize.) 2, Compress them. Run images through a free compression tool, which reduces file size substantially with little visible quality loss. Compressing is one of the easiest, highest-return image fixes. 3, Use modern formats. Modern image formats (like WebP) are significantly smaller than older ones (JPEG/PNG) at similar quality. Many tools and site builders can convert or serve modern formats, use them where you can. 4, Lazy-load below-the-fold images. Lazy loading means images further down the page load only as the visitor scrolls to them, so they don't slow the initial load. Many platforms enable this with a setting or do it automatically. 5, Reserve space to prevent shift. Ensure images have defined dimensions so the page doesn't jump around as they load (the layout-stability problem). Many builders handle this; check that yours does. Most of these are settings or free-tool steps, not code, which is what makes images the win a non-technical owner can actually capture. (These are the commonly cited image-optimization practices.)
Section 3
The non-technical image fixes, in one view
The takeaway: images are usually 60-70% of your page weight (1), making them the single biggest lever on your site's speed, and because the fixes are mostly non-technical (right-sizing, compressing, modern formats, lazy loading, reserving space), they're the highest-impact performance win a non-technical owner can actually execute themselves. Unoptimized images uploaded at full resolution in inefficient formats quietly drag your pages down; the simple fixes recover a lot of speed for little effort, using free tools and platform settings rather than code. If you want the biggest performance improvement you can make on your own this week, it's almost certainly sitting in your image folder, start by right-sizing and compressing the images on your slowest, most important pages. (The non-technical fix guide synthesizes the performance research established across this library.)
Section 4
Execute This With AI
Step 1, Inputs. Note your platform, your slowest/most important pages, and how you currently add images (straight from camera/phone?). Step 2, Run the prompt: You are an image-optimization coach for a NON-TECHNICAL owner. Images are usually 60-70% of page weight, the biggest, most accessible speed lever. Non-technical fixes: right-size to display size, compress (free tools), use modern formats (WebP), lazy-load below-fold, reserve space to prevent shift. Mostly settings and free tools, not code. My platform: [X]. My slowest/most important pages: [LIST]. How I add images: [DESCRIBE]. Do four things: 1. Give me step-by-step image fixes for MY platform (where to resize, compress, set formats, lazy-load). 2. Tell me which fix will likely recover the most speed for my pages first. 3. Recommend free tools for resizing and compressing. 4. Tell me how to check my image weight before/after so I can see the win. Make this the biggest performance win I can do myself this week. Step 3, The before/after check. Measure your page weight (or load time) before and after optimizing the images on one important page, "how much faster did right-sizing and compressing make it?" Tools and expected output. Any frontier chat model, plus free image resize/compress tools and a page-weight/speed checker. Expect platform-specific steps, the highest-return fix first, tool recommendations, and a before/after method. The QA discipline: measure page weight or load time before and after so the improvement is verified, not assumed, and check that images still look good after compression (the goal is smaller files at acceptable quality, not degraded images). The model coaches the fixes; the before/after measurement proves the win. Images are usually 60-70% of your page weight, making them the single biggest lever on your site's speed, and because the fixes are mostly non-technical, they're the highest-impact performance win a non-technical owner can execute themselves. Right-size your images to display size, compress them with a free tool, use modern formats like WebP, lazy-load below-the-fold images, and reserve space so the page doesn't shift, mostly settings and free tools, not code. Unoptimized images quietly drag your pages down; the simple fixes recover a lot of speed for little effort. The biggest performance improvement you can make on your own is almost certainly sitting in your image folder, start with the images on your slowest, most important pages.
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), [How to Read a PageSpeed Insights Report Without Being a Developer](/blog/how-to-read-a-pagespeed-insights-report-without-being-a-developer), [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), [What Is Conversion-First Web Design? A Plain-English Guide for Founders](/blog/what-is-conversion-first-web-design-a-plain-english-guide-for-founders).