Title: Critical Performance Issue – Duplicate SQL Queries Causing Admin Slowdown
Last modified: June 13, 2025

---

# Critical Performance Issue – Duplicate SQL Queries Causing Admin Slowdown

 *  [CyrilleC](https://wordpress.org/support/users/cyrillec/)
 * (@cyrillec)
 * [12 months ago](https://wordpress.org/support/topic/critical-performance-issue-duplicate-sql-queries-causing-admin-slowdown/)
 * Hello Packlink Support Team,
 * I’m experiencing a critical performance issue with the Packlink Pro Shipping 
   plugin on the WooCommerce Orders admin page.
 * **Environment Details**
    - **Plugin:** Packlink Pro Shipping 3.5.2
    - **WordPress Version:** 6.8.1
    - **WooCommerce Version:** 9.8.5
    - **PHP Version:** 8.1.32
    - **Server:** Apache
 * **Problem Description**
 * The WooCommerce Orders admin page (`/wp-admin/edit.php?post_type=shop_order`)
   is extremely slow, taking **over 7 seconds** to load with only 20 orders displayed.
 * **Root Cause Analysis**
 * Using Query Monitor, I’ve identified that your plugin is executing **identical
   SQL queries multiple times** for each order.
 * **Problematic Query:**
 *     ```wp-block-code
       SELECT * FROM wp_xxx_packlink_entity 
       WHERE type = 'OrderShipmentDetails' 
       AND ( index_1 = 'ORDER_ID') 
       LIMIT 0, 1
       ```
   
 * **Impact:**
    - Same query executed **10-15 times per order**
    - With 20 orders displayed = **200+ identical queries**
    - Each query takes ~0.02s = **4+ seconds just for duplicates**
 * **Code Location:**
 *     ```wp-block-code
       Packlink\WC\R\Base_Repository->select()
       Extension: packlink-pro-shipping
       ```
   
 * **Evidence**
 * I can provide:
    - Query Monitor screenshots showing duplicates
    - Complete query log with timing data
    - Performance metrics before/after modifications
 * **Business Impact**
 * This performance issue significantly affects:
    - Daily order management workflow
    - User experience for store administrators
    - Server resource consumption
 * **Request**
 * Please prioritize this optimization in your next update. The current implementation
   creates an exponential performance degradation as the number of orders increases.
 * I’m available to provide additional debugging information or test potential fixes.
 * **Thank you for your attention to this matter.**
 * Best regards,
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcritical-performance-issue-duplicate-sql-queries-causing-admin-slowdown%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  [Gerard Blanco](https://wordpress.org/support/users/sixaxis/)
 * (@sixaxis)
 * [11 months, 2 weeks ago](https://wordpress.org/support/topic/critical-performance-issue-duplicate-sql-queries-causing-admin-slowdown/#post-18530328)
 * [@packlink](https://wordpress.org/support/users/packlink/) could you please look
   into this and fix it?

Viewing 1 replies (of 1 total)

The topic ‘Critical Performance Issue – Duplicate SQL Queries Causing Admin Slowdown’
is closed to new replies.

 * ![](https://ps.w.org/packlink-pro-shipping/assets/icon-128x128.png?rev=3372347)
 * [Packlink PRO for WooCommerce](https://wordpress.org/plugins/packlink-pro-shipping/)
 * [Support Threads](https://wordpress.org/support/plugin/packlink-pro-shipping/)
 * [Active Topics](https://wordpress.org/support/plugin/packlink-pro-shipping/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/packlink-pro-shipping/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/packlink-pro-shipping/reviews/)

## Tags

 * [duplicate queries](https://wordpress.org/support/topic-tag/duplicate-queries/)
 * [sql](https://wordpress.org/support/topic-tag/sql/)

 * 1 reply
 * 2 participants
 * Last reply from: [Gerard Blanco](https://wordpress.org/support/users/sixaxis/)
 * Last activity: [11 months, 2 weeks ago](https://wordpress.org/support/topic/critical-performance-issue-duplicate-sql-queries-causing-admin-slowdown/#post-18530328)
 * Status: not resolved