Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author adeelkhan

    (@adeelkhan)

    Could you please verify that GZIP compression rules add to your .htaccess file?

    Thread Starter djeah

    (@djeah)

    @adeelkhan Yes, I see the following piece of code in the .htaccess file:

    <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>
    Plugin Author adeelkhan

    (@adeelkhan)

    The above code is not applied by Breeze. It means there are multiple plugins installed in your application for the same purpose. Could you please verify that the “Gzip compression” option enabled at Breeze also disable the plugins which serve the above-mentioned code in .htaccess file?

    Thread Starter djeah

    (@djeah)

    @adeelkhan Yes, this above code was added by Hummingbird Plugin last year, it’s been long since I uninstalled and deleted that plugin, but this value still remains in htaccess and no current plugin that I am using has any gzip compression options, but only Breeze, where it is enabled. So do you mean to say that Breeze did not add any gzip code to my htaccess till now? If not then how does it work to get it enabled?

    Plugin Author adeelkhan

    (@adeelkhan)

    It’s not difficult first you remove the Gzip compression rules which insert by your previous installed plugin then you will enable Gzip compression option by click on the option Gzip Compression under the Basic Options tab in Breeze.

    For the sake of confirmation, you can find the code .htaccess file after enabling Gzip Compression through Breeze

    Thread Starter djeah

    (@djeah)

    Hi @adeelkhan

    It seemed to me that I am using siteground and NGINX on top. Somehow GZIP rules being present in htaccess or not did not make any difference. I will test this today again. If not br is brotli and should be better than gzip I believe. So I am not much worried

    Thread Starter djeah

    (@djeah)

    I tested it. I see that breeze added the below code. However, I still see that the content-encoding is br :

    # Begin GzipofBreezeWPCache
    SetEnv BREEZE_GZIP_ON 1
    <IfModule mod_deflate.c>
    	AddType x-font/woff .woff
    	AddOutputFilterByType DEFLATE image/svg+xml
    	AddOutputFilterByType DEFLATE text/plain
    	AddOutputFilterByType DEFLATE text/html
    	AddOutputFilterByType DEFLATE text/xml
    	AddOutputFilterByType DEFLATE text/css
    	AddOutputFilterByType DEFLATE text/javascript
    	AddOutputFilterByType DEFLATE application/xml
    	AddOutputFilterByType DEFLATE application/xhtml+xml
    	AddOutputFilterByType DEFLATE application/rss+xml
    	AddOutputFilterByType DEFLATE application/javascript
    	AddOutputFilterByType DEFLATE application/x-javascript
    	AddOutputFilterByType DEFLATE application/x-font-ttf
    	AddOutputFilterByType DEFLATE application/vnd.ms-fontobject
    	AddOutputFilterByType DEFLATE font/opentype font/ttf font/eot font/otf
    </IfModule>
    # End GzipofBreezeWPCache

    @djeah Content encoding br means your server supports Brotli compression, which is a more recent alternative to gzip compression.

    https://hacks.mozilla.org/2015/11/better-than-gzip-compression-with-brotli/

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘JS and CSS not gzip enabled’ is closed to new replies.