<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web-Performance on Lorbic</title><link>http://localhost:1313/tags/web-performance/</link><description>Recent content in Web-Performance on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 11 Apr 2026 16:00:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/web-performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical Rendering Path Optimization: 8 Proven Strategies to Boost Web Performance</title><link>http://localhost:1313/critical-rendering-path-optimization-8-proven-strategies-to-boost-web-performance/</link><pubDate>Sat, 11 Apr 2026 16:00:00 +0530</pubDate><guid>http://localhost:1313/critical-rendering-path-optimization-8-proven-strategies-to-boost-web-performance/</guid><description>&lt;p>&lt;strong>TL;DR:&lt;/strong> The Critical Rendering Path (CRP) is how browsers convert code into pixels. Optimizing it means reducing bottlenecks at five stages: Network, Parsing, Tree Building, Layout, and Paint. Use this guide to reduce First Contentful Paint by 40-60%, improve Lighthouse scores, and master the eight optimization strategies that separate fast sites from slow ones.&lt;/p>
&lt;p>To master web performance, stop guessing and start engineering. View the browser as a single-threaded virtual machine that must convert raw text into pixels 60 times per second. Every performance delay is a bottleneck in the &lt;a href="https://developer.mozilla.org/en-US/docs/Web/Performance/Critical_rendering_path" target="_blank" rel="noopener noreferrer">&lt;strong>Critical Rendering Path (CRP)&lt;/strong>&lt;/a>.&lt;/p></description></item><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></channel></rss>