Not sure if I'm doing it right

Hey Chris,

Glad to hear the plugin is helping you out. It does seem like the plugin is doing it’s job since you’re seeing the srcset and sizes attributes on your images. There are several reasons that Google’s page speed test may still be giving you warnings. First, it may be that the image sizes that are included in the srcset are wider than they need to be for how they appear on the page at certain viewport widths (e.g., mobile device sizes). You could create an additional crop size that is smaller to compensate for this, but that’s really up to you.

The second reason Google might complain is if the original image isn’t compressed as well as it could be, which means the file size would be larger than necessary. Here are some tips on image optimization from Google: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/image-optimization

Hope this helps.

Joe

Hey Joe,

thank you for your reply.
Is there a chance in the plugin to set the images sizes in the srcset? Because (pls correct me if I’m mistaken) in my example above it looks like that:
`??<img class=” wp-image-6253 size-full aligncenter” src=”https://xn--canyoningallgu-iib.de/wp-content/uploads/2013/10/Canyoning-Allgaeu-Bayern-Starzlachklamm1.jpg&#8221; srcset=”https://xn--canyoningallgu-iib.de/wp-content/uploads/2013/10/Canyoning-Allgaeu-Bayern-Starzlachklamm1-300×164.jpg 300w, https://xn--canyoningallgu-iib.de/wp-content/uploads/2013/10/Canyoning-Allgaeu-Bayern-Starzlachklamm1.jpg 476w” alt=”” sizes=”(max-width: 476px) 100vw, 476px” height=”260″ width=”476″>

So the image width is 476, but where is the plugin telling the browser (of an Iphone) to load a smaller version?

To your second point: I optimzed the fotos for a desktop and therefore they have the right size. It’s just that mobile devices are loading the same foto, and that’s where it becomes tricky.

So is there a chance to change settings so the mobile devices load smaller images?

Hi,

I had the same issue and i found other developpers that faced it too.

See this topic : https://groups.google.com/forum/#!msg/pagespeed-insights-discuss/-3w9jyBHNQY/X-tmEnIultsJ

That’s not a RICG plugin bug but it could be a Page Speed Insights limitation.