Minifying JS libraries is definitely worth the effort, but don't forget to check your JS libraries first for syntax errors. I always use JSLint for that task.
In a web app I manage we use a lot of images and JS libraries. Lately, we've gained a lot of performance increase by caching images more aggressively on the user's client. This can be achieved by adding values to the HTTP response header. Chris Linfoot talks about this here: {Link}
Two notes about this method:
1. It won't influence first time visitors (which is what your current project is all about).
2. Think about what will happen if you update a library. Since the expiration headers are set, your end users won't automatically receive the updated file (only after a page refresh or after the resource is expired). We've solved this by adding a version to the path in which the resources are stored.
Minifying JS libraries is definitely worth the effort, but don't forget to check your JS libraries first for syntax errors. I always use JSLint for that task.
In a web app I manage we use a lot of images and JS libraries. Lately, we've gained a lot of performance increase by caching images more aggressively on the user's client. This can be achieved by adding values to the HTTP response header. Chris Linfoot talks about this here: {Link}
Two notes about this method:
1. It won't influence first time visitors (which is what your current project is all about).
2. Think about what will happen if you update a library. Since the expiration headers are set, your end users won't automatically receive the updated file (only after a page refresh or after the resource is expired). We've solved this by adding a version to the path in which the resources are stored.
Cheers,
Mark