| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 |
I spent several hours today wading through IIS access logs. Not the most fun part to my job, but sometimes necessary. During the course of it though, I found a subtle difference with the way clients (browsers) pass the information that goes into these logs. Hopefully it will be of use to someone else.
Following on from yesterday's review of High Performance Web Sites, I had a quick go with YSlow, to see where I could optimise this site.
The starting point was a respectable score of C(71) for the home-page. The first rule that didn't score well was number 2: Use a Content Delivery Network. A CDN is over-kill for a blog, so that left me looking at the following rules 3 (Add Expires Header), 4 (Gzip components) and 13 (Configure Etags).
When a website is running slow, the traditional response has been to look at optimising the application code. In fact, 90% of the response time is taken downloading and rendering the page and it's constituent elements. In the book High Performance Web Sites, Steve Souders describes 14 rules for improving front-end performance.
