title: Skipping traditional pages load/speed techniques when mod_pagespeed in use
body: <p>I'm trying to determine if certain "PageSpeed best practices" can be skipped by our front-end team and build process now that we are using mod_pagespeed (Apache). An example of things which mod_pagespeed does automatically which could potentially be skipped are:
  1. Combine and Minify JS and CSS (such as might be done with a tool like Browserify)
  2. Compress images
  3. Asynchronous loading/injection of JS and CSS (script loaders, atomify, etc)
  4. Static asset versioning for cache-busting (grunt-usemin, etc)</p>
  
  <p>To give an example answer, right now I have removed static asset versioning and instead have our global.js and global.css files non-versioned and with a short expiry time. This is because mod_pagespeed quickly versions them with huge expires anyway.</p>