<?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: Nico Salinas</title>
    <description>The latest articles on DEV Community by Nico Salinas (@nico-salinas).</description>
    <link>https://dev.to/nico-salinas</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%2F4256035%2Fb5519d9e-f534-4fd6-a860-6acc9e4de9e9.jpg</url>
      <title>DEV Community: Nico Salinas</title>
      <link>https://dev.to/nico-salinas</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nico-salinas"/>
    <language>en</language>
    <item>
      <title>Why the WooCommerce orders page gets slow with 100K orders (and what actually fixes it)</title>
      <dc:creator>Nico Salinas</dc:creator>
      <pubDate>Fri, 20 Nov 2026 16:06:47 +0000</pubDate>
      <link>https://dev.to/nico-salinas/why-the-woocommerce-orders-page-gets-slow-with-100k-orders-and-what-actually-fixes-it-5bb8</link>
      <guid>https://dev.to/nico-salinas/why-the-woocommerce-orders-page-gets-slow-with-100k-orders-and-what-actually-fixes-it-5bb8</guid>
      <description>&lt;p&gt;Your storefront is fast, but &lt;strong&gt;WooCommerce &amp;gt; Orders&lt;/strong&gt; takes ages to open, and searching an order by the customer's email never finishes. That pattern almost always points at the size of the order tables, not your theme or your hosting plan. The storefront is cached; the admin is not.&lt;/p&gt;

