<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser on Vijay Pagare</title><link>https://www.vijaypagare.in/blog/browser/</link><description>Recent content in Browser on Vijay Pagare</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 31 Jul 2026 10:24:40 +0530</lastBuildDate><atom:link href="https://www.vijaypagare.in/blog/browser/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical Rendering Path: The Foundation of Web Performance [Part 1]</title><link>https://www.vijaypagare.in/blog/critical-rendering-path-the-foundation-of-web-performance-part-1/</link><pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.vijaypagare.in/blog/critical-rendering-path-the-foundation-of-web-performance-part-1/</guid><description>&lt;p>Most frontend performance problems arise due to lack of understanding of how the browser renders a page. When you deeply understand this process, you stop guessing what’s going wrong? You know why a page is slow, which part of the rendering pipeline is expensive, and which optimisation will actually make a difference.&lt;/p>
&lt;p>I&amp;rsquo;ve spent a fair amount of time debugging slow pages, improving Core Web Vitals, and chasing Lighthouse regressions. Almost every issue eventually led back to one thing: the browser&amp;rsquo;s rendering pipeline.&lt;/p></description></item></channel></rss>