Hello by1411,
I do not know exactly understand what you want to achieve, sorry! Please notice that you should turn off all the thumbs which you do not use on your website. If you will turn off such a thumbs and then if you will use blocks which are using that thumbs you will bring a message with the required images size in a placeholder.
Thanks for your understanding!
Hi,
I use blocks on my website but I only want it to use 1 image size (i.e. 500*500px) for all the different thumbs. Not resizing to another size (i.e. 300*400px) for a specific thumbnail.
I can achieve this successfully by uploading images directly to my web server instead of using WordPress uploader. But this might require me to login to my server every time I post and other users who posts via WordPress panel can not achieve this.
Well, it’s really bad to use one thumb for all size images from pagespeed/seo point.
Meaning, if you only have 500px image, and then try to have theme resize to fit 200×300 thumb, it will either be distorted or oddly cropped.
You cannot load a 200×300 thumb without there actually being a 200×300 thumb image.
Google will penalize you for only having one image resized to different sizes (try it).
“You cannot load a 200Ă—300 thumb without there actually being a 200Ă—300 thumb image” -> I am doing this actually and no distortion of images.
I am more concerned about this: Google will penalize you for only having one image resized to different sizes (try it)” -> Is there any statement from Google about this?
Um, yeah. Test one of your pages with the image sizes not at ‘actual size’ with Google’s testing tools? Have you tested your site with PageSpeed or their mobile testing tool? Sites which don’t do well in mobile testing won’t be shown to mobile users!
e.g.,
https://search.google.com/test/mobile-friendly
Meaning there is more overhead for browser to resize images multiple times to multiple sizes vs caching the actual images at actual sizes.
However if it works for you, and you’re passing Google’s PageSpeed test and mobile test doing it your way, go for it — just not “normal” practice in modern webdev (I’ve been doing it since 1995 professionally, as a point of reference).