1. Make fewer HTTP requests – Grade:F

```
This page has 19 external JavaScript files.

```

2. Use a CDN – Grade:F

3. Add an Expires header – Grade:F

```
These components do not have a far future Expires header:

```

4. Gzip components – Grade:F

```
These components are not gzipped:

```

5. Put CSS at the top – Grade:A

6. Put JS at the bottom – Grade:A

7. Avoid CSS expressions – Grade:B

```
4 rules containing “expression” were found across all the CSS text.

```

8. Make JS and CSS external – Grade:n/a

```
Only consider this if your property is a common user home page.
```

9. Reduce DNS lookups – Grade:A

10. Minify JS – Grade:F

```
The following JavaScript files do not appear to be obfuscated nor minified.

```

11. Avoid redirects – Grade:A

12. Remove duplicate scripts – Grade:A

13. Configure ETags – Grade:F

Overall Grade F(40)

MoreInformation at:[Best Practices for Speeding Up Your Web Site](http://developer.yahoo.com/performance/rules.html)

My ideas for improvements

Point 1: I think it is not useful to merge the JS and CSS files to two big files, because the readability of the code decreases and it becomes more difficult to understand the code.

Point 2: Negligible at the current state

Point 3,4: Can only be achieved by server configuration

Point 10: I think we should a least create minified versions of our own js-files. Any suggestions for a good js minifier?

Point 13: Can only be achieved by the server configuration

The only point seems to be point 10. At this stage, but such a thing has to be done at build time, or in a post commit hook. We could open a ticket for this if we decide to implement it.

At the current stage, I suggest there is not much we can do that Yslow! advises us.

Thanks Christian for the analysis :)

I’ve already mentioned this in an email to the core developer team, but may a customized [PHP Speedy](http://aciddrop.com/php-speedy/) be a solution to points 1 + 10?
Without loosing readability

ticket done. Created #533 to followup our findings