Honestly, the "use Browser caching" point is mute for two reasons.
1) Its up to the client (the end user if they use browser caching)
2) During testing, you will need to test in both conditions, with and without caching. If you never test without the cache then you have no idea how fast the site will load for the user on their initial page load.
Also the article makes no mention of static asset caching server side. Once development is finished and its go live time sane caching rules need to be put in place server side for static assets. Most likely implementing a cdn when possible to expand the number of concurrent request available to the host server.
1) Its up to the client (the end user if they use browser caching)
2) During testing, you will need to test in both conditions, with and without caching. If you never test without the cache then you have no idea how fast the site will load for the user on their initial page load.
Also the article makes no mention of static asset caching server side. Once development is finished and its go live time sane caching rules need to be put in place server side for static assets. Most likely implementing a cdn when possible to expand the number of concurrent request available to the host server.
