• Resolved lawpress

    (@lawpress)


    I spoke with Chrome support and they’ve said the reason my png’s look worse on Chrome-based browsers/Opera than on Firefox, Safari, and Edge is because WordPress is serving my site from https://i1.wp.com.

    When a browser requests data from a server, it will send an HTTP “accept” header, telling the server what format this browser supports.

    For Chrome, it sends this:

    text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8

    The WordPress server can see image/webp is explicitly stated as being supported, so WordPress compresses the image to webp and sends that to Chrome instead.

    The problem is in my instance WordPress seems to be overly compressing my png to a point where there is a dramatic quality loss when my page is viewed in a browser that isn’t doing this.Microsoft Edge and Firefox don’t support webp (and also not specified in HTTP “accept” header) which is why my image is looking better in those browsers.

    Is there any way I can prevent this?/make the data request send less compressed webp file? I’ve been told this is a server-side fix.

    • This topic was modified 7 years, 5 months ago by lawpress.
    • This topic was modified 7 years, 5 months ago by lawpress.
    • This topic was modified 7 years, 5 months ago by lawpress.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Looking at the characters at the end of your file extension, there is a plugin interfering with your images and I assume it’s Jetpack. Try deactivating Jetpack to see whether that caused the problem.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    @lawpress, By the way we don’t allow URL shorteners like the one you’ve posted in your opening thread. If you’re not comfortable with the URL being public then I suggest removing it before you run out of time. You cannot edit a post after 60 minutes of publishing it here.

    Thread Starter lawpress

    (@lawpress)

    Thanks

    Thread Starter lawpress

    (@lawpress)

    @anevins thanks for your help. Had to turn off proton in jetpack. Everything fixed now

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WebP Compression in Chrome’ is closed to new replies.