The page was causing 100% CPU usage in Chrome for me. Admittedly, this may have been the result of using an adblocker and some aggressive rules or possibly some

The page was causing 100% CPU usage in Chrome for me. Admittedly, this may have been the result of using an adblocker and some aggressive rules or possibly some kludgy userscripts. Anyways, the page was giving console output suggesting that it was trying to use javascript to actively change the layout of the page. Whatever the actual intent, I managed to stop such activity by blocking 'devicepx-jetpack.js' and 'jquery.sticky-kit.min.js', and article site appeared to stay mostly intact.