&lt;p&gt;I measured this on a test store with &lt;strong&gt;100,000 orders and 20,000 refunds&lt;/strong&gt;. Here is what I found.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, time three screens
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;The order list (first page, no filters).&lt;/li&gt;
&lt;li&gt;A search by customer email.&lt;/li&gt;
&lt;li&gt;Opening a single order.&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Slow&lt;/th&gt;
&lt;th&gt;Fast&lt;/th&gt;
&lt;th&gt;Likely cause&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;List and search&lt;/td&gt;
&lt;td&gt;Single order&lt;/td&gt;
&lt;td&gt;Legacy order storage (orders in &lt;code&gt;wp_posts&lt;/code&gt; / &lt;code&gt;wp_postmeta&lt;/code&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Search only&lt;/td&gt;
&lt;td&gt;List, single order&lt;/td&gt;
&lt;td&gt;Order volume&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Every admin screen&lt;/td&gt;
&lt;td&gt;Storefront&lt;/td&gt;
&lt;td&gt;A plugin running heavy queries in the admin&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Cause 1: legacy order storage
&lt;/h2&gt;

&lt;p&gt;Before WooCommerce 8.2, every order was a post and every field was a row in &lt;code&gt;wp_postmeta&lt;/code&gt;. Switching to &lt;strong&gt;High-Performance Order Storage (HPOS)&lt;/strong&gt; moves orders into proper tables with indexes: &lt;em&gt;WooCommerce &amp;gt; Settings &amp;gt; Advanced &amp;gt; Features&lt;/em&gt;. Test it on staging first; a few old extensions still read &lt;code&gt;wp_posts&lt;/code&gt; directly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cause 2: volume (HPOS doesn't fix this one)
&lt;/h2&gt;

&lt;p&gt;With HPOS on the 100K-order store, the list loaded in 0.8 s, but a search by email &lt;strong&gt;did not finish&lt;/strong&gt;: the server cut it at 40 s with a 500 error. Search still has to go through every order's addresses, items and meta.&lt;/p&gt;

&lt;p&gt;The fix is to keep only recent orders in the live tables. You can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Delete old orders.&lt;/strong&gt; Fast and permanent. You also lose the history that refunds, accounting and repeat-customer lookups rely on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Archive them.&lt;/strong&gt; Move completed and cancelled orders older than N months into archive tables in the same database, where they can still be searched, viewed and restored.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What archiving did on the test store
&lt;/h2&gt;

&lt;p&gt;I wrote a free plugin for the second option, &lt;strong&gt;OrderArc&lt;/strong&gt;. On the test store:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Archiving everything older than a year (about 96,000 orders) ran in the background in 11 minutes, with the order list still loading in 1.0-1.2 s during the run.&lt;/li&gt;
&lt;li&gt;After it, WooCommerce's own order search went from &lt;em&gt;never finishes&lt;/em&gt; to &lt;strong&gt;0.2 s&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;WooCommerce Analytics kept all its history, because the stats tables are never touched.&lt;/li&gt;
&lt;li&gt;Restoring everything and comparing every table against a fingerprint taken before: zero differences.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Archived orders stay visible in the admin (with search and one-click restore) and customers still see them under &lt;em&gt;My Account&lt;/em&gt;. It works with HPOS, with or without sync, and with legacy storage. Nothing leaves your database.&lt;/p&gt;

&lt;p&gt;It is on WordPress.org: &lt;a href="https://wordpress.org/plugins/orderarc/" rel="noopener noreferrer"&gt;OrderArc – Order Archive for WooCommerce&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What will not help
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Caching plugins.&lt;/strong&gt; The admin is never cached.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A bigger server.&lt;/strong&gt; It turns a 40-second search into a 20-second one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deleting products or images.&lt;/strong&gt; They live in different tables.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More detail (including how to spot cause 3 with Query Monitor) is in the guides at &lt;a href="https://getorderarc.com/guides/" rel="noopener noreferrer"&gt;getorderarc.com/guides&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: I'm the author of OrderArc.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>woocommerce</category>
      <category>wordpress</category>
      <category>mysql</category>
      <category>performance</category>
    </item>
    <item>
      <title>How to check if your WordPress plugins will break on PHP 8.4 (before your host upgrades you)</title>
      <dc:creator>Nico Salinas</dc:creator>
      <pubDate>Fri, 20 Nov 2026 16:06:00 +0000</pubDate>
      <link>https://dev.to/nico-salinas/how-to-check-if-your-wordpress-plugins-will-break-on-php-84-before-your-host-upgrades-you-cg8</link>
      <guid>https://dev.to/nico-salinas/how-to-check-if-your-wordpress-plugins-will-break-on-php-84-before-your-host-upgrades-you-cg8</guid>
      <description>&lt;p&gt;Hosting companies keep retiring old PHP versions. When yours moves a site from 7.4 or 8.1 to 8.3 or 8.4, the question is always the same: &lt;strong&gt;which plugin is going to take the site down?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You can find out before the switch. This is the short version of how.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tool most people find first is abandoned
&lt;/h2&gt;

&lt;p&gt;The plugin most people install for this, WP Engine's &lt;em&gt;PHP Compatibility Checker&lt;/em&gt;, has carried a "no longer actively maintained" notice on WordPress.org since 2023. It only checks code up to &lt;strong&gt;PHP 8.0&lt;/strong&gt; and was last tested with WordPress 6.4.&lt;/p&gt;

&lt;p&gt;So a plugin that breaks on PHP 8.2 or 8.4 can come out of it looking clean. That is worse than having no tool at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a useful scan has to tell you
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Breaks vs. deprecations.&lt;/strong&gt; A removed function stops the site with a fatal error. A deprecation only writes a line in the error log and keeps running. A report with 400 mixed findings is noise; you need to know which lines are fatal on the version you are moving to.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No false alarms for guarded code.&lt;/strong&gt; Code wrapped in &lt;code&gt;function_exists()&lt;/code&gt; or &lt;code&gt;version_compare( PHP_VERSION, ... )&lt;/code&gt; is already safe and should not be reported as a problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It has to finish on shared hosting.&lt;/strong&gt; WooCommerce alone is about 3,600 PHP files. A scan that runs in one request dies at the 30-60 second limit of shared hosts. It has to work in batches and resume.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your code stays on your server.&lt;/strong&gt; No &lt;code&gt;exec()&lt;/code&gt; (disabled on most managed hosts) and no uploading plugin code to an external service.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A free way to do it
&lt;/h2&gt;

&lt;p&gt;I built &lt;strong&gt;Upgravo&lt;/strong&gt; for exactly this, because I needed it for my own sites. It is free on WordPress.org:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Install it from &lt;strong&gt;Plugins &amp;gt; Add New&lt;/strong&gt; (search "Upgravo") or from &lt;a href="https://wordpress.org/plugins/upgravo/" rel="noopener noreferrer"&gt;wordpress.org/plugins/upgravo&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;Upgravo&lt;/strong&gt; in the admin menu, pick the PHP version you are moving to (8.1 to 8.5) and run the scan. It runs in short batches with a progress bar; you can close the tab and come back.&lt;/li&gt;
&lt;li&gt;Read the verdict per plugin and theme:

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Breaks&lt;/strong&gt;: fatal on the target version, with file and line.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Notices&lt;/strong&gt;: deprecated, still runs. Fix when you can.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hidden&lt;/strong&gt;: findings that do not apply (guarded code, or already true on your current PHP), with the reason.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;If something breaks, check whether the plugin has an update first. Usually the author already fixed it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It also flags the most common PHP 8.2 notice that the standard rule set misses: &lt;em&gt;Creation of dynamic property&lt;/em&gt;. There is a CSV export and a WP-CLI command (&lt;code&gt;wp upgravo scan&lt;/code&gt;) for scripted runs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What no scanner can do
&lt;/h2&gt;

&lt;p&gt;A scanner reads source code; it does not run it. Errors that depend on real data (a &lt;code&gt;null&lt;/code&gt; where a string was expected, for example) only show up when the code runs. So the safe order is: &lt;strong&gt;scan, fix what breaks, switch PHP on a staging copy, click through the site, then switch production.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A longer checklist, with the specific PHP 8.2-8.4 errors and how to read them, is on &lt;a href="https://phpready.com/guides/" rel="noopener noreferrer"&gt;phpready.com/guides&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: I'm the author of Upgravo.&lt;/em&gt;&lt;/p&gt;

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