In Neova Runs from the crawl itself: nothing to set up.
Rule last reviewed October 17, 2026
Large image files slow pages: compress them, size them to how they are displayed and use modern formats. The 100KB line is a tool default, not an engine rule; Lighthouse judges images by potential savings, not absolute size.
How Neova Finds It
Neova runs a speed test on a sample of each kind of page.
Why It Matters
Images are often the largest part of page weight, and a heavy LCP image slows Largest Contentful Paint, a Core Web Vital Google asks sites to get to good. Mobile users pay for the bytes.
The Ticket It Writes
PE-065 · Transferred Image Size Is Over 100KB
Expected Result: All in-scope pages pass 'Transferred image size is over 100KB'.
How to Check the Fix: 1. Run the check again in Neova 2. Spot-check sample URLs across affected templates 3. Record the re-check date and period label next to the baseline 4. Known limits of this check: A well compressed 150KB hero image can be fine while a 60KB image shown at 50 pixels is waste, so size alone decides nothing. Google also says sharp images appeal more in result thumbnails, so do not crush key images. Sitebulb measures transferred (compressed) size. Same check as PE-066; overlaps PE-011 and PE-020. 5. Sources: https://developer.chrome.com/docs/performance/insights/image-delivery | https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight | https://developers.google.com/search/docs/appearance/google-images
Neova writes this ticket for every affected page group and sends it to Jira, Linear, Asana and the rest, after you approve it.