The reason why there was such a small effort on optimization in the first place is that this isn't meant to be a revenue generating site, or one that focuses on

The reason why there was such a small effort on optimization in the first place is that this isn't meant to be a revenue generating site, or one that focuses on "ultimate performance" - it's more of just a personal, online resume. Any time I needed something new, I'd just throw it in, because "it worked and looked good on my machine". If I found a cool js snippet that needed an entire library, I'd just throw it in. An argument could be made that that's part of what's wrong with modern webdev, and I wouldn't necessarily disagree, but this wasn't trying to be the fastest or most efficient site out there. I think there's a pretty distinct difference between making a scalable, well optimized webapp and just making a personal site as an online resume. This was me documenting my updates - I just revised the article with a few more updates, and the total site size is 250kb, 99kb without images. This still isn't great, but total page speed is pretty quick (js execution takes ~70ms on my 2016 MBP). Thanks for the feedback!