No, you won't get any acknowledgement from Apple. But at least it's a means of telling them. There are other methods of contacting them more directly, including free phone contact, and for that you need to look at the options at the bottom of http://www.apple.com/support/, including at extreme bottom-right. Another thought is that you could complain also at a local highstreet Apple Store, if one's conveniently to hand. The harder and more widely we press Apple, expressing our deep dissatisfaction with the situation, the more likely Apple will sit up and start to take notice.
You mention the spinning beachball. The appearance of that is indeed symptomatic of this issue with Safari. Until I discovered a workaround some weeks ago, Safari would freeze whenever I visited the UK Amazon site, and the beachball would then appear. It'd never happen with any other website I used. My mouse pointer immediately became ineffective, except for some limited movement of it. I found that if I moved the pointer out of the website's window I was then able to do a Quit or to move backward to a previous and different website and then continue. But I think the ability to do this probably depends on the individual circumstances. I've gathered that this freezing has happened with pretty much all the Amazon sites around the world. Also, some other large websites, such as that of the New York Times, exhibit this behaviour as well.
Use of Activity Monitor, one of the utilities built into OSX (see Applications > Utilities), has always flagged a 'website error' when this freezing has occurred, at the same time showing that CPU activity goes up to virtually 100%. It's clearly an issue that involves both Safari and certain websites, and it's my contention that the websites of Amazon and the like now fail in compatibility terms because changes were made some months ago in the Javascript that they use (that's Javascript, not Java), so that now the website hyperlinks and other functions no longer respond properly to the browser. Incidentally, this issue seems to be affecting all other browsers (despite some claims to the contrary), as well as being common to Yosemite, Mavericks and El Capitan. Curiously though, one or two respondents say that they don't experience the problem at all. Eric Root, for example, says he's not met the problem. The 64-dollar question is Why? What's he been doing that we haven't? Is it just that he hasn't exercised the Amazon site sufficiently? After all, the problem at that site comes and goes; sometimes you can spend some hours there and not meet it at all, but in other sessions the freezing will happen within a minute or two.
The workaround that I discovered was to reconfigure Safari to use a smaller fontsize. This was, and is, dead simple to do. It's stopped the freezing and the beachballing, though just occasionally the beachball will appear for half-a-second (with no consequence) when I'm moving from being online to offline. This workaround has worked for many others too, I've gathered, though I suspect it might be confined to specific Macs, such as iMacs. Always worth a try, though. It could be, for instance, that certain website developers took a decision some months ago to cut down the number of compatible fontsizes, perhaps as a measure in slimming down website performance to conform more to iOS devices. Who knows?
One particular theory banded about by others is that some websites are now employing IPv6 and that therefore users who continue to use IPv4 will inevitably find that their browser will then either not open the website at all, or will display only a limited amount of the webpage. Personally, I've not tested for this, for the simple reason that my ISP tells me that they do not, as yet, support IPv6. In any event, these symptoms can just as easily be the result of some corruption of website data on the individual's machine (history, cookies, cache, etc), which could be corrected by just clearing them out.
Finally, there's the question of Flash Player. Is it necessary? Should it be used on any Mac these days? Could it be interfering with the operation of Safari in some detrimental way? Well, it's classed as a 'plug-in' and is most certainly still required at many websites, one or two of which I regularly use. And despite all the bad press that Flash has received in recent years about holes in its security, I found that the latest iMac on demo in my local Apple Store most definitely was using it, so I can only summise that Apple regards the presence of Flash on its Macs as perfectly valid, provided it's kept up to date.