For the photo as you posted it here, dimensions are listed as 700 x 800 pixels.
Dividing those numbers in half will produce the same image but half as wide and half as tall.
So do what you did to post the image. To re-size, following the first equals sign = , the url of the image MUST be bracketed by quotation marks " " , as do the pixel numbers following their own = sign(s) which specifies what dimension. After the " close quotation mark skip a space if desired, then if half width & height of the image your are sourcing from is wanted, in this instance put height="400" width="350" followed by the closing > bracket command, leaving that part of the equation appearing something as
- ="url listing for image" height="400" width="350">
So give it a try? If more folks are going to post images, we all may as well know how to make them a bit smaller. Remember to use the review function. Switching the dimensions around can give yield some strangeness. Done on purpose for effect is another trick...
Dividing the width/height by 4, yields
loads faster, making it easier on smart-phone users and remote location dial-up dinosaurs. So if the image not needed to be big to maintain effect, something smaller is many times better. In the Thatcher/Reagan photo, the fuller size brings some detail and effect...so I'm not complaining, just talking about images in general.
One thing I've noticed is that in "properties" the width seems to be given before the height...but when resizing it's somehow either traditional (or maybe necessary?) to first enter height="", then width="">.
Notice too, that a url following the opening command sequence bracket < img src= need not be put within quotation marks to simply bring the image in the same size as is listed at the original location. But we've been told that it loads faster if we do add the quotation marks, even if not resizing, which is good to know.
Just to get < img src= to appear (and not get lost as an opened-but-not-finished-and-closed > command, I had to skip a space between the opening command bracket < and that which followed.
There is another way to code, bringing what is apparently keystroke results as substitionary images themselves, resulting in a coder being able to present a replica of the code without needing skip a space at crucial junctures to invalidate the html coding execution itself (thus leaving the apparant keystrokes to appear rather than not). But I'm not ambitious enough to go look up the tables, and am years away from original bookmarks for that stuff. It can take some digging, using the just right search terms to find the stuff in the first place, but it's out there...simulated code which does not execute as html command, can be done...