Search the Community
Showing results for tags 'gzip'.
Found 1 result
-
For nearly all of my projects I use SmartOptimizer (to minify CSS and JS resources) in combination with .htaccess rues (Gzip compression, expires headers, ETag removel etc.) of the HTML5 Boilerplate. This combination makes speed optimization pretty easy and effective. But there is still one thing Page Speed and YSlow criticize: The HTML page itself (i.e. the CMS output) is not compressed. Obviously the HTML5 Boilerplate .htaccess rules don’t apply here: # ---------------------------------------------------------------------- # Gzip compression # ---------------------------------------------------------------------- <IfModule mod_deflate.c> # Force deflate for mangled headers developer.yahoo.com/blogs/ydn/posts/2010/12/pushing-beyond-gzipping/ <IfModule mod_setenvif.c> <IfModule mod_headers.c> SetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X{15}|~{15}|-{15})$ ^((gzip|deflate)\s*,?\s*)+|[X~-]{4,13}$ HAVE_Accept-Encoding RequestHeader append Accept-Encoding "gzip,deflate" env=HAVE_Accept-Encoding </IfModule> </IfModule> # Compress all output labeled with one of the following MIME-types <IfModule mod_filter.c> AddOutputFilterByType DEFLATE application/atom+xml \ application/javascript \ application/json \ application/rss+xml \ application/vnd.ms-fontobject \ application/x-font-ttf \ application/xhtml+xml \ application/xml \ font/opentype \ image/svg+xml \ image/x-icon \ text/css \ text/html \ text/plain \ text/x-component \ text/xml </IfModule> </IfModule> Even if compressing HTML output is not that critical for speed optimization, it annoys me every time I see a Page Speed or YSlow report ;-) Does anyone know how to compress ProcessWire’s HTML output?
