I think it's less of an unfamiliarity and more of an outdated development practise. Plus, completing the entire page in under 750ms (measured in Firefox) is still faster than some other pages out there (reddit: 4s, HN: 1.2s, etc)
I would personally say the website has it's charm, even if it's a bit dated in design.
Oh no, I don't have anything against the website. It worked 100% of the times I tried in less than one second and it responds well to every lighthouse audit for performance except render-blocking tags. Also the books look amazing.
But the point was all about the look of the site and the defense was that it should behave like an old-time simple barebones website because it looks like one. This is not true.
This website waits to parse a JavaScript file that adds like 5 lines to the bottom of the page. It looks and behaves... unconventionally.
Why can't the website just load everything and then, only after showing you the contents of the page, run the necessary JavaScript? Probably because the developer never even thought about all of this. I don't blame him. He's not walking around saying his website is fine handcrafted HTML free of bloat or fluff. He's just making a website about his book.
As a sidenote, you believing that this is a website that "loads extremely quickly" reminds me of Jonathan Blows's "there's generalized insanity about software and people often don't know what makes programs slow" ( https://www.youtube.com/watch?v=gWv_vUgbmug )