Perhaps next time it happens open up the browser console and see if you can pin down which particular endpoint, or resource not loading that is the culprit.