<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Images on Kliku Kliku</title><link>https://klikukliku.dev/tags/images/</link><description>Recent content in Images on Kliku Kliku</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 06 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://klikukliku.dev/tags/images/index.xml" rel="self" type="application/rss+xml"/><item><title>Hugo Image Processing: How I Reduced Page Size by 98%</title><link>https://klikukliku.dev/posts/hugo-image-optimization/</link><pubDate>Tue, 06 Jan 2026 00:00:00 +0000</pubDate><guid>https://klikukliku.dev/posts/hugo-image-optimization/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Images are usually the biggest obstacle to website performance. Although Hugo generates fast static sites by nature, unoptimized images can completely cancel out this advantage. I decided to investigate this using my own website as a case study.&lt;/p&gt;
&lt;p&gt;Analysis in Chrome DevTools clearly showed the source of the problem. Images made up 96% of the total transfer, adding up to nearly 15 MB. I identified three large PNG files that caused most of this traffic and increased the load time to over 4 seconds. For mobile users, this meant a long wait and wasted data.&lt;/p&gt;</description></item></channel></rss>