<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hugo on Lorbic</title><link>http://localhost:1313/tags/hugo/</link><description>Recent content in Hugo on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 11 Apr 2026 14:30:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>A Tale of Web Vitals</title><link>http://localhost:1313/a-tale-of-web-vitals/</link><pubDate>Sat, 11 Apr 2026 14:30:00 +0530</pubDate><guid>http://localhost:1313/a-tale-of-web-vitals/</guid><description>&lt;p>&lt;strong>TL;DR:&lt;/strong> I achieved 95+ Lighthouse scores by removing abstractions and automating browser fundamentals. This guide details how to solve &lt;strong>LCP network discovery&lt;/strong>, &lt;strong>main thread congestion&lt;/strong>, and &lt;strong>third-party accessibility traps&lt;/strong> using Hugo pipelines and vanilla JavaScript.&lt;/p>
&lt;hr>
&lt;p>&amp;ldquo;Why is the LCP 4.2 seconds? It&amp;rsquo;s just a static site&amp;rdquo;.&lt;/p>
&lt;p>I was staring at a Lighthouse report that felt like an insult. &lt;strong>Lorbic.com is a zero-dependency Hugo site.&lt;/strong> No React, no heavy frameworks, just vanilla CSS and minimal JS. Yet, the mobile performance was tanking.&lt;/p></description></item><item><title>10 years of lorbic.com architecture</title><link>http://localhost:1313/10-years-of-lorbic.com-architecture/</link><pubDate>Thu, 02 Apr 2026 12:00:00 +0530</pubDate><guid>http://localhost:1313/10-years-of-lorbic.com-architecture/</guid><description>&lt;p>&lt;picture class="optimized-image-container">&lt;source srcset="http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_c3df73cc291f2d3a.webp 480w, http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_d6eb9db6213c4dc9.webp 800w, http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_156b083258cf7313.webp 1200w, http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_abf66fd5579991cd.webp 3068w" sizes="(max-width: 800px) 100vw, 800px" type="image/webp">&lt;img src="http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_abf66fd5579991cd.webp" width="3068" height="800" alt="Lorbic Evolution: 2017 vs 2026" loading="eager" decoding="async" fetchpriority="high" class="img-fluid" />
 &lt;/picture>&lt;/p>
&lt;p>This post tracks four architectural rewrites of my personal site over ten years: moving from managed platforms (Blogger) to dynamic backends (Django), static site generators (Jekyll/Hugo), and finally to a custom, zero-dependency architecture built for absolute control and performance.&lt;/p>
&lt;hr>
&lt;h2 id="technical-context">Technical Context&lt;a class="anchorjs-link" href="#technical-context" aria-label="Link to section: Technical Context">&lt;/a>&lt;/h2>&lt;p>For an engineer, a personal site is the only project where you have absolute authority over the stack. There are no product managers, no legacy constraints, and no enterprise technical debt: you own the metal.&lt;/p></description></item></channel></rss>