<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Htaccess on Kliku Kliku</title><link>https://klikukliku.dev/tags/htaccess/</link><description>Recent content in Htaccess on Kliku Kliku</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 20 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://klikukliku.dev/tags/htaccess/index.xml" rel="self" type="application/rss+xml"/><item><title>HTTP Server Optimization for Hugo: GZIP, Cache Headers, and Fingerprinting</title><link>https://klikukliku.dev/posts/hugo-server-optimization/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://klikukliku.dev/posts/hugo-server-optimization/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;We often focus on HTML minification or CSS bundling, treating it as the end of optimization. However, I&amp;rsquo;ve noticed that even the best-prepared files can load slowly if we forget about the HTTP server layer. That&amp;rsquo;s where untapped potential lies, worth exploring.&lt;/p&gt;
&lt;p&gt;In my practice, two configuration elements prove crucial. First, GZIP compression. From my experience, it can reduce text file sizes by sixty to seventy percent. Second, proper Cache headers. They eliminate unnecessary requests on subsequent user visits. Today I&amp;rsquo;ll show you how to configure a server for a Hugo-based site to squeeze maximum performance from static files.&lt;/p&gt;</description></item></channel></rss>