HTTP Requests4:36 with Nick Pettit
It's important to pay attention to the total number of HTTP requests on a web page. Even when no data is sent, as is the case with a 404 error, an HTTP request will still take up time. Each HTTP request is generally fast, but if there lots of assets (even small ones like icons), it can add up.
- Reduce HTTP Requests - Every asset will generate an HTTP request even when no data is sent (as is the case in a 404 error). The browser is also limited in the number of parallel connections that can be open at one time. For this reason, reducing HTTP requests is paramount to improving performance.
- 404 Error - This is an HTTP response indicating that the server could not find the requested asset.
You need to sign up for Treehouse in order to download course files.Sign up