I hate to tell you, but it's SAFARI not the website. Prints fine on Chrome. And the HTML is all there - it's the first bit after the link to the style sheet under the <body> tag. It's all in <div class="wsb-canvas body"> - expand that and you'll see it. It's just layers deep; courtesy of the GoDaddy website builder used to construct the page 5 years ago (judging by the copyright notice). The javascript declarations are all after that - as they should be - and don't affect whether or not the page will print.
I don't know what is wrong with Safari - there are plenty of complaints about it not printing if you look - though most of those seem to be a complete refusal, rather than a blank page. I've also seen the blank page complaint about Chrome too - so all I can say is - try another browser.
If NO browser will print the page without conversion to PDF, then yeah, it's the page. But if another browser will print it, then it's more likely some peculiarity with the browser itself and how it interacts with that particular page. Lots of variables there, and while all major browsers are pretty good these days, they do have their differences. I use Firefox for web development because I like its dev tools the best, Chrome for development as well (speed testing etc.) and for regular browsing, and Safari sometimes as it is still set as the default from links in any other application on my Macs, and it is likely the most secure. However, it's much more likely to quit on me for unknown reasons and I find it much more quirky - sometimes sits there and refuses to do anything for no reason at all too. I also have Brave and Vivaldi. Vivaldi has the unique ability to pretend it's a phone, allowing one to upload to Instagram from a desktop.
