Support

Please bear in mind that the .htaccess file you have found does not include front-end and back-end protection for Joomla!. It's best to nit-pick the additional features you want and add them as custom .htaccess code to be added at the top or bottom of the file.

Also bear in mind that you MUST NOT include sections of code which perform the same function as an existing .htaccess Maker feature. For example "Error prevention", "REWRITES", "Forcing `https://`", "Suppressing / Forcing the `www.` at the beginning of URLs", "File access", "Block access to all hidden files and directories", "Block access to files that can expose sensitive information", "HTTP Strict Transport Security (HSTS)", "Compression", "ETags", "Expires headers" will definitely conflict with .htaccess Maker. I've not tested the other sections, I can't tell you if they will work or not.

Some sections rely on Apache features which may be blocked by shared hosts. In this case your site will display an error 500 or blank page. Please do not request support for this situation :) Once you add custom code to the .htaccess Maker we can't provide support for it (unless "please remove all custom code first" sounds like a support option, because that's the first thing we'll ask you to do).

A word of caution: do not touch ETags, no matter what "site optimisation" tools tell you. Disabling ETags can have an adverse effect to browser-side caching of content which is not explicitly cached through mod_expires. This is the case on your site. Apparently your host doesn't have Apache's mod_expires installed / activated. In this case ETags are used for browser-side caching!

This is not all that bad. Using ETags is only bad if you use a server cluster to serve the same site. When I see Joomla! and WordPress guys obsess over ETags my reaction is mild annoyance. People, you are NOT using a server farm to host your small Joomla! / WordPress site. You are using a SHARED HOST. This means that you don't use a hundred servers to serve the same site, you use one hundreth of a single server. ETags are bad in the former case, indifferent (or useful, in the lac of mod_expires!) in the latter. Do NOT treat site optimisation as a competition. A higher score for a test designed for massive sites hosted on thousands of servers does not mean that it's better for your small site. It could be a waste of your time or worse. Educate yourself and think.

Speaking of which, for more information on ETags please read: https://developer.yahoo.com/blogs/ydn/high-performance-sites-rule-13-configure-etags-7211.html

Stop worrying, start reading ;)