Editor’s note: This post formed the basis of the Front-End Optimization talk I’ve given in the past.
Not if you want maximum performance.
According to the Yahoo Exception Performance team:
…Only 10% of the time is spent here for the browser to request the HTML page, and for apache to stitch together the HTML and return the response back to the browser. The other 90% of the time is spent fetching other components in the page including images, scripts and stylesheets.
So static content is very important. The same Yahoo people provide us with a comprehensive list of Best (Front-end) Practices for Speeding Up Your Website. IMO, some of the rules are more important than others, and some are more easily achieved. Leaving aside hardware solutions (static server, CDN, etc.) for now, let’s look at six of the rules:
- Rule 3: Add an Expires Header, or every static file must accompany a time-stamp so we can take advantage of the HTTP Expires: header. A time-stamp in the GET parameters might work, but some say that some CDN’s and browser/version/platform combinations will not request a new file if the query string changes. A better solution would be to put the time-stamp in the filename somewhere.
- Rule 4: Gzip Components. This is easily achieved by enabling
- Rule 9: Reduce DNS Lookups. Okay, the real value in this rule is introducing parallel downloads by using at least two but no more than four host names. This is better explained here.
- Rule 12: Remove Duplicate Scripts, which as they say is more common than you think.
Rule 3 is a matter of configuring Apache. How to achieve the other five?
As I see it, there are three broad ways to achieve them.
- Handle every request in real-time. This means using a PHP file to serve the files (e.g.
<link rel="stylesheet" type="text/css" href="custom_handler.php?file1.css,file2.css" />or something like that). It can also mean using
- Use a template or view plugin. If you are using a templating system to dynamically generate your HTML, you can use some sort of plugin or function to read in a list of static files, check their last-modified times, and if changed build a combined, minified, time-stamped output file to serve up. This is better than method #1 because by the time the page is built, there is a static file that is simply served to the browser. Still, there must be a better way.
- The best way is to do it offline. This means a job that checks static files to see if they’ve been modified. If so, it processes the files and builds the output file that is directly served to the browser. This job could be run in cron, or run manually by developers, but the best way is to make it a part of the build server.
Don’t have a build server? That’s a whole other topic.