These pages about different languages / apis / best practices were mostly jotted down quckily and rarely corrected afterwards.
The languages / apis / best practices may have changed over time (e.g. the facebook api being a prime example), so what was documented as a good way to do something at the time might be outdated when you read it (some pages here are over 15 years old).
Just as a reminder.
Decrease the loading time for web pages
how to reduce number of http requests
As a side note, to "build" my website I use ant, (in essence, pack together and push out the files I changed to the production server), so that is what i refer to when i mention "build process" further ahead.Less files, means less requests.I bundle together all css files in the build process, i.e. it means the client would only have to request one css instead of several in parallel.
so if the user just passing through and wants to click onto some other page in your menu, they can do it quickly.
of that image using the css background-image /position.Memcache anything that makes sense, keep in mind that you can also cache chunks of html to avoid recalculating stuff (it is not just db-requests that slow things down),
but make sure you have proper handling of the data with/without memcache.
A good test is to bring memcache down and the web page should still look nice.Turn on gzip on anything that makes sense (e.g. not useful for pdf, but for ccs and js)But getting a bit off topic, just wanted to mention the number of http requests which people tend to forget about.
Google around and you will find other tips on how to speed up your website.
More programming related pages