WordPress powers 43% of the web. It’s also frequently blamed for slow sites — but slow WordPress sites are almost always a configuration problem, not a WordPress problem. A properly optimized WordPress site can score 95+ on PageSpeed Insights and load in under 1 second. Here’s how.
Don’t guess what’s slow. Use these tools to get a baseline:
Run tests from a cold cache (disable caching temporarily) to see your true baseline.
The single biggest performance lever is your hosting and server configuration. In order of impact:
LCP measures how quickly the largest visible element loads — usually a hero image or headline. Google’s Core Web Vitals threshold is under 2.5 seconds. To improve LCP:
<link rel="preload" as="image" href="hero.webp">CLS measures visual stability — elements that shift after initial render. Common causes in WordPress:
font-display: optional or preload fonts)INP replaced FID as a Core Web Vitals metric in 2024. It measures how quickly your page responds to user interactions — clicks, taps, keyboard input. Poor INP is almost always caused by excessive JavaScript on the main thread.
Audit with Chrome DevTools Performance Insights. Long tasks (>50ms) block the main thread. Break them up with scheduler.yield() or move work to Web Workers.
Render-blocking CSS delays the First Contentful Paint. Inline your critical CSS (above-the-fold styles) and load the rest asynchronously:
<link rel="preload" href="styles.css" as="style" onload="this.onload=null;this.rel='stylesheet'">For fonts, preload the specific weights you use and use font-display: swap to avoid invisible text during font load.
define('WP_POST_REVISIONS', 5); to wp-config.phpSELECT * FROM wp_options WHERE autoload = 'yes' ORDER BY LENGTH(option_value) DESC LIMIT 20; — large autoloaded options hurt TTFBA complete caching stack has four layers:
Layers 1 and 2 are server configuration. Layers 3 and 4 are plugin + CDN configuration. All four together produce the fastest possible WordPress response time.
Scoring 95+ on PageSpeed Insights is achievable on a well-configured WordPress site. The roadmap: fix your server stack, implement all four cache layers, optimize images, eliminate render-blocking resources, and audit your JavaScript. Each step produces measurable improvement.
Running a WooCommerce store? Also check out our guide on optimizing your shipping workflow — a fast store and a fast fulfillment process go hand in hand. Questions? Contact our team.
High-Performance Order Storage (HPOS) is the most impactful database improvement WooCommerce has shipped in years. Orders move from the overcrowded wp_posts and wp_postmeta tables into dedicated, indexed order tables — and the performance difference is dramatic. Here’s how to migrate safely.
Legacy WooCommerce stores every piece of order data — customer name, line items, shipping address, payment method, custom meta — in the generic WordPress post meta table. As your store grows, this table becomes enormous and queries slow down.
HPOS introduces dedicated tables: wc_orders, wc_order_items, wc_order_addresses, and wc_order_operational_data. These tables are purpose-built for order data with appropriate indexes, foreign keys, and query optimization. The result:
The most important step is verifying plugin compatibility. Any plugin that directly queries wp_posts or wp_postmeta for order data (instead of using WooCommerce’s order API) will break with HPOS.
WooCommerce provides a compatibility report under WooCommerce → Status → Features. Plugins that are HPOS-compatible declare compatibility explicitly. Check every active plugin before proceeding.
Well-maintained plugins have already added HPOS compatibility — the TheForge EasyPost Shipping plugin is fully HPOS-compatible and has been since the feature entered beta.
This is non-negotiable. Use your host’s backup tool, WP-CLI, or a plugin like UpdraftPlus to create a complete database backup immediately before migration. Store it somewhere outside your WordPress installation.
WooCommerce offers a Compatibility Mode that runs both the legacy post tables and the new HPOS tables in sync. Enable this first — it lets you test HPOS while keeping legacy data intact as a fallback.
Go to WooCommerce → Settings → Advanced → Features → Order Storage and select “WooCommerce orders tables (compatibility mode)”.
After enabling compatibility mode, WooCommerce will prompt you to run the data migration. This syncs your existing orders into the new HPOS tables. The migration runs in the background via Action Scheduler — for stores with 10,000+ orders, this may take several hours.
Monitor progress under WooCommerce → Status → Scheduled Actions. Don’t run other heavy batch operations while the migration is in progress.
With compatibility mode active, test every order-related workflow:
Once you’ve confirmed everything works correctly in compatibility mode, switch to HPOS-only: WooCommerce orders tables (recommended). This disables the legacy post table sync and runs purely on HPOS.
You’ll immediately notice faster order list loads and quicker bulk operations.
If something goes wrong after switching to HPOS-only, you can re-enable compatibility mode, which re-syncs from the HPOS tables back to legacy. If that fails, restore your pre-migration database backup.
For stores with 1,000+ orders, the performance improvement is immediately noticeable. For stores with 10,000+ orders, HPOS migration is essential — the alternative is a database that continues to degrade as you scale. Migrate now while your order volume is manageable rather than waiting until performance becomes a crisis.
Need help with the migration or plugin compatibility questions? Our support team is here to help.