<?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 Pragati Rithekar on Medium]]></title>
        <description><![CDATA[Stories by Pragati Rithekar on Medium]]></description>
        <link>https://medium.com/@pragati.s.rithekar?source=rss-230bd53b5411------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FcGJ8eQJnmBN5aP6gWw0-A.jpeg</url>
            <title>Stories by Pragati Rithekar on Medium</title>
            <link>https://medium.com/@pragati.s.rithekar?source=rss-230bd53b5411------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:05:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pragati.s.rithekar/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[Hey Browser — What’s your priority?]]></title>
            <link>https://medium.com/globant/hey-browser-whats-your-priority-1fbe5db71d23?source=rss-230bd53b5411------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fbe5db71d23</guid>
            <category><![CDATA[resource-prioritisation]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[resource-hints]]></category>
            <category><![CDATA[fast-browser]]></category>
            <dc:creator><![CDATA[Pragati Rithekar]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 12:46:32 GMT</pubDate>
            <atom:updated>2020-10-03T13:11:50.590Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hey Browser — What’s your priority?</h3><p>Browser resource prioritization — How can it increase web performance?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QjGETaoOA1hX_-9jbESLtw.png" /></figure><p>The website performance — Hasn’t this been a big deal for every project that you have worked upon. The reason is simple — The user wants everything in a blink of an eye. A website performance affects the conversion rate(<em>A website’s conversion rate is the percentage of users who take the desired action, and the conversion rate is tied directly to how much revenue a website generates</em>). Below are a few examples of how an increase in performance is tied with conversion rates. <a href="https://www.cloudflare.com/en-ca/learning/performance/why-site-speed-matters/">Source</a></p><ul><li>Mobify found that decreasing their homepage’s load time by 100 milliseconds resulted in a 1.11% uptick in session-based conversion</li><li>Retailer AutoAnything experienced a 12–13% increase in sales after cutting page load time in half</li><li>Walmart discovered that improving page load time by one second increased conversions by 2%</li></ul><p>As a result, loads of money is spent on increasing the performance of a website to get higher conversion rates.</p><p>However, what if there were some small techniques through which you could increase your website performance without having to spend anything? There are a few amenities that the browser has given the developer to gain more control over how and when resource loading is done.</p><h3>Browser resource prioritization — the deal!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQuPib3t-znAyVJHw35K5w.png" /><figcaption>Browser resource prioritization</figcaption></figure><p>When the webserver returns the asked HTML back to the browser, the browser has its own heuristics that are responsible for the best-guess on which of the resources are important so as to load them first. E.g., CSS will always be loaded before scripts or images. However, you have ways through which you can influence this decision making of the browser.</p><p>These are known as <strong><em>resource hints</em></strong>. The following are the resource hints we will be exploring in this article.</p><ul><li><strong>Preload</strong></li><li><strong>Prefetch</strong></li><li><strong>Preconnect</strong></li></ul><p>All these resource hints use the <strong>rel</strong> attribute of the <strong>link</strong> element in an HTML. So let’s explore them in detail.</p><h3><strong>PRELOAD</strong></h3><p>Preload is a declarative fetch directive. This priority hint allows you to compel the browser to make a request for a certain resource without blocking the onload event of the window. It is a way of letting the browser know that a certain resource is going to be needed soon for sure.</p><p>Preload ensures the resources specified with this priority hint are available earlier and are less likely to block the page’s render, ultimately improving performance.</p><p>How does this work?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FCPskAi4C6WLHa%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FCPskAi4C6WLHa%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FCPskAi4C6WLHa%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="198" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc3da9e2d0fc3141c59d893d7625df24/href">https://medium.com/media/cc3da9e2d0fc3141c59d893d7625df24/href</a></iframe><pre>&lt;link rel=&quot;preload&quot; href=&quot;myStyles.css&quot; as=&quot;style&quot;&gt;</pre><p>Let’s see the attributes used above,</p><ul><li><strong>rel</strong> attribute gives the power to preload to the <strong>link</strong> directive.</li><li>We specify the resource destination in the <strong>href</strong> attribute.</li><li><strong>as</strong> is used to specify the resource type.</li></ul><p>The <strong>as </strong>an attribute has multiple available values like — audio, font, image, script, video, worker, track, script, embed.</p><p>When should you use PRELOAD?</p><p>Preload tells the browser to download and cache a resource (like a script or a stylesheet) as soon as possible. It’s helpful when you need that resource a few seconds after loading the page, and wish to speed it up. The browser does not work on the downloaded resource. Below are the scenarios where it can be helpful.</p><ul><li>Early loading of fonts</li><li>Dynamic loading without execution</li><li>Responsive loading</li></ul><p>What are a few things we need to take care of when using PRELOAD?</p><ul><li><strong>&lt;link&gt;</strong> elements can accept a <strong>type</strong> attribute, which contains the MIME type of the resource the element points to. This is especially useful when preloading resources — the browser will use the type attribute value to work out if it supports that resource, and will only download it if so, ignoring it if not.</li><li>Make sure you are ultimately using the resource that is loaded using PRELOAD. Else, your browser will start throwing an error as below,</li></ul><pre><em>The resource </em><a href="https://pl.***.com/wp-includes/%E2%80%A6(.css"><em>https://***.com/…(.css</em></a><em>, .js) was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it has an appropriate ‘as’ value and it is preloaded intentionally.</em></pre><h3>PREFETCH</h3><pre>&lt;link rel=&quot;prefetch&quot; href=&quot;MyImage.jpeg&quot; as=&quot;image&quot;&gt;</pre><p>When you can confidently identify a resource the user is likely to navigate to later in time, you can use the prefetch browser hint to load the page ahead of time. This technique relies on fetching the resource in the background and having either the browser cache or even service worker cache to persist the request. This way, the network request for that resource is bypassed when the navigation occurs.</p><p>PREFETCH tells the browser that it can go ahead and fetch a page in the background so that it’s ready to go when requested. There’s a bit of a catch here because you have to anticipate where you think the user will navigate next. If your anticipation is correct, the next page might appear to load really fast. It goes wrong, and you’ve wasted time and resources in downloading something that isn’t going to be required at all. If the user is on a metered connection like a limited mobile phone plan, it might actually cost them money.</p><p>When a prefetch takes place, the browser does the DNS lookup and makes the server connection. It then goes a step further and requests and downloads the files. Now, it stops at this point. The files are not parsed or executed. They’re just requested and kept ready-to-go.</p><p>You might think of PREFETCH as being a bit like adding a file to the browser’s cache. Instead of needing to go out to the server and download it when the user clicks the link, the file can be pulled out of memory and used much faster.</p><p>But, when should you use it?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FfUwOs80ja3sTPpjndh%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FfUwOs80ja3sTPpjndh%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FfUwOs80ja3sTPpjndh%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/73f51223774a1f13b523956bb1986181/href">https://medium.com/media/73f51223774a1f13b523956bb1986181/href</a></iframe><p>You should use it when you have a reasonable amount of certainty of where the user navigates on your site. Also, if you believe that speeding up the navigation will positively impact your user’s experience. This should be weighed against the risk of wasting resources by possibly fetching a resource that isn’t then used.</p><h3>PRECONNECT</h3><pre>&lt;link rel=&quot;preconnect&quot; href=&quot;https://my.sample.com&quot;&gt;</pre><p>Why PRECONNECT?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fgd09Y2Ptu7gsiPVUrv%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fgd09Y2Ptu7gsiPVUrv%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZGhyMXZyNTExYzNtN2lkZjd3eXA1ejFteXR1ajJ4MWRwYXdxZGU1dSZlcD12MV9naWZzX2dpZklkJmN0PWc%2Fgd09Y2Ptu7gsiPVUrv%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="246" frameborder="0" scrolling="no"><a href="https://medium.com/media/7d52f7be7a01f2ae7e6dd26bcff63dc9/href">https://medium.com/media/7d52f7be7a01f2ae7e6dd26bcff63dc9/href</a></iframe><p>One step on from DNS prefetching is <em>preconnecting</em> to a server. Establishing a connection to a server and hosting a resource takes several steps:</p><ul><li><strong>DNS lookup</strong></li><li><strong>TCP handshake</strong></li><li><strong>TLS negotiation on HTTPS sites</strong></li></ul><p>This typically happens once per server and takes up a valuable amount of time — especially if the server is very far from the browser and network latency is very high. Pre-connecting to a server can make sure that when the browser gets to the part of the page where a resource is needed, the slow work of establishing the connection to that server has already taken place and the line is open and ready to go.</p><p>OK! So, when should you use PRECONNECT?</p><p><a href="https://caniuse.com/?search=preconnect">Browser support is pretty good</a> and there’s no harm if a browser doesn’t support PRECONNECT — there will be no change in the experience. Consider using PRECONNECT when you are sure that you will be using a resource and you want to be prepared by being ready in advance.</p><p>As was the case in PREFETCH, be careful not to PRECONNECT and then not use the connection. This will slow your page as well as tie up a tiny amount of resources on the server you connect to.</p><h3><strong>Closing Thoughts</strong></h3><p>It’s important to remember that these hints are just that; hints of <strong>ways the browser could optimize performance</strong>. They’re not commands. The browser takes these suggestions and uses its best judgment in deciding how to respond.</p><p>This might mean that on a busy or overloaded device, the browser doesn’t attempt to respond to the hints at all.</p><p>However, there is also a risk associated with resource hints. As the code is undercover and goes undetected, it could be very easy for the page to change in the future without updating the resource hints which might have become irrelevant.</p><p>So, use them wisely!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fbe5db71d23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globant/hey-browser-whats-your-priority-1fbe5db71d23">Hey Browser — What’s your priority?</a> was originally published in <a href="https://medium.com/globant">Globant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jamming away with JAMstack]]></title>
            <link>https://medium.com/globant/jamming-away-with-jamstack-4e702947a217?source=rss-230bd53b5411------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e702947a217</guid>
            <category><![CDATA[modern-way-of-webapps]]></category>
            <category><![CDATA[what-is-jamstack]]></category>
            <category><![CDATA[performant-webapps]]></category>
            <category><![CDATA[jamstack]]></category>
            <dc:creator><![CDATA[Pragati Rithekar]]></dc:creator>
            <pubDate>Mon, 21 Sep 2020 13:31:10 GMT</pubDate>
            <atom:updated>2020-09-21T13:31:10.282Z</atom:updated>
            <content:encoded><![CDATA[<p>The modern way of building web apps</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOpNR4SysBXTHbpIpTHjkQ.jpeg" /></figure><p>Modern Web Development — The place to be today! This requires you to think differently, bring innovation into play, and ultimately — think smart! For this, we need to move away from the traditional way of building websites i.e., using a web server. Sites built this way needlessly slow things down, provide way too many opportunities for an attack, and are often expensive to scale.</p><p>Wait! Did you read it right? A website without a web server? Sounds weird?</p><p>NO, it is not! This is where JAMstack comes in.</p><p>Although, why would you need to move away from the traditional way of building websites with a server? Let’s have a look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*ce7dlqm7UFcqgVqjZq3EaQ.jpeg" /></figure><p>The above scenario seems pretty neat, right? Why change it? Hold on. Now try using this for a website that would get a lot of hits. The server would crash unless we provide it some help. Enter — Load Balancer! They act as a reverse proxy and distribute network or application traffic across multiple web servers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*35o9qPZ6XCn15rEovyb7rA.jpeg" /></figure><p>Umm. Still doing good. Then we all thought — Maybe there are some assets that are static in the web app and don&#39;t need to do the roundabout from the server. And we thought of putting those on a different location like a CDN!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*3TWcXi8DJ1Vd1KyfOgqp8w.jpeg" /></figure><p>OK! So now we have multiple web servers to handle the traffic and we put in a load balancer in front of them to share the load. We also started abstracting where the data lived. So now the DB servers share the load with the data that is specific to it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FcnuQwZ8IFLDZFwreWF%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FcnuQwZ8IFLDZFwreWF%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FcnuQwZ8IFLDZFwreWF%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="436" frameborder="0" scrolling="no"><a href="https://medium.com/media/5aa970e59b605ef2bcd2bcc9e3c2fc29/href">https://medium.com/media/5aa970e59b605ef2bcd2bcc9e3c2fc29/href</a></iframe><blockquote>JAMstack happens to be one of the multiple solutions present out there to handle this scenario.</blockquote><p>JAMstack projects neatly separate the frontend pages and UI from the backend apps and databases. Freed from backend servers, the frontend can then be deployed globally, directly to a CDN. That’s right, a CDN!</p><blockquote>Now, you must be thinking, one more library/framework to learn.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fd10dMmzqCYqQ0%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fd10dMmzqCYqQ0%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fd10dMmzqCYqQ0%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/38c4809bd0519b9d984812029d29e0f7/href">https://medium.com/media/38c4809bd0519b9d984812029d29e0f7/href</a></iframe><p>Hold on! JAMstack doesn’t change the technologies you use — JAMstack sites can be built in Javascript, PHP, Ruby, Python, React, Vue, or virtually any language. It’s not a collection of specific software, it’s a set of best practices.</p><p>JAMstack is a modern way of building websites &amp; web apps.</p><p>What’s in the “J-A-M”, you may ask? It stands for:</p><p><strong>JavaScript</strong>: Any dynamic programming during the request/response cycle is handled by JavaScript, running entirely on the client.</p><p><strong>APIs</strong>: All server-side functions or database actions are abstracted into reusable APIs, accessed over HTTPS with JS. Be it SaaS, third-party services, or custom-built.</p><p><strong>Markup</strong>: Templated markup should be prebuilt at build time, usually using a site generator for content sites, or a build tool for web apps.</p><p>Ok, enough of the hype — Let’s see the real deal now!</p><blockquote>How does JAMstack work?</blockquote><p><strong><em>Code development &amp; deployment</em></strong></p><p>The traditional way — Developer completes a website development and ships it to a web server.</p><p>The JAMstack way — Developer uses a Static Site Generator to produce pages and assets. She then ships the built files to CDN. So, before deployment, the entire front end is prebuilt into highly optimized static pages and assets.</p><p><strong><em>Request for a web page from the client</em></strong></p><p>The traditional way — The Server goes through a series of interactions between the browser, layers of caching, server, back-end code and produces the HTML requested.</p><p>The JAMstack way — The CDN provides the pre-built files on demand.</p><p><strong><em>Updates</em></strong></p><p>The traditional way — Core updates are pushed to production servers, often through FTP. The database must be maintained or updated.Content updates are pushed through traditional CMS, like WordPress or Drupal.</p><p>The JAMstack way — Core updates are pushed through Git; the site gets re-built entirely via modern build tools like static site generators. Content updates are pushed through Git or a static site CMS.</p><blockquote><strong>How is JAMstack beneficial?</strong></blockquote><ul><li><strong><em>More secure. </em></strong>Server-side and database are delegated which reduces failures and surface areas for attacks.</li><li><strong><em>Cheaper scaling.</em></strong> Cost automatically reduces owing to the lesser complexity during development.</li><li><strong><em>Performant.</em></strong> The user experience is super speedy as the static content is served via CDN.</li><li><strong><em>Happy developer.</em></strong> The reduction of bloat &amp; maintenance + refreshing flexibility in workflows diminishes depression and alcoholism among developers. :)</li></ul><p>It’s not a collection of specific software, it’s a set of best practices that combines:</p><h4>GIT WORKFLOWS</h4><p>The JAMstack ties deployments closely to a Git-based workflow. Git brings the rigor and safety of version control to web projects allowing support for large projects with numerous contributors.</p><h4>MODERN BUILD TOOLS</h4><p>With a build run every time a deploy happens, The JAMstack brings full support for linting code, transpiling javascript, compiling CSS, and optimizing HTML and assets.</p><h4>CDN TECHNOLOGY</h4><p>First deployed by large enterprises, the JAMstack democratizes the use of CDN technology to deliver web content from endpoints as close to users as possible.</p><blockquote>Is JAMstack the silver bullet?</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FgnE4FFhtFoLKM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FgnE4FFhtFoLKM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FgnE4FFhtFoLKM%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/3b64e69c20806f44be197532ad746d35/href">https://medium.com/media/3b64e69c20806f44be197532ad746d35/href</a></iframe><h3>When should you not consider JAMstack?</h3><p>Any project that relies on a tight coupling between client and server cannot be built with the JAMstack. This would include:</p><ul><li>A site built with a server-side CMS like WordPress, Drupal, Joomla, or Squarespace.</li><li>A monolithic server-run web app that relies on Ruby, Node, or another backend language.</li><li>A single-page app that uses isomorphic rendering to build views on the server at runtime.</li></ul><h3>Closing Thoughts</h3><p>Like mentioned earlier, JAMstack is not about specific technologies. It’s a new way of building websites and apps that delivers better performance, higher security, lower cost of scaling, and better developer experience. Worth giving a thought!</p><p><em>Keep on reading, keep on exploring. You never know which thought/idea would change your life!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e702947a217" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globant/jamming-away-with-jamstack-4e702947a217">Jamming away with JAMstack</a> was originally published in <a href="https://medium.com/globant">Globant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>