As long as your webserver sets the proper Content-Encoding HTTP header it should work in all browsers that support SVG.
I haven’t tested this though. Do you have an environment where this isn’t working?
Also if your SVG files are big, then you should consider preprocessing them with SVG Scour or similar. It’s rather common to see vector graphics editors such as Illustrator and Inkscape output display-redundant data in the files — binary blobs or custom xml markup.
Note: Not all browser support SVGZ. Your HTTP server may probably compresses its response with deflate, which have the same performance.
Oh I saw your other post!
http://wordpress.org/support/topic/could-not-display-svg?replies=3%29
Glad you are squared away. I’ll close this out.
I would like support to SVGZ too :). I tried by replacing SVG by SVGZ in mimetype, but the sanitizer doesn’t seem to like it as that’s gziped.
An alternative could be to have the option to gzip SVG every time (eventually advertizing the user that don’t know that they need :
Thee mime type
* In apache and nginx, add in conf/mime.types :
image/svg+xml svg svgz
* To inform the browser that this kind of file is compressed by default (that’s the case in apache by default, at least after a bug report I made ~5~10 years ago).
* In apache : AddEncoding gzip svgz
* In nginx :
location ~* \.(svgz)$ {
add_header Content-Encoding gzip;
break;
}
