LiteSpeed

LiteSpeed Cache image optimisation: WebP/AVIF, lazy load and settings

Optimise WordPress images with LiteSpeed Cache: request QUIC.cloud optimisation, serve WebP or AVIF, keep originals, lazy-load safely and fix images that do not change.

IntermediateWordPress on LiteSpeed3 min read

Images are usually the heaviest part of a page. The LiteSpeed Cache plugin can compress your existing images, create modern WebP or AVIF versions and serve them automatically to browsers that support them, all without a separate image plugin. The heavy processing happens on QUIC.cloud servers, not on your hosting account.

Before you start

  • LiteSpeed Cache installed (see configuring LiteSpeed Cache).
  • Your site linked to QUIC.cloud with a domain key (see QUIC.cloud basics). The CDN is not required.
  • Enough disk space for optimised copies; WebP versions add files next to originals.

Configure image optimisation settings

  1. Go to LiteSpeed Cache → Image Optimization → Image Optimization Settings.
  2. Auto Request Cron: On, so new uploads are sent for optimisation automatically.
  3. Optimize Original Images: On.
  4. Remove Original Backups: Off until you are happy with the results; backups let you revert.
  5. Optimize Losslessly: Off for best savings, On if you need pixel-perfect photos.
  6. Preserve EXIF/XMP data: Off, unless you need camera metadata.
  7. Image WebP Replacement (or Next-Gen Image Format in newer versions): choose WebP or AVIF.
  8. Click Save Changes.

Optimise existing images

  1. Open LiteSpeed Cache → Image Optimization → Image Optimization Summary.
  2. Click Send Optimization Request. Images are sent in batches according to your QUIC.cloud quota.
  3. Click Pull Images if they are not pulled automatically. Progress shows how many are done.

Note: QUIC.cloud processes images in batches and has a free monthly quota. Large media libraries can take several days to finish; this is normal.

Lazy load images

In Page Optimization → Media Settings, turn on Lazy Load Images so off-screen images load only when scrolled into view. Then:

  • Add your logo and the main hero image to Lazy Load Image Excludes (or exclude the first images with VPI, viewport images), so the largest visible image loads right away and does not hurt Largest Contentful Paint.
  • Turn on Add Missing Sizes to reduce layout shift.

Check that WebP is served

  1. Open a page in Chrome, press F12 and go to Network → Img.
  2. Reload and look at the Type column: it should say webp or avif for optimised images.

Purge the page cache after enabling WebP replacement so cached pages pick it up.

Troubleshooting

Requests stay "pending"

The domain key is not approved or QUIC.cloud cannot reach the site. Check LiteSpeed Cache → General and allow the WordPress REST API in security plugins.

Images look too compressed

Turn on Optimize Losslessly, then use Restore Original (needs backups kept) and re-optimise.

Disk usage jumped

Optimised copies and backups take space. Once satisfied, use Remove Original Image Backups, and check the account quota (see monitoring disk usage).

Frequently asked questions

WebP or AVIF?

AVIF files are usually smaller, WebP is supported by more tools and processes faster. Both are supported by current browsers; WebP is the safe default.

Do I still need to resize images before upload?

Yes. Uploading 6000-pixel photos wastes space and processing. Resize to the largest size your theme displays, then let the plugin compress.

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.