Something may be broken on 95% of web pages (e.g. commenting or menus), but the main bit of the web - rendering hypertext and following links - mostly works.
Web applications less so, of course. But I don't think they're 95% of the web.
If you really need scripting on a page, it's very uncomplicated to add an exception in Chrome: just click the "Javascript blocked" icon in the address bar, and choose "Always allow Javascript on example.com".
In my experience using NoScript for the past year on all my desktops and laptops, this is at best only partly true.
Load times do definitely decrease, but this is dwarfed by the effect of having to reload the page for most new sites after re-enabling Javascript (since so many sites are unusable without Javascript[0]). In the end, it's a much slower experience browsing the web, not faster, and even with aggressive whitelisting, it's still rather frustrating.
I actually have separate Firefox profiles that I use for various websites that tend to be particularly problematic with extensions (like online banking), so I'm not even including those in this summary.
I wish using NoScript provided a faster browsing experience overall while providing better security, but the simple fact remains that right now, it does not. It provides better security at the expense of slowing down your browsing experience.
[0] So many static blogs now literally fail to display static text without Javascript!
Why would someone want to use javascript on the client-side for things where it's not necessary?
Year after year, the browser and the web are turning into "something else", and while the possibilities are exciting, it seems the use cases where javascript is used for things that actually make a positive difference, are vastly outnumbered by the cases where it is used to re-implement in a more flashy, complex and resource-intensive way things that have been usable, performant and functional, 10 years ago.
IMO displaying content should be done just by HTML, using javascript if it's not to provide useful functionality, is wrong.
Whether it is browser HTML/CSS incompatibilities, flash atrocities or complex script bloat, it seems the popular web always manages to fix one problem and create another.
When I click a link and see a blank page, I often click the back button or close the tab rather than allow it to run scripts. You do not need a script to display text. That functionality has been present since Sir Tim wrote version 0.1 .
Would it be so hard to provide alternate text for no-script browsers that says "Some content on this site is only viewable to users that allow scripts hosted by www.example.com and js.example.com to run on their browser clients."? No. It's not. There is no excuse for serving a blank page full of invisible scripts.