# Google Speed Test - Enable Compression

**URL:** <https://meta.discourse.org/t/google-speed-test-enable-compression/77305>\
**Category:** Product Support\
**Created:** [January 5, 2018, 11:20am UTC](https://meta.discourse.org/t/google-speed-test-enable-compression/77305 "2018-01-05T11:20:01Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 9, 2018, 2:32am UTC](https://meta.discourse.org/t/google-speed-test-enable-compression/77305/8 "2018-01-09T02:32:21Z")

</div>

This is some crazy banana level stuff:

> <https://stackoverflow.com/questions/33375304/what-are-the-options-for-the-gzip-proxied-directive-for/33448739#33448739>

I just enabled `gzip_proxied: any` in our template per:

[https://github.com/discourse/discourse/commit/18a929d801442643883531ea82c948c21d306e73](https://github.com/discourse/discourse/commit/18a929d801442643883531ea82c948c21d306e73)

NGINX _explicitly_ do not serve gzipped content to CDNs that send through a `Via` header (for dynamically compressed stuff)

The reason appears to be that:

> it is reasonable to compress responses only to requests that will not be cached on the proxy server

Now my guess here is that this is some sort of crazy scheme where they are

- Either trying to account for bad proxies sending bogus headers

- Or, are trying to save a handful of CPU cycles

Both reasons do not make sense to me so I am setting our template to something saner.

**EDIT** confirmed the fix, so closing.

---

_[View the full topic](https://meta.discourse.org/t/google-speed-test-enable-compression/77305)._