WordPress Performance · Updated October 10, 2026
How to Fix “Core Web Vitals” Image Size Errors on WordPress
PageSpeed Insights may flag an image that is larger than its display size, has avoidable bytes, or delays the main content. That is a specific optimization opportunity—not a blanket Google penalty for using JPEG or PNG. Diagnose the flagged asset first, then choose the smallest change that preserves visual quality and layout.
Test a WEBP copy
Try the image that your audit identified, compare the output size and visual quality, and test it on a staging page before changing the live WordPress media. PulseTools converts one PNG or JPEG at a time into a WEBP copy in your browser.
Open Image to WEBP Converter1. Read the audit message before changing formats
Run the affected page through Google PageSpeed Insights and note the exact image URL and recommendation. “Properly size images,” “efficiently encode images,” and an LCP discovery or loading hint call for different fixes. Core Web Vitals measure user experience; changing every image to a next-gen format is not a universal requirement or ranking guarantee.
2. Serve dimensions close to the rendered size
If a 2400-pixel image appears in a 400-pixel content column, export or serve a version closer to the actual display dimensions, while accounting for high-density screens and zoom. In WordPress, check the image block, theme size, generated thumbnails, and responsive srcset output. Avoid manually replacing originals until the theme still selects the correct source across screen sizes.
3. Compare compression and formats carefully
WEBP or AVIF can reduce transfer size for some images, but results depend on the source and encoder. JPEG remains a practical fit for many photographs; PNG is useful for lossless graphics and transparency; SVG can suit simple vector artwork. Keep the original, compare at the actual display size, and verify transparency, sharp edges, color, and file dimensions.
PulseTools’ converter accepts PNG and JPEG input and exports WEBP. It creates a copy; it does not resize WordPress media or update your site automatically. Upload and test the output using your normal staging workflow.
4. Check loading behavior and layout stability
Do not lazy-load the likely Largest Contentful Paint image if that delays its discovery. Below-the-fold images can often be lazy-loaded. Reserve image width and height so content does not jump while files load, and inspect whether a plugin, theme, CDN, or WordPress core is serving duplicate or oversized versions.
5. Retest the same page
After deployment, rerun the same URL and compare the specific audit, image bytes, and page behavior. Lab measurements can vary between runs; use field data when available to understand real users. A smaller image may help if it was the bottleneck, but scripts, server response, fonts, and layout work can also affect Core Web Vitals.