Hello.
Only some .js files are gzipped and cached by the browser.
The 2 .css files that you send to the browsers are neither gzipped, nor cached.
This comes in the .htaccess file in the forums main webserver-directory.
I tried much, but this was best i achieved so far.
It is always best practize to gzip ressources directly through Apache rather then the applications installed on server (forum software).
________________________________________________
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 seconds"
ExpiresByType image/x-icon "access plus 2592000 seconds"
ExpiresByType image/jpeg "access plus 2592000 seconds"
ExpiresByType image/jpg "access plus 2592000 seconds"
ExpiresByType image/png "access plus 2592000 seconds"
ExpiresByType image/gif "access plus 2592000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2592000 seconds"
ExpiresByType text/css "access plus 604800 seconds"
ExpiresByType text/javascript "access plus 216000 seconds"
ExpiresByType application/x-javascript "access plus 216000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</IfModule>
# END Expire headers
# BEGIN Cache-Control Headers
<IfModule mod_headers.c>
<FilesMatch "\\.(ico|jpeg|jpg|png|gif|swf)$">
Header set Cache-Control "max-age=2592000, public"
</FilesMatch>
<FilesMatch "\\.(css)$">
Header set Cache-Control "max-age=604800, public"
</FilesMatch>
<FilesMatch "\\.(js)$">
Header set Cache-Control "max-age=216000, private"
</FilesMatch>
<FilesMatch "\\.(php|html|xhtml?)$">
Header set Cache-Control "max-age=600, private, must-revalidate"
</FilesMatch>
</IfModule>
# END Cache-Control Headers
# BEGIN Turn ETags Off
<IfModule mod_headers.c>
Header unset ETag
</IfModule>
FileETag None
# END Turn ETags Off
# BEGIN Remove Last-Modified Header
<IfModule mod_headers.c>
Header unset Last-Modified
</IfModule>
# END Remove Last-Modified Header
<FilesMatch "\.(js|html|xhtml|text|txt|css|php)$">
SetOutputFilter DEFLATE
</FilesMatch>
________________________________________________
This is the Start-Page of USmessageboard.
You can optimize the images at Yahoo's "smush.it" without quality loss.
Also the images loaded from theme have no expiries set, meaning browsers load them every time.
In above .htacces it is covered.
LINK: Smush.it
or
PunyPNG - PNG Compression and Image Optimization - Gracepoint After Five
This is Yahoo-Yslow performance analysis of front-end of one of my websites:
100 is max.
The score for USmessageboard, I wont post.
I don't want to meddle in your things.
But with little work, you could optimize front-end load of website, like caching pictures and scripts, gzipping scripts.
Minimization of scripts and combining them to reduce DNS-lookups would need more "work".
From Yahoo:
LINK: Yahoo - Best Practices for Speeding Up Your Web Site
You make 21 HTTP-requests on Front-Page.
Depending on each Users settings for paralell downloads in their browser-settings, this is - like Yahoo says - the area to achive most results in responsiveness of front-end.
That would need the HTTP-requests to decrease, which is achieved by combining the scripts which make the HTTP-requests.
P.S: Sorry for meddling in your business.
And I do not take any responsibilities, if you try something mentioned here.
Only some .js files are gzipped and cached by the browser.
The 2 .css files that you send to the browsers are neither gzipped, nor cached.
This comes in the .htaccess file in the forums main webserver-directory.
I tried much, but this was best i achieved so far.
It is always best practize to gzip ressources directly through Apache rather then the applications installed on server (forum software).
________________________________________________
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 seconds"
ExpiresByType image/x-icon "access plus 2592000 seconds"
ExpiresByType image/jpeg "access plus 2592000 seconds"
ExpiresByType image/jpg "access plus 2592000 seconds"
ExpiresByType image/png "access plus 2592000 seconds"
ExpiresByType image/gif "access plus 2592000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2592000 seconds"
ExpiresByType text/css "access plus 604800 seconds"
ExpiresByType text/javascript "access plus 216000 seconds"
ExpiresByType application/x-javascript "access plus 216000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</IfModule>
# END Expire headers
# BEGIN Cache-Control Headers
<IfModule mod_headers.c>
<FilesMatch "\\.(ico|jpeg|jpg|png|gif|swf)$">
Header set Cache-Control "max-age=2592000, public"
</FilesMatch>
<FilesMatch "\\.(css)$">
Header set Cache-Control "max-age=604800, public"
</FilesMatch>
<FilesMatch "\\.(js)$">
Header set Cache-Control "max-age=216000, private"
</FilesMatch>
<FilesMatch "\\.(php|html|xhtml?)$">
Header set Cache-Control "max-age=600, private, must-revalidate"
</FilesMatch>
</IfModule>
# END Cache-Control Headers
# BEGIN Turn ETags Off
<IfModule mod_headers.c>
Header unset ETag
</IfModule>
FileETag None
# END Turn ETags Off
# BEGIN Remove Last-Modified Header
<IfModule mod_headers.c>
Header unset Last-Modified
</IfModule>
# END Remove Last-Modified Header
<FilesMatch "\.(js|html|xhtml|text|txt|css|php)$">
SetOutputFilter DEFLATE
</FilesMatch>
________________________________________________
This is the Start-Page of USmessageboard.
You can optimize the images at Yahoo's "smush.it" without quality loss.
Also the images loaded from theme have no expiries set, meaning browsers load them every time.
In above .htacces it is covered.
LINK: Smush.it
or
PunyPNG - PNG Compression and Image Optimization - Gracepoint After Five

This is Yahoo-Yslow performance analysis of front-end of one of my websites:
100 is max.

The score for USmessageboard, I wont post.
I don't want to meddle in your things.
But with little work, you could optimize front-end load of website, like caching pictures and scripts, gzipping scripts.
Minimization of scripts and combining them to reduce DNS-lookups would need more "work".
From Yahoo:
Remember that 80-90% of the end-user response time is spent downloading all the components in the page: images, stylesheets, scripts, Flash, etc.
This is the Performance Golden Rule.
LINK: Yahoo - Best Practices for Speeding Up Your Web Site
You make 21 HTTP-requests on Front-Page.
Depending on each Users settings for paralell downloads in their browser-settings, this is - like Yahoo says - the area to achive most results in responsiveness of front-end.
That would need the HTTP-requests to decrease, which is achieved by combining the scripts which make the HTTP-requests.
P.S: Sorry for meddling in your business.
And I do not take any responsibilities, if you try something mentioned here.