https://klikukliku.dev/tags/css/Recent content in Css on Kliku KlikuHugoenTue, 03 Mar 2026 00:00:00 +0000https://klikukliku.dev/posts/cusdis-custom-styles/Tue, 03 Mar 2026 00:00:00 +0000https://klikukliku.dev/posts/cusdis-custom-styles/<h2 id="introduction">Introduction</h2> <p>I recently looked into implementing a comment system based on Cusdis. It&rsquo;s a lightweight and privacy-friendly solution, but it comes with a UI challenge: the widget renders inside an <code>iframe</code>.</p> <p>What does this mean for us? An iframe creates an isolated environment. The CSS styles we have in our project don&rsquo;t leak inside. As a result, if our layout has specific branding, the default, minimalist Cusdis design looks like a part of something else.</p>https://klikukliku.dev/posts/hugo-css-optimization/Tue, 13 Jan 2026 00:00:00 +0000https://klikukliku.dev/posts/hugo-css-optimization/<h2 id="introduction">Introduction</h2> <p>We often focus on optimizing JavaScript or images, while treating CSS styles as somewhat secondary. We assume that since individual files weigh just a few kilobytes, they&rsquo;re not a problem. But that&rsquo;s a false assumption. The way we deliver these files to the browser can have a crucial impact on how quickly users see the finished page.</p> <p>When I looked into Chrome&rsquo;s developer tools, I noticed a specific problem on my site. My page was loading fifteen separate CSS files. Combined, this generated a delay of around one point six seconds. Interestingly, the data size wasn&rsquo;t the issue at all. GZIP compression was working correctly and reducing file weight by over sixty percent. The real bottleneck turned out to be the sheer number of HTTP requests. The browser was wasting time establishing connections instead of downloading content.</p>