How to tell if Statically compression & webp is working?

1. If the images are served via Statically, the URL will start with “https://cdn.statically.io/”

2. Having ‘.jpg’ extension doesn’t mean the image will have a jpg format. Open the network panel in your browser, click on the image and check the response header>content-type. It will show “image/webp”

• This reply was modified 4 years, 9 months ago by Gijo Varghese.

Hi Gijo,

Thanks for getting back to me.

I’ve noticed that on first load, Statically tries to load the images but fails. On opening the broken image on a new tab, I’m given the error message:

“400 Bad Request
Statically cannot download remote images, backend returned an unexpected status code (502).”

Then when I refresh the page, the images display, but from a cache rather than from Statically.

Could all this possibly be due a conflict with Cloudflare?
I’ve tried installing the Statically plugin and entering the API key, and it still doesn’t work

@sammiefields2512gmailcom Pls contact Statically regarding this

Gijo,

I contacted Satically, and here’s what they said:

“I apologize that this happened to you.

I checked into the service, it looks like your domain is blocked by our security filter. So I went ahead and whitelist your domain, please check from your side”

It’s working fine now, thanks for your help!

I can confirm that there is no need to install the Statically plugin.

@sammiefields2512gmailcom Cool!

Yikes, ok, new problem:

With your plugin, sometimes the images load via statically, sometimes they don’t. I’ve tried instead with the Statically wordpress plugin, and the images always load from statically.

Also, when using your plugin and the images DO load from statically, they’re still not webp – when I go to the network panel in my browser, the response header>content-type shows image/jpg.

I’m using the Statically plugin for now, until there’s a fix with your plugin.

“sometimes the images load via statically, sometimes they don’t” that’s probably something related to your cache.

“load from statically, they’re still not webp” – Once image URL is set to Statically, it’s their decision to deliver it as WebP or not. We don’t have any control over them.

woops please delete

• This reply was modified 4 years, 9 months ago by garryambient.

Hey Gijo,

Regarding the first point, it’s not a cache problem, as I can check in Chrome console whether it’s being delivered by cache.

With the Statically plugin, when I clear the cache then load the page, the images are delivered by Statically. Then when I refresh the page, the images are delivered from cache.

With Flying Images however, when I clear the cache then load the page, the images are delivered from my own server. Then when I refresh the page, the images are delivered from cache. Sometimes after clearing the cache, images are served via Statically, I’m not sure if the SAME images are SOMETIMES served via Statically, or if specific images are ALWAYS served via Statically, I didn’t take the time to play around with it.

Anyways, let’s see if others complain about the same thing, then you might want to look into it.

Don’t worry, I won’t leave a bad review, lol I’m using one of your other plugins and it’s great!

@sammiefields2512gmailcom is there any other plugin/theme doing lazy loading? If so try turning it off.

I’ll look into it detail if more people are reporting the same. Never heard about this issue.

Thanks