Thread

they are giving away a dream home, read more here: http://ellislab.com/forums/viewthread/186993/

of course the architecture will be great as useful, and you won’t need to worry about home improvement or decoration.

Hi Jan. This is all non-EE related, but sounds like you need to do some caching of your static content (Javascript, CSS, images). I tend to do this in my .htaccess file, with far-future expires headers like “access plus 10 years”. Then you can use cache-busting techniques as outlined Cachebusting techniques to help you manage versions (avoid query strings in CSS refs). That will certainly help.

You should also enable Gzip compression if you can. Other best practice stuff like combining/minifying scripts, and referencing them after your </body> tag can help. Maybe add a defer attribute on some of your external scripts. For high traffic sites you might even want to put your static content on a CDN. There’s a bunch of other front-end tips you can Google too.

You could use Minimee to combine and minify your JavaScript and CSS files.

It requires almost no effort on your part (other than installing and doing the initial config). This technique avoids the query string trick by rebuilding the cache files with unique names every time you make a change.

Setting a far future expires header is a great technique for people who run sites with high traffic and visitors who frequently return to the site at regular intervals.

If you’re setting up a site for a client’s local interior design business for example, using cache control on the server is kind of overkill (in my humble opinion).

I only have one site that uses cache control and it’s a frequently updated newspaper website with many returning visitors.