<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ankit Singhal on Medium]]></title>
        <description><![CDATA[Stories by Ankit Singhal on Medium]]></description>
        <link>https://medium.com/@ankit-singhal?source=rss-758ba2eb8d49------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*v3ege_QSG_hcjpyp60RegQ.png</url>
            <title>Stories by Ankit Singhal on Medium</title>
            <link>https://medium.com/@ankit-singhal?source=rss-758ba2eb8d49------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:48:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ankit-singhal/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Enabling Performance Continuous Delivery]]></title>
            <link>https://ankit-singhal.medium.com/enabling-performance-continuous-delivery-3eda34b2a074?source=rss-758ba2eb8d49------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eda34b2a074</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[web-performance]]></category>
            <dc:creator><![CDATA[Ankit Singhal]]></dc:creator>
            <pubDate>Fri, 09 Nov 2018 16:55:51 GMT</pubDate>
            <atom:updated>2018-11-12T09:36:23.126Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“Infuse your life with action. Don’t wait for it to happen. Make it happen. Make your own future.” <br>- </em>Bradley Whitford</blockquote><p>Similarly, why wait till performance issues start cropping up in production. Below framework will highlight each step taken at different development stages to alleviate performance issues as much as possible and as early as possible.</p><h3>Why Continuous Performance?</h3><p>Optimized website performance directly improves the user experience and increases engagement and brand loyalty. This translates into better conversion rates and greater profitability.</p><p>With increased needs to offer rich customer experiences to consumers, websites have evolved to an extent where <strong>70–80% of the time</strong> is spent on frontend processing and rendering. This increases the importance of frontend performance tuning significantly than it used to be.</p><p>If you are building a web application and concerned about your <em>conversion</em>, <em>revenues</em>, and <em>performance</em>, this framework will help you in setting up tools and the processes across different stages in development lifecycle covering the following points:</p><ul><li>Pre-defined rule-based performance metrics</li><li>Automated performance checks at <em>developer box</em> to monitor budgets for quantity based metrics</li><li>Integrate with continuous <em>integration environments</em> to raise alerts based on performance criteria</li><li><em>Performance monitoring</em> at different development stages</li><li>Pre-defined framework for analyzing <a href="https://en.wikipedia.org/wiki/Real_user_monitoring">RUM</a> reports from production</li></ul><p>With this framework one thing is most important is the performance budgeting and categorized into the following metrics:</p><p><strong>Speed/Milestone timings</strong>: e.g. Time to Interactive, First Meaningful Paint time, SpeedIndex. These metrics are used to track the user experience and perceived performance.</p><p><strong>Quantity-based metrics</strong>: e.g. Total Number of Requests, Overall Page Weight, Total Image/CSS/JS Weight. To enable to take decisions about what goes on the page/browser.</p><p><strong>Rule-based metrics</strong>: PageSpeed Score, YSlow Score, Critical Rendering Path Score. To make sure that we are not overlooking simple optimizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpZ63JcniEcaTcSxuXKcaQ.png" /></figure><p>To learn more about performance budgeting a detailed <a href="https://medium.com/@addyosmani/start-performance-budgeting-dabde04cf6a3">post</a> by <a href="https://medium.com/u/2508e4c7a8ec">Addy Osmani</a> and about Performance Budget Metrics by <a href="https://timkadlec.com/2014/11/performance-budget-metrics/">Tim Kadlec</a></p><h3>The Workflow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*AiSbeerzlpXI7VkGqpQiwQ.png" /><figcaption>The Workflow for Continous Performance Delivery</figcaption></figure><p>At each stage, the framework suggests using different tools which are more useful for the purpose:</p><p>A Stage: Use tools like <a href="https://www.sitespeed.io/">sitespeed.io</a> or <a href="https://developers.google.com/web/tools/lighthouse/">lighthouse</a> which can be easily integrated and setup for a developer box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bv87_m2p3SDUWnuuKHetsQ.png" /><figcaption>Sample HTML Report reference: <a href="https://www.sitespeed.io/examples/">sitespeed.io</a></figcaption></figure><p>B Stage: Use tools similar to Stage A which will be integrated with your CI/CD pipelines and also the milestone rules will help with better monitoring of application performance using dashboards or during the builds itself after each build deployed on different environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86wE5q5l_CgAzrc7e5Firw.png" /><figcaption>Sample Dashboard reference: <a href="https://www.sitespeed.io/examples/">sitespeed.io</a></figcaption></figure><p>CStage: Again use tools like Stage A and B to get early feedback performance after each production deployment but a Real-Time Monitoring tool is also necessary which can provide you the live feedback about the performance of your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8BNHyGja2PVHnU-DCrSopg.png" /><figcaption>RUM Monitoring reference <a href="https://www.dynatrace.com/">Dynatrace</a></figcaption></figure><h3>Wrapping up…</h3><p>That’s if for now, until next time… but do remember:</p><blockquote>Don’t trust performance tips, make sure you test it</blockquote><p>For any questions on this article ping me or reach me on Twitter <a href="https://twitter.com/dreamzmaster">@dreamzmaster</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eda34b2a074" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>