No specific file size but the total weight of all the images will make the site load slowly for people who don’t have fast connections, thing rubbish broadband, mobile 2g/3g etc.
As an example your logo image is 620kb, that is huge, I’d normally expect that sort of image to be optimised to about 10kb-ish. If you optimise all your images you should be abel to bring the page weight down to well below 1mb, that’s a 75% + saving.
I run the homepage through Pingdom and it comes up as being 8.1MB in total. The real hog being the background image stair-face-grab-3.png at 4.7MB alone.
Choice of image format is important. As a general rule, don’t use png for photos, they are quite inefficient for that, jpeg is better where you don’t need alpha.
However your logo, which has already been commented on may be more efficient as a png rather than jpeg, png is more efficient for that type of graphic image (though svg is better ).
This was a new area for me but thats to help here ive learnt and resolved the isssue of huge picture file sizes, thank you @Gandalf@SamA74@bluedreamer. Now my home page is super skinny in comparison to yesterday
That’s a significant reduction in load time and page size.
I see with the logo you have got it super small filesize by upping the jpeg compression, but that has introduced some noticeable compression artefacts. That’s why I was inclined to go with png for that type of image. The png format used lossless compression, this means that although you have no control over the amount of compression, the image quality is not degraded at all form the original. That’s why it’s so inefficient with photos or very detailed images. But with graphics with areas of flat colour it can be very efficient without any loss of image quality.
You could make a further saving with the grid images. I see they are ‘letterboxed’ with black sides to give a square aspect ratio. Those black bands are redundant pixels and could be cropped off and replaced by a black css background.
To make the images fit the square container you could use object-fit: none, see the methods discussed in this thread:-