Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter patrikmuse

    (@patrikmuse)

    I think I figured out the problem: it happens when the image is converted using ImageMagick. If I delete the converted image and use GD instead, the issue is resolved. Why does that happen?

    CompressX version0.9.26
    WordPress version6.7.2
    PHP version8.1.32
    GD extensionThe GD extension has been properly installed.
    GD Versionbundled (2.1.0 compatible)
    GD WebP Supporttrue
    GD AVIF Supporttrue
    Imagick extensionThe imagick extension has been properly installed.Imagick
    Version1809, ImageMagick 7.1.1-45 Q16-HDRI x86_64 22722 https://imagemagick.orgImagick
    WebP Supporttrue
    Imagick AVIF Supporttrue

    • This reply was modified 1 year, 2 months ago by patrikmuse.
    • This reply was modified 1 year, 2 months ago by patrikmuse.
    • This reply was modified 1 year, 2 months ago by patrikmuse.
    Plugin Support tonyrobins

    (@tonyrobins)

    Hello @patrikmuse

    We noticed that for example, this image is 141KB in Chrome, with a response header of last-modified:Mon, 07 Apr 2025 11:10:30 GMT. In our Firefox, it is 259KB, with a response header of last-modified: Sun, 30 Mar 2025 15:47:10 GMT. And it is indeed cached.

    So, could it be that different versions of this image are cached in different browsers, Firefox has an old version, and Chrome has a new version? For example, different versions of cache are generated for different Vary: User-Agents?

    Do you use CDN or cache plugins on the site? If so, you can also try to clear cache and see if that helps.

    All the best,

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Firefox support’ is closed to new replies.