How do I know if Hammy is working?

Good question Bill, so if you resize your browser and then right click the image to open it up, the URL should be quite different:

One of my blog posts:
https://www.noeltock.com/web-design/wordpress/all-for-one/

Small image:
https://www.noeltock.com/wp-content/uploads/cache/2013/05/team/1488879186.jpg

Large image:
https://www.noeltock.com/wp-content/uploads/cache/2013/05/team/1791085542.jpg

This was simply done by right clicking open on the same page and the same image after resizing.

I see. I checked the images on my site https://digitl.co.nz and they are much smaller than the uploaded image, that’s good. And I notice that means faster page loads.

Can I assume the page speed results show them as uncompressed because Smushit isn’t compressing the hammified images? And, supplementary question, is that do-able?

Great. That’s correct, the image resizer doesn’t compress the same way smushit does, hence it won’t tag it as such in pagespeed tests. That said, your mobile users are still shaving 80%+ bandwidth on mobile ??

I ran into this as well. Prizm Image is a great plugin to resize and pass PageSpeed tests.

It would be great if Hammy would map to WordPress image sizes like Simple Responsive Images seems to do.

Adding custom image sizes in WordPress is easy and Prizm takes these into account. You can even create the new image size only using AJAX Thumbnail Rebuild.

Unfortunately, I couldn’t get Simple Responsive Images to work at all.

I stumbled on to Hammy because of Google PageSpeed. It solved the issue of serving smaller images to mobile. But re-introduces the optimized image problem. Would be great if Hammy would work together nicely with Prizm!

As this topic is marked “resolved” and I got no response on my tweet, I decided to try to contact the developer with a separate post.

As this topic is marked “resolved” and I got no response on my tweet, I decided to try to contact the developer with a separate post.