- Make fewer HTTP requests - Reducing 304’s with Cache-Control Headers
- Use a CDN
- Add an Expires header - Caching with mod_expires on Apache
- Gzip components
- Put CSS at the top
- Move JS to the bottom
- Avoid CSS expressions
- Make JS and CSS external
- Reduce DNS lookups - Use Static IP address, use a subdomain for static content.
- Minify JS - Refactor the code, compress with dojo
- Avoid redirects - Use internal redirection with mod_rewrite, The correct way to redirect with 301
- Remove duplicate scripts
- Turn off ETags - In htaccess:CODEFileETag None
Header unset ETag - Make AJAX cacheable and small
Sources & References
- book
- These rules are the key to speeding up your web pages
- Image maps
- How do CSS Sprites work
- Speedy Sites with Image Sprites and CSS
- embed (small) media type data directly inline
- JSMin is a filter which removes comments and unnecessary whitespace from JavaScript files
- tool to reduce the size, and therefore latency, of JavaScript by browsers
- Status Codes for HTTP
- All 57 HTTP Status Codes
- A graphical tool that enables Web content providers to rapidly and accurately measure client side performance of Web pages
- Speed up Firefox
- HTTP Debugging Tool
- Debug the web!
- Part 1: What the 80/20 Rule Tells Us about Reducing HTTP Requests
- Part 2: Browser Cache Usage - Exposed!
- Part 3: When the Cookie Crumbles
- Part 4: Maximizing Parallel Downloads in the Carpool Lane
- The Importance of Front-End Performance
- Rule 1 - Make Fewer HTTP Requests