@biscuitist I've seen a few reports of problems with group cooking, so it's worth testing other activities (with the new sims; I know you did with your old sims in the new save) to make sure you're still seeing the same issue. The welcome wagon event also complicates things, so please test once it's over.
There's no good guideline for how large a save should be, but over 100 MB is a sign that something may be very wrong with the save. I have seen saves that large that run okay, not mine but from other people. However, these tend to be "play all the sims in all the worlds"-style saves, so the large size makes sense given how much sim data would be present. I'd expect a legacy save of a few generations to be much smaller even when someone has played all the descendants.
The point is, the problem is not the save file size per se, it's something that happens to bloat the save. The size is a symptom. A common cause of this bloat is large numbers of sims being generated in the background—I've seen cases with literally 10,000 sims, most of which can only be found with a mod. If you want to check, one way is to add this mod:
https://frankkmods.com/#/mods/show-sim-info
Click one of your sims and select Search All Sims, and you'll see the total number of sims in your save.
I wouldn't expect photos to have such an outsize effect, although I suppose they could if extra data was attached to them. At the very least, I'd expect more reports than just yours since a lot of players like to collect in-game photos.
Separately, if you're placing one build in a new save and that save size is immediately 34 MB, that suggests there's something wrong with the build. You could try saving it as a number of different rooms and placing those to try to narrow things down.
For your legacy save, emptying out the sims' inventories is a useful test, as is moving them to a default EA-made lot. Use "save as" and see how the save file size changes. And please do let me know how many sims are in the save.