Ticket #85 (closed defect: fixed)
Speed suggestions
Reported by: | ed | Owned by: | chris |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Drupal modules & settings | Keywords: | |
Cc: | Estimated Number of Hours: | 0.0 | |
Add Hours to Ticket: | Billable?: | no | |
Total Hours: |
Description
I am talking with Ben about servers etc. but these suggestions came up:
Taking a quick look at the YSlow profile of the site, there are a couple optimization opportunities:
1) 8 external stylesheets -- most can be consolidated automatically by Drupal
2) no expires header on css or image files
Change History
comment:2 Changed 6 years ago by jim
- Owner changed from jim to chris
- Estimated Number of Hours set to 0.0
- Status changed from new to assigned
- Billable? unset
- is done and will remain done...
- Expires headers - NEEDS CHRIS!
Chris, solution below and here http://drupal.org/node/272082, please implement this:
1.Changing the future date for the Expires headers is easy enough: simply edit your .htaccess file. Your Apache server must also have mod_expires installed, this is available by default on most servers.
2.Enable 'LoadModule? expires_module modules/mod_expires.so' in your apache configutation file.
3.Add the below lines on your .htaccess file.
ExpiresActive On ExpiresByType text/html A1 ExpiresByType application/x-javascript "access plus 3 months" ExpiresByType application/javascript "access plus 3 months" ExpiresByType text/javascript "access plus 3 months" ExpiresByType text/css "access plus 3 months" ExpiresByType image/gif "access plus 3 months" ExpiresByType image/jpeg "access plus 3 months" ExpiresByType image/jpg "access plus 3 months" ExpiresByType image/png "access plus 3 months"
This will improve speed, yes - and indeed the CSS optimisation is _supposed_ to be on so resolves (1)
As for (2), no expires is a good idea - will need to look into modules that handle this.
However, these enhancements will make little improvement to the user experience when the site is on such a slow server.