I've got a couple of sites I designed for my work, nothing major, mainly just little tools which individuals can access and employ when they are outside. I am not so experienced like a developer but I love to mess quite a bit and I'm wondering if anybody had any clever little tweaks I possibly could do in order to my sites to ensure they are download faster? There's an office in south usa having a poor web connection who constantly complain my sites take too lengthy to make use of. To date I've discovered the next site that was quite helpful and also the men within the other office stated they'd seen a positive change within the service www.dev-explorer.com/articles/apache-optimisation

Anybody kno associated with a more little odds and ends I possibly could do?

Any assistance is much appreciated.

Thanks ahead of time


Consider YSLOW and browse the Yahoo Dev blog. You are able to perform a lot by optimizing the leading-finish.

  • Limit the amount of http demands (css, js, images)
  • Use mod_deflate in apache to gzip your articles
  • Make use of a far-future expires header whenever you can
  • Build your HTML markup as lean as you possibly can

2 things (from YSlow) that can help really are a CDN (Content Delivery Network)... and cookie-less servers for static content.

Even when you can easily push your images to load off another server you'll have the ability to load your HTML content faster while image installing sometimes happens without anyone's knowledge in the other server(s).

Attempt to have other servers (for images, CSS, and Scripts) be cookie-less if at all possible, its a small saving, however it seems like you are attempting to squeeze every last drop. -)

not to mention, cache everything except your HTML.

I'd got for yslow, as already stated, and (because is exactly what yslow is dependant on) the Yahoo Exceptional Performance Team best practices

A couple of simple methods:

First of all, limit you to ultimately exactly one CSS and something Javascript file. Forget about. For those who have multiple compact them into one (each). Ideally, your Javascript ought to be minified. I have used JSMin with this recently.

You will find more advanced strategies to optimize this. You place the expires header to far later on therefore the browser does not download it as being frequently. To push changes you have to alter the connect to the css/js file though. This can be done with Apache mod_rewrite along with a small PHP script.

More about this in What is an elegant way to force browsers to reload cached CSS/JS files?

You may also make use of the expires trick on images.

Next, gzip your constent. Typically all you want do with this in PHP is start all of your scripts wiht:


This activates output loading (wise decision anyway) and when the browser states it supports gzip encoding, your script is going to be gzipped before delivering it towards the client.