Include all your own CSS and Javascript in the same file as your HTML, so that only one page needs to be requested. During times of heavy load, 99.9% of your visitors only load a single page of your web site anyway, so it makes no sense to split things up into different files.
This is terrible advice. Your JS and CSS should be consolidated into single files for latency purposes, but including them in every HTML page is insane. The bandwidth costs for two extra connections are negligible. After that you are wasting bandwidth every single time someone would have have those files cached.
On the latency front, reducing the number of connections improves latency on the later connections (given the standard browser limit of two connections per domain). However cramming CSS and JS into the HTML file actually will increase latency as it has to process those before it can display the page. This is arguably a benefit in the case of CSS so your visitors don't see an unstyled page, but with JS it's definitely bad.
This is terrible advice. Your JS and CSS should be consolidated into single files for latency purposes, but including them in every HTML page is insane. The bandwidth costs for two extra connections are negligible. After that you are wasting bandwidth every single time someone would have have those files cached.
On the latency front, reducing the number of connections improves latency on the later connections (given the standard browser limit of two connections per domain). However cramming CSS and JS into the HTML file actually will increase latency as it has to process those before it can display the page. This is arguably a benefit in the case of CSS so your visitors don't see an unstyled page, but with JS it's definitely bad.