<?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: Drake oakley</title>
    <description>The latest articles on DEV Community by Drake oakley (@drake_oakley_b113a491b36e).</description>
    <link>https://dev.to/drake_oakley_b113a491b36e</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%2F4196633%2F7718b652-7fd8-44c5-80d6-ef93ba2a3de5.jpg</url>
      <title>DEV Community: Drake oakley</title>
      <link>https://dev.to/drake_oakley_b113a491b36e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/drake_oakley_b113a491b36e"/>
    <language>en</language>
    <item>
      <title>Core Web Vitals in 2026: A Practical Checklist to Fix LCP, INP and CLS</title>
      <dc:creator>Drake oakley</dc:creator>
      <pubDate>Tue, 20 Oct 2026 17:18:55 +0000</pubDate>
      <link>https://dev.to/drake_oakley_b113a491b36e/core-web-vitals-in-2026-a-practical-checklist-to-fix-lcp-inp-and-cls-1n24</link>
      <guid>https://dev.to/drake_oakley_b113a491b36e/core-web-vitals-in-2026-a-practical-checklist-to-fix-lcp-inp-and-cls-1n24</guid>
      <description>&lt;p&gt;Google's Core Web Vitals directly affect how your pages feel to users, and they are part of the page experience signals used in search. Here is a practical checklist we use when auditing sites.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three metrics and their "good" thresholds
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;LCP (Largest Contentful Paint):&lt;/strong&gt; 2.5 seconds or less&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;INP (Interaction to Next Paint):&lt;/strong&gt; 200 milliseconds or less&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CLS (Cumulative Layout Shift):&lt;/strong&gt; 0.1 or less&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Measure them on real devices with PageSpeed Insights, the Chrome UX Report, and Lighthouse. Field data matters more than lab scores.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Fixing LCP
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Serve the hero image in WebP or AVIF and set explicit &lt;code&gt;width&lt;/code&gt; and &lt;code&gt;height&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Preload the LCP image and critical fonts:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel=&lt;/span&gt;&lt;span class="s"&gt;"preload"&lt;/span&gt; &lt;span class="na"&gt;as=&lt;/span&gt;&lt;span class="s"&gt;"image"&lt;/span&gt; &lt;span class="na"&gt;href=&lt;/span&gt;&lt;span class="s"&gt;"/hero.webp"&lt;/span&gt; &lt;span class="na"&gt;fetchpriority=&lt;/span&gt;&lt;span class="s"&gt;"high"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;Inline critical CSS and defer the rest.&lt;/li&gt;
&lt;li&gt;Use a CDN and server-side caching to reduce time to first byte.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Fixing INP
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Break up long JavaScript tasks (anything over 50ms) with &lt;code&gt;setTimeout&lt;/code&gt; or &lt;code&gt;scheduler.yield()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Remove unused third-party scripts. Chat widgets and tag managers are common offenders.&lt;/li&gt;
&lt;li&gt;Debounce expensive input handlers and avoid heavy work on the main thread.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Fixing CLS
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Always reserve space for images, ads and embeds.&lt;/li&gt;
&lt;li&gt;Use &lt;code&gt;font-display: swap&lt;/code&gt; with a well-matched fallback font.&lt;/li&gt;
&lt;li&gt;Never inject content above existing content after load.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A quick workflow
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Run PageSpeed Insights on your top 5 landing pages.&lt;/li&gt;
&lt;li&gt;Fix the worst metric first, usually LCP.&lt;/li&gt;
&lt;li&gt;Re-test after each change and track field data for 28 days.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Final thoughts
&lt;/h2&gt;

&lt;p&gt;Performance is not a one-time task. Small, measured improvements compound into better rankings, lower bounce rates and higher conversions.&lt;/p&gt;

&lt;p&gt;If you want a team to handle performance, custom web apps or technical SEO for you, take a look at &lt;a href="https://diginixit.com/" rel="noopener noreferrer"&gt;DiginixIT&lt;/a&gt;, a web engineering and digital growth agency in Pakistan.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>performance</category>
      <category>seo</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
