These days, in practice, “slow” is usually a special case of “broken”; and the tricky thing about software brokenness is that there tend to be additional preconditions before it appears. I have occasionally seen Less Wrong being slow, but it doesn’t appear to be slow consistently.
The best way to investigate page-load time issues is to open Chrome’s developer tools panel (ctrl+shift+i or command+shift+i), go to the Network tab, and refresh. This will give you a list of all the individual parts of the page (including things loaded from third party CDNs, which are frequently sources of trouble), and a breakdown of when they started loading, how big they were, and how long they took. On the other hand, the problem might be on the server side. In that case, most of the time will go to the first entry in the list, the page’s HTML; and further investigation will have to be done on the server, rather than on the browser.
These days, in practice, “slow” is usually a special case of “broken”; and the tricky thing about software brokenness is that there tend to be additional preconditions before it appears. I have occasionally seen Less Wrong being slow, but it doesn’t appear to be slow consistently.
The best way to investigate page-load time issues is to open Chrome’s developer tools panel (ctrl+shift+i or command+shift+i), go to the Network tab, and refresh. This will give you a list of all the individual parts of the page (including things loaded from third party CDNs, which are frequently sources of trouble), and a breakdown of when they started loading, how big they were, and how long they took. On the other hand, the problem might be on the server side. In that case, most of the time will go to the first entry in the list, the page’s HTML; and further investigation will have to be done on the server, rather than on the browser.