Introduction
You switched your website to WebP, expecting a speed boost, and PageSpeed Insights still dings you for heavy images. WebP is more efficient than JPG, but simply serving WebP is not the whole optimization story. If your WebP files are exported at maximum quality from Photoshop or straight off a camera, they are often larger than they need to be for web display, and that extra weight shows up directly in your load times and your Core Web Vitals scores. The good news is you can optimize WebP images further without wrecking the visual quality, and the gains can be dramatic. In this guide we cover how to squeeze your WebP images for faster page loads and better Core Web Vitals scores. We also cover how to batch process a whole site so every image gets the same treatment without manual one-by-one work.
Why This Happens
WebP's compression is efficient, but it is tuned for quality by default. Most image editors export WebP at quality 90 or higher, which preserves fine detail but produces files that are still heavy for web use. A typical hero image exported at quality 90 can hit 500 KB to 1 MB, and a product gallery with 20 images can total several megabytes, crushing load times on mobile connections. Page speed matters because Google uses Core Web Vitals as a ranking factor, and shoppers bounce from slow sites. The two levers you have are quality and dimensions. Dropping quality from 90 to 70 typically shrinks files 50 to 70 percent with no visible difference on screens. Resizing images to match their display dimensions, instead of serving a 4000-pixel photo in a 600-pixel slot, cuts file size dramatically. Most sites leave both levers untouched, which is why WebP alone does not guarantee fast pages.
3 Solutions
Solution 1: Batch compress and resize in one pass. Run your WebP images through a batch compress tool, set quality to around 70, and resize to display dimensions. Files shrink 60 to 80 percent with no visible loss on screen, and your whole site gets faster in one batch.
Solution 2: Use a CDN with automatic optimization. Cloudflare, Cloudinary, and Imgix can auto-compress and resize WebP on the fly based on the visitor device. This is zero manual work after setup and gives every visitor the right size for their screen.
Solution 3: Re-export from your editor at lower quality. In Photoshop or Figma, set WebP export quality to 60 to 70 instead of 90. This gives you smaller files at the source, so every future export is already optimized with no extra step.
Step-by-Step Guide
For the most control, use a browser-based compress tool. Open your browser and load the batch compress page. Drag your WebP images onto the upload area, you can drop an entire folder at once. Set the quality slider to around 70 percent. This is the sweet spot where file size drops sharply but images stay sharp on phone and laptop screens. If the tool offers a resize option, set the longest edge to your display size. For hero images, 1920 pixels wide is plenty. For product cards, 800 to 1200 pixels works. For thumbnails, 400 pixels is enough. Click Compress and let it process. For a batch of 50 images this usually takes a minute or two. Download the results, replace the originals on your site, and re-test in PageSpeed Insights. You should see a noticeable jump in your image scores and your Largest Contentful Paint metric. Always keep the original full-resolution files archived in case you need to re-export at a different size later.
Pros and Cons
Optimizing WebP images cuts page weight dramatically, improves Core Web Vitals, and boosts SEO and conversion rates. The tradeoff is the time spent processing batches and the risk of over-compressing. Drop quality too far and fine details like fabric texture, text on graphics, and smooth gradients start to show artifacts. Resizing is safer because it preserves quality within the new dimensions, but it caps how much visitors can zoom. For most websites, a quality 70 WebP at display dimensions is the ideal balance: small, sharp, and fast. CDNs are the lowest-effort option if you want ongoing optimization without manual batches, but they add cost. For most site owners, a monthly batch compress pass plus a CDN for delivery hits the sweet spot. It is also worth re-running the optimization pass whenever you add a batch of new images to your site, since new uploads from your team or your CMS will arrive at full quality and drag your scores back down. A simple routine is to export new images to a watch folder, run them through the compress tool before uploading, and only ever publish optimized files. That habit keeps your page speed scores stable over time instead of slowly degrading as fresh content piles on. Pair that with periodic checks in PageSpeed Insights, ideally monthly, and you catch weight creep before it hurts your rankings. Optimization is not a one-time task, it is an ongoing habit that pays off in faster pages, better SEO, and higher conversion rates.