Website performance | URL time saving
cool notes at tech days 2010
1) use slash-ending urls to save performance:
ex.:
http://www.google.pt --> http://www.google.pt/
the url is forward to the with-slash version by IIS
directly adding it saves load time
2) use an "Expires header"
3) use http compression (gZip)
4) use separate .js and .css files, but try using the least amount of external files
5) minimize & compress .js and css files on production environments
Option 1: CSS Sprites for reducing http calls on image files
Option 2: Use CDN to get jQuery and other extensions. saves a lot of time (http request faster, and ensure minified, gziped and geopositioned versions)
Thanks to César Silva and Luís Martins for their great sessions.
1) use slash-ending urls to save performance:
ex.:
http://www.google.pt --> http://www.google.pt/
the url is forward to the with-slash version by IIS
directly adding it saves load time
2) use an "Expires header"
3) use http compression (gZip)
4) use separate .js and .css files, but try using the least amount of external files
5) minimize & compress .js and css files on production environments
Option 1: CSS Sprites for reducing http calls on image files
Option 2: Use CDN to get jQuery and other extensions. saves a lot of time (http request faster, and ensure minified, gziped and geopositioned versions)
Thanks to César Silva and Luís Martins for their great sessions.
Comments
Post a Comment