Images not optimized or converted WebP

When an image is not found in the cache, the original image is sent immediately to the visitor. But the image is optimized and converted to WebP in the background. Subsequent requests to the same image will deliver optimized and WebP images.

If your image is still not optimized or converted to WebP, check the "cf-polished" response header. It will give you more information like below:

  • not_compressed or not_needed: The image was fully optimized at the origin server, and no compression was applied.
  • webp_bigger: FlyingProxy attempted to convert to WebP, but the image was optimized at the origin server or was created using a low-quality setting. Because the WebP version does not exist, the response's status is set on the JPEG/PNG version.
  • cannot_optimize or internal_error: The input image is corrupted or incomplete at the origin server. Upload a new version of the image to the origin server.
  • vary_header_present: The origin web server has sent a Vary header with a value other than accept-encoding. If the origin web server is attempting to support WebP, disable WebP at the origin web server and let Polish perform the WebP conversion. Polish will still work if accept-encoding is the only header listed within the Vary header.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.