Wordpress Installing WebP Express Wordpress Plugin on Centmin Mod Nginx

No I literally mean there's a new 'Tests' module inside the plugin configuration: https://imgur.com/tzmWlEy

---

I know I only need one of the libraries to work, but the tests are failing.

 

if using webp express still need image optimize plugin or not ?
because in webp expresss already has feature reduce image quality

 

1. are safe removing original .jpg or .png after converted to .webp ?

2. and how i can fix multiple vary ?
vary Accept-Encoding ( how to remove this default vary )
vary Accept

3. if i using add_header X-Content-Type-Options "nosniff" from server { will apply to all type file css, js, html, etc? or i still need uncomment in /usr/local/nginx/conf/staticfiles-hsts.conf

 

Okay so i followed the guide and everything is working properly. Screenshot

I wanted to ask why is the original image loaded in JPG or PNG

Sorry i still haven't properly studied this, i know we need original files for unsupported browsers.

But in supported browsers it loads all the images originally when i inspect element.

 

@eva2000
WebP express is functioning great for me overall with your config as per page 1 of this thread.
Just wondering if anything can be done about the various errors/warnings that crop up in the plugins live tests.

None of these actually stop me using the plugin as the bulk convertor catches anything historic (and works fine with your whitelist exception). and the convert on upload catches anything new.

But I'm guessing some might get missed with updates to theme images (and forgetting to re-run a bulk conversion) so it would be nice to have the plugins fallbacks work.

I'm guessing some additional whitelist rules would be needed for the on demand and realizor scripts per their recommended nginx config (as per below).

Any thoughts on this?

Code:

# WebP Express rules
# --------------------
location ~* ^/?wp-content/.*\.(png|jpe?g)$ {
  add_header Vary Accept;
  expires 365d;
  if ($http_accept !~* "webp"){
    break;
  }
  try_files
    /wp-content/webp-express/webp-images/doc-root/$uri.webp
    $uri.webp
    /wp-content/plugins/webp-express/wod/webp-on-demand.php?xsource=x$request_filename&wp-content=wp-content
    ;
}

# Route requests for non-existing webps to the converter
location ~* ^/?wp-content/.*\.(png|jpe?g)\.webp$ {
    try_files
      $uri
      /wp-content/plugins/webp-express/wod/webp-realizer.php?xdestination=x$request_filename&wp-content=wp-content
      ;
}
# ------------------- (WebP Express rules ends here)

e.g.





Redirection error


Realizer error

 

On my end the tests always end up failing, despite the plugin working correctly. Try checking if it's working despite the tests.

 

Hi

In this version i'm currently using it has more options, in particularly
You need to change Destination structure to: image root.
Otherwise it won't work, as you mentioned both images need to be on the same folder.

Destination structure:

This setting determines how the converted files are structured within the folder that WebP Express uses for storing webp images (from here on called "the cache root")

"document root"
When "document root" is selected, the webp images will be stored in:
[cache root]/doc-root/[relative path of source image, from document root].

"image roots"
A Wordpress site has images stored in different locations. Uploaded files are for example stored in the uploads folder, which is usually - but not always - located in the "wp-content" folder. I call the uploads folder an "image root". Other roots are: "themes", "plugins", "wp-content" and "index". When the "image roots" setting is selected, the webp files are stored in a structure that mirrors the relative path of the source image within its image root. For "uploads", that location is:
[cache root]/uploads/[relative path of source image, from uploads root].
More generally we have:
[cache root]/[image root]/[relative path of source image, from its image root].

Which option is best?
Well, in most cases it does not matter. However, there are hosts out there that have set the document root up incorrectly, so I would generally recommend "Image roots". On Nginx, I however recommend "Document root", as it requires fewer rewrite rules.​

 

Hello @eva2000 I'm struggling to have my WebP images cached.

I've followed your guide on Wordpress Cache Enabler Advanced Full Page Caching Guide - Centmin Mod Blog to setup with Cloudflare (although I have in development mode, I have set to respect expires header from the origin)

Firefox shows as having a expires header on my WebP images for 30d, but WebPageTest claims there's none, and I tend to believe more on tools these days WebPageTest do you have any insights on this? Also, here's my nginx -T output #include /usr/local/nginx/conf/errorpage.conf; include /usr/local/nginx/con - Pastebin.com

Also, my WOFF2 fonts from Use Any Font plugin that's on /wp-content/uploads/useanyfont/ have no expires header, and I imagine that I've done something wrong because I could swear it should have a cache control header on /uploads/ folder

Anyways, thank you