sorta piling on here, but it's also worth noting that this problem goes away (and the article is quite readable) in a browser with javascript turned off (and no adblocker).