igb10

Instead of right-click and “Inspect”, right click and “Open image in new tab” and see the uncompressed size.

Or you can do it easier. Look at Pingdom website speed report here:
https://tools.pingdom.com/#!/bv9a3C/https://mbzmaster.com/important-update-to-2019-e-class-sedan-lineup/

Scroll down and check “File Requests”, you can click on “Size” to filter by size. You can see some images served are over 300kB! And the whole page grew to 2 MB. Then click on one of this images files name. For example click on “2019-C63-AMG.png” and it will open in the new tab – and then just look at the size.

I know… I’m puzzled myself. But click on the link I provided above on top in the first post and open this page. On the right side you’ll see 5 posts in the widget of the side bar.

Then if you use Chrome – right-click on the image and click on “Open image in new tab”. All of them will open in either 1024 or 1280 resolution.. You can also Inspect it right there.

On my home page and archive pages it works as you described at 768. I already cleared cache on website and Cloudflare.

Ok, so now I specified the size 372×209 and check-marked to keep aspect ratio. So my home page, archive pages and search pages continue to serve at reduced size, but only reduced to 768×432 resolution, while displaying 372×209 correct size on the screen – so the same thing.

However something changed on my Post pages, so there is a little progress. Featured images with original size of 2000×1125 are now served at reduced 1024×577 size, which is still very high… but much better than 2k! But if original featured size is 1280×720 – then image is NOT reduced at all and continues to be served at original size.

So there is a difference at service on archive pages and Post pages.
Here is HTML of the image when I click Inspect on Archive page:

<img width="372" height="209" src="https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-768x432.png" class="attachment-372x209 size-372x209 wp-post-image" alt="Mercedes C-Class Sport" srcset="https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-768x432.png 768w, https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-300x169.png 300w, https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-1024x577.png 1024w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px">

Here is HTML of the image when I click Inspect on Post page:
<img width="372" height="209" src="https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-768x432.png" class="attachment-372x209 size-372x209 wp-post-image" alt="Mercedes C-Class Sport" srcset="https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-768x432.png 768w, https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-300x169.png 300w, https://mbzmaster.com/wp-content/uploads/2018/04/C-Sport-Featured-1024x577.png 1024w" sizes="100vw">

That didn’t help, even made it worse. If I specify height and width, and don’t check-mark “Keep aspect ratio” – all the images are still served at fill weight. But now.. the image loses it’s ratio on the resize or serving at smaller screen – and they start to look really bad. So I went back to height 0 and 372px wide and checked to keep aspect ratio no matter what.

But now I noticed something really weird: on my home page all images in this widget are resized down to approx. 768px width. Still not compressed to 371px that I want… but much better than 2000 px width. Also my other categories/ archives pages serve the same reduced to 768px or so. However if I go to the Post page… all the images in the widget are still serving at full 2000 px!

So what is the difference on how this widget works differently on archive pages.. comparing to the Post pages? Because it serves the same images at different weight.

Thank you,

Eclev91, how do you increase the PHP timeout limit? And is it a good idea as far as security, since it didn’t have this provision in the 1st place?
Thank you,

I only know basic stuff. How and where do I check for errors?

Thank you for your reply. If I do it your way, everything works until I click ACTIVATE. Then the whole website crashes with internal error. When I go into plugins folder and delete the plugin file that was extracted, my website goes back to life.. Any other ideas?