<?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: Dirga Raj Lama</title>
    <description>The latest articles on DEV Community by Dirga Raj Lama (@lmdrga).</description>
    <link>https://dev.to/lmdrga</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%2F3926982%2F74547d5e-9f15-476d-80a6-ff87a1885181.jpg</url>
      <title>DEV Community: Dirga Raj Lama</title>
      <link>https://dev.to/lmdrga</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lmdrga"/>
    <language>en</language>
    <item>
      <title>Don’t Allow Your WordPress DB Performance Issues to Sabotage Your Page Speed</title>
      <dc:creator>Dirga Raj Lama</dc:creator>
      <pubDate>Wed, 01 Jul 2026 14:05:58 +0000</pubDate>
      <link>https://dev.to/lmdrga/dont-allow-your-wordpress-db-performance-issues-to-sabotage-your-page-speed-5bnm</link>
      <guid>https://dev.to/lmdrga/dont-allow-your-wordpress-db-performance-issues-to-sabotage-your-page-speed-5bnm</guid>
      <description>&lt;p&gt;In discussions around web performance optimization, the first things that come to mind are image optimization, minification, and edge caching. All good practices, but on a dynamic site or a high traffic one, the biggest hurdle to performance actually comes much closer to home - a cluttered database.&lt;/p&gt;

&lt;p&gt;Whenever a page is loaded, WordPress needs to do several queries to get options, content, and data from your database. Should your database be cluttered with digital dust from many years ago, your Time to First Byte (TTFB) will be slow no matter how fast your CDN is.&lt;/p&gt;

&lt;p&gt;Here are three database-level optimizations you should make today:&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Putting Post Revisions on a Tighter Leash
&lt;/h2&gt;

&lt;p&gt;By default, WordPress keeps every one of your revisions stored indefinitely. A 50-paragraph piece could easily end up filling 100 rows in the wp_posts table.&lt;br&gt;
Control this by putting a line in your wp-config.php:&lt;br&gt;
define( 'WP_POST_REVISIONS', 5 ); // Limits revisions to 5 per post&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Nuking Expired Transients&lt;br&gt;
Transients are a great way to cache API calls or heavy query results in the database. But once they expire, WordPress doesn't always clean them up automatically. Over time, millions of orphaned rows can collect in your wp_options table. Use a CLI command or a clean-up query to purge expired transients routinely.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Cleaning the wp_commentmeta and wp_usermeta Tables&lt;br&gt;
If you use plugins that track user behavior, store session tokens, or handle spam comments, these tables balloon quickly. Always ensure metadata is deleted when the parent comment or user is removed.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Database hygiene is just one piece of the puzzle, though. If you want a complete, step-by-step breakdown covering asset optimization, advanced caching strategies, and script management, check out the full guide:&lt;/p&gt;

&lt;p&gt;🔗 Read the complete deep-dive: &lt;a href="https://lamadirga.com.np/wordpress-performance-optimization/" rel="noopener noreferrer"&gt;Comprehensive Guide to WordPress Performance Optimization&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let's discuss: What's your go-to hidden trick for squeezing a sub-100ms TTFB out of a legacy WordPress site? Drop your favorite optimization strategies below!&lt;/p&gt;

</description>
      <category>database</category>
      <category>performance</category>
      <category>tutorial</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>How to Deploy a MERN App for Free in 2026</title>
      <dc:creator>Dirga Raj Lama</dc:creator>
      <pubDate>Sun, 21 Jun 2026 15:51:46 +0000</pubDate>
      <link>https://dev.to/lmdrga/how-to-deploy-a-mern-app-for-free-in-2026-3e21</link>
      <guid>https://dev.to/lmdrga/how-to-deploy-a-mern-app-for-free-in-2026-3e21</guid>
      <description>&lt;p&gt;🚀 I've just posted a comprehensive guide on setting up a free MERN application in 2026!&lt;/p&gt;

&lt;p&gt;Are you having trouble setting up your MERN app without any cost? Then this guide is what you need to get started with deployment using all the free services.&lt;/p&gt;

&lt;p&gt;Best for beginners, portfolio projects, and indie developers 👨‍💻&lt;/p&gt;

&lt;p&gt;Read here: &lt;a href="https://lamadirga.com.np/how-to-deploy-a-mern-app-for-free-in-2026/" rel="noopener noreferrer"&gt;https://lamadirga.com.np/how-to-deploy-a-mern-app-for-free-in-2026/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  webdev #mern #react #nodejs #mongodb #javascript #opensource #beginners
&lt;/h1&gt;

</description>
    </item>
    <item>
      <title>How I cut WooCommerce load times by 70% (A 2026 Case Study)</title>
      <dc:creator>Dirga Raj Lama</dc:creator>
      <pubDate>Tue, 12 May 2026 11:01:02 +0000</pubDate>
      <link>https://dev.to/lmdrga/how-i-cut-woocommerce-load-times-by-70-a-2026-case-study-1d7b</link>
      <guid>https://dev.to/lmdrga/how-i-cut-woocommerce-load-times-by-70-a-2026-case-study-1d7b</guid>
      <description>&lt;p&gt;Is your high-traffic online shop frustrating customers and costing you sales?&lt;/p&gt;

&lt;p&gt;A sluggish website in the competitive world of e-commerce is not just an inconvenience; it is a critical business failure. Recently, I worked with a client, “Himalayan Threads,” whose store took an average of 7.5 seconds to load. Their cart abandonment rate was over 60%.&lt;/p&gt;

&lt;p&gt;After a month of optimization, we brought that down to 1.8 seconds. Here is the exact technical checklist I used to fix their slow WooCommerce store.&lt;/p&gt;

&lt;p&gt;Original post: &lt;a href="https://lamadirga.com.np/how-to-fix-a-slow-woocommerce-store/" rel="noopener noreferrer"&gt;How to Fix a Slow WooCommerce Store&lt;/a&gt;&lt;/p&gt;

</description>
      <category>performance</category>
      <category>tutorial</category>
      <category>webdev</category>
      <category>wordpress</category>
    </item>
  </channel>
</rss>
