1. Database result set caching or even better, logical data object caching (eg. user profile). Dont run your joins over and over again!2. Using cache solution like CSQL (Bi-directional database cache, keeps tables in RAM, on which it queries)3. Different and faster approach to data model, like Cassandra4. Web server configuration tuning.. loads of stuff there. For example, does an Apache child serving image/ css/ js resources need to load with PHP when it wakes up? We always tend to set it up that way. Also, such static resources can be served with something like lighttpd which has a damn smaller footprint5. And of course, DIV designs please