<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: sagarbharvadiya1</title>
    <description>The latest articles on DEV Community by sagarbharvadiya1 (@sagarbharvadiya1).</description>
    <link>https://dev.to/sagarbharvadiya1</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4200835%2F260a616c-4122-4f12-9c8b-dc248d29d8d7.png</url>
      <title>DEV Community: sagarbharvadiya1</title>
      <link>https://dev.to/sagarbharvadiya1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sagarbharvadiya1"/>
    <language>en</language>
    <item>
      <title>How I cut a sales page’s LCP from 11.6s to 2.2s</title>
      <dc:creator>sagarbharvadiya1</dc:creator>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/sagarbharvadiya1/how-i-cut-a-sales-pages-lcp-from-116s-to-22s-27jc</link>
      <guid>https://dev.to/sagarbharvadiya1/how-i-cut-a-sales-pages-lcp-from-116s-to-22s-27jc</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fsagarbharvadiya.com%2Fblog%2Fhow-i-cut-lcp-from-11-6s-to-2-2s%2Fog" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fsagarbharvadiya.com%2Fblog%2Fhow-i-cut-lcp-from-11-6s-to-2-2s%2Fog" alt="How I cut a sales page’s LCP from 11.6s to 2.2s" width="1200" height="630"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A client was paying for traffic to a sales page that took 11.6 seconds to show its main content. Most visitors on mobile left before they saw the offer. The brief was simple: make it fast without changing the design.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Measure before touching anything
&lt;/h2&gt;

&lt;p&gt;I ran Lighthouse on a throttled mobile profile and checked the Core Web Vitals report. The Largest Contentful Paint element was the hero image, and it was waiting behind several render-blocking scripts.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Fix the LCP element first
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Served the hero in a modern format at the size it actually displays&lt;/li&gt;
&lt;li&gt;Preloaded it with high fetch priority&lt;/li&gt;
&lt;li&gt;Removed lazy-loading from above-the-fold images (a common mistake)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Get scripts out of the way
&lt;/h2&gt;

&lt;p&gt;Chat widgets, trackers and review badges were loading before the content. I deferred everything that isn’t needed for the first paint and moved some of it to load after user interaction.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Stop the page from jumping
&lt;/h2&gt;

&lt;p&gt;Images and embeds without dimensions were pushing content down as they loaded. Reserving space with width/height and aspect-ratio fixed CLS. Font swapping was tuned so text appears immediately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result
&lt;/h2&gt;

&lt;p&gt;LCP dropped from 11.6s to 2.2s and the Lighthouse performance score went from 65 to 97. Same page, same design. If your page is slow, send me the link and I’ll tell you the first three things I’d fix.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://sagarbharvadiya.com/blog/how-i-cut-lcp-from-11-6s-to-2-2s" rel="noopener noreferrer"&gt;sagarbharvadiya.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webperf</category>
      <category>nextjs</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Core Web Vitals explained: what LCP, INP and CLS mean (+ thresholds)</title>
      <dc:creator>sagarbharvadiya1</dc:creator>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/sagarbharvadiya1/core-web-vitals-explained-what-lcp-inp-and-cls-mean-thresholds-400d</link>
      <guid>https://dev.to/sagarbharvadiya1/core-web-vitals-explained-what-lcp-inp-and-cls-mean-thresholds-400d</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fsagarbharvadiya.com%2Fblog%2Fcore-web-vitals-explained-for-business-owners%2Fog" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fsagarbharvadiya.com%2Fblog%2Fcore-web-vitals-explained-for-business-owners%2Fog" alt="Core Web Vitals explained: what LCP, INP and CLS mean (+ thresholds)" width="1200" height="630"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Google measures how your pages feel to real visitors using three numbers called Core Web Vitals. They affect rankings, but more importantly they reflect whether visitors stay or leave.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 3 types of Core Web Vitals
&lt;/h2&gt;

&lt;p&gt;There are three Core Web Vitals, each measuring one part of how a page feels to a visitor:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;LCP (Largest Contentful Paint): loading. How fast the main content appears.&lt;/li&gt;
&lt;li&gt;INP (Interaction to Next Paint): responsiveness. How fast the page reacts to taps and clicks. It replaced FID in March 2024.&lt;/li&gt;
&lt;li&gt;CLS (Cumulative Layout Shift): visual stability. How much the layout jumps while loading.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is LCP in Core Web Vitals?
&lt;/h2&gt;

&lt;p&gt;Largest Contentful Paint is the time until the biggest thing on screen, usually a hero image or headline, is visible. Google wants it under 2.5 seconds. Common causes of slow LCP are huge images, slow servers and scripts that block the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is CLS in Core Web Vitals?
&lt;/h2&gt;

&lt;p&gt;Cumulative Layout Shift measures how much content moves while loading. You’ve felt it when you try to tap a button and an ad pushes it down. Google wants it under 0.1. It’s usually fixed by reserving space for images, embeds and banners.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is INP in Core Web Vitals?
&lt;/h2&gt;

&lt;p&gt;Interaction to Next Paint measures how quickly the page reacts when someone taps or clicks. Google wants it under 200 milliseconds. Heavy JavaScript, chat widgets and tracking scripts are the usual culprits.&lt;/p&gt;

&lt;h2&gt;
  
  
  Core Web Vitals thresholds (good, needs improvement, poor)
&lt;/h2&gt;

&lt;p&gt;These are Google’s official limits. A page passes when at least 75% of real visits (the 75th percentile) are in the “good” range, measured separately for mobile and desktop.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;LCP: good at 2.5 s or less, needs improvement up to 4 s, poor above 4 s&lt;/li&gt;
&lt;li&gt;INP: good at 200 ms or less, needs improvement up to 500 ms, poor above 500 ms&lt;/li&gt;
&lt;li&gt;CLS: good at 0.1 or less, needs improvement up to 0.25, poor above 0.25&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check yours in two minutes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Open PageSpeed Insights and paste your URL&lt;/li&gt;
&lt;li&gt;Look at the mobile tab first; that’s what most visitors use&lt;/li&gt;
&lt;li&gt;Real-user data at the top matters more than the lab score&lt;/li&gt;
&lt;li&gt;In Google Search Console, the Core Web Vitals report shows which pages fail&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What a fix looks like
&lt;/h2&gt;

&lt;p&gt;On one sales page I took LCP from 11.6s to 2.2s without changing the design, mostly by fixing how the hero image and third-party scripts loaded. Most sites have two or three issues causing most of the slowness.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://sagarbharvadiya.com/blog/core-web-vitals-explained-for-business-owners" rel="noopener noreferrer"&gt;sagarbharvadiya.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webperf</category>
      <category>nextjs</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
