Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WooCommerce Not Loading: Causes and How to Fix It

WooCommerce Not Loading: Causes and How to Fix It

Short answer

WooCommerce usually stops loading because PHP runs out of memory or time, a plugin or theme conflict breaks pages, the REST API is blocked, caching serves broken scripts, or the database is overloaded. Read the debug log first, then test conflicts on staging.

Key takeaways

  • Identify whether store pages or admin screens fail.
  • The debug log usually names the failing plugin.
  • WooCommerce needs more PHP memory than a blog.
  • Admin screens depend on a working REST API.
  • Never cache cart, checkout or account pages.
  • Clear past-due scheduled actions to cut load.

Why is WooCommerce not loading?

WooCommerce usually stops loading because the server runs out of PHP memory or time, a plugin or theme conflict breaks a page, the REST API is blocked, caching serves broken files, or the database is slow or overloaded.

“Not loading” can mean several different things. Pin down which one you have before changing anything:

  • Shop or product pages load forever, show a blank screen or a critical error.
  • The cart or checkout block shows a spinner that never finishes.
  • WooCommerce admin pages, such as Home, Orders or Analytics, stay stuck on loading.
  • The whole WooCommerce menu is missing from the dashboard.

Each one points to a different layer. This guide covers them in order, starting with the quickest checks.

If WooCommerce loads but behaves strangely, our broader guide on WooCommerce not working properly may be a better fit.

What are the common causes at a glance?

Most cases fall into a handful of patterns, so matching your symptom saves time and avoids risky changes on a live store.

SymptomLikely causeFirst fix
Blank page or critical errorPHP fatal error or memory limitCheck error log, raise memory
Pages load very slowly then time outSlow database or heavy pluginCheck slow queries and Action Scheduler
Admin pages spin foreverREST API blocked or JavaScript errorTest REST API, check console
Cart or checkout block spinsCached scripts or blocked APIExclude store pages from cache
WooCommerce menu missingPlugin deactivated or user role issueCheck Plugins screen and role
Broke after updateOutdated extension or templateUpdate all, check status report

Pick the closest row, then read the matching section.

How do you find the actual error?

Turn on WordPress debug logging, reproduce the problem, then read the log and the browser console, because the exact message tells you which plugin, file or request is failing.

Steps:

  1. Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php. The WordPress debugging guide shows the exact lines.
  2. Load the broken page again.
  3. Open wp-content/debug.log and read the newest entries.
  4. In the browser, open developer tools and check the Console and Network tabs.

WooCommerce also keeps its own logs under WooCommerce > Status > Logs. Payment gateways and extensions often write useful errors there.

If you see a critical error screen instead of your store, our guide on fixing the critical error message explains how to use recovery mode.

Common messages and what they usually mean:

  • Allowed memory size exhausted points to a PHP memory limit.
  • Maximum execution time exceeded means a request took too long.
  • Call to undefined function often means an extension expects a newer or older WooCommerce version.
  • Uncaught error in a theme file points to an outdated template override.

Note the plugin or theme folder named in the message. That is your strongest lead.

Is the server running out of memory or time?

If the log mentions allowed memory size or maximum execution time, WooCommerce is hitting PHP limits, so raise the memory limit and check your hosting plan's resources.

WooCommerce uses more memory than a simple blog. Product variations, large carts and many extensions add up quickly.

Things to do:

If pages time out with a 504 error, see our guide on fixing 504 gateway timeout errors.

Is a plugin or theme conflict breaking WooCommerce?

Yes, conflicts are one of the most common causes, so test with a default theme and only WooCommerce active, ideally on a staging copy, to find the plugin responsible.

The free Health Check and Troubleshooting plugin lets you disable plugins and switch themes for your own session only. Customers keep seeing the normal site while you test.

The process:

  1. Enable troubleshooting mode.
  2. Activate only WooCommerce with a default theme.
  3. Check whether the store loads.
  4. Turn plugins back on one at a time until it breaks.

Our plugin conflict guide walks through the full method.

Pay special attention to plugins that touch every store page. These include page builders, currency switchers, product filters, wishlist tools and marketing pixels.

If the store loads with only WooCommerce active, you know the core plugin and your server are fine. The cause is one of the extras, and testing them one by one will reveal it.

Are WooCommerce admin pages stuck on loading?

WooCommerce admin screens are built with JavaScript that talks to the REST API, so a blocked API, a script error or a security rule often leaves them spinning forever.

Check these points:

  • Visit your site address with /wp-json/wc/ added while logged in. An error or blank page suggests the API is blocked.
  • Look for security plugins with options that disable or restrict the REST API.
  • Check the browser console for JavaScript errors on the admin page.
  • Ask your host whether a firewall rule blocks admin API requests.

Our guide on fixing REST API errors in Site Health covers common blocks.

If only Analytics is affected, our guide on WooCommerce Analytics not working covers data import and caching issues.

Is caching breaking the cart or checkout?

Page caching and script optimisation can break dynamic store pages, so exclude cart, checkout and account pages from caching and exclude WooCommerce scripts from delay or combine features.

Cart and checkout show content unique to each shopper. A cached copy shows the wrong data or loads outdated scripts.

Fixes:

  • Exclude cart, checkout and my account pages from page cache.
  • Do not cache pages for visitors with a cart cookie.
  • Exclude WooCommerce scripts from delay and combine settings.
  • Purge all caches, including CDN, after changes.

If you use LiteSpeed, our guide on LiteSpeed Cache settings for WooCommerce lists the right exclusions.

Is the database slowing WooCommerce down?

A large or cluttered database can make store pages and admin screens load very slowly or time out, especially when scheduled actions, sessions or old order data pile up.

Common problems:

  • Thousands of past-due scheduled actions in Action Scheduler.
  • Expired sessions and transients that were never cleared.
  • Large log tables from extensions.
  • Missing database updates after a WooCommerce update.

Check WooCommerce > Status > Scheduled Actions for a backlog. Our guide on fixing past-due Action Scheduler actions explains how to clear it.

Slow admin screens are often a sign of this. If the Orders screen is the main problem, our guide on fixing a slow WooCommerce orders page covers order storage and indexing.

For a wider clean-up, our guide on optimising the WooCommerce database covers safe steps. Always back up first.

Did an update stop WooCommerce from loading?

If the problem started after an update, an extension or theme may not yet support the new WooCommerce version, or a database update may still be pending.

Check these things:

  • Look for a database update notice in the dashboard and run it.
  • Update every WooCommerce extension and your theme.
  • Open WooCommerce > Status and scroll to the templates section for outdated theme overrides.
  • Roll back the update on staging if you need time to find the cause.

The WooCommerce system status report guide explains what each warning means. Our guide on the WooCommerce status report covers it in plain English.

How do you stop WooCommerce loading problems coming back?

Keep plugins and PHP current, test updates on staging, watch scheduled actions and logs, and make sure your hosting plan has enough resources for your store's traffic.

Good habits:

  • Update WooCommerce and extensions together, after testing.
  • Review the status report monthly.
  • Keep regular backups you have tested.
  • Exclude dynamic store pages from all caching.
  • Upgrade hosting before big sales or campaigns.

Our guide on updating WooCommerce safely shows a reliable routine for store updates.

Frequently asked questions

Why is my WooCommerce shop page not loading?

A shop page that hangs or shows a blank screen usually has a PHP error, a memory limit problem or a plugin conflict. Check the debug log for the exact message, raise memory if needed and run a conflict test.

Why are WooCommerce admin pages stuck loading?

Admin screens rely on JavaScript and the REST API. If a security plugin blocks the API, a script fails or a firewall rejects requests, the screens keep spinning. Check the browser console and test the API.

Can caching stop WooCommerce from loading?

Yes. Caching cart, checkout or account pages, or delaying WooCommerce scripts, can break those pages. Exclude them from page and CDN caching and purge every cache layer after making changes.

How much memory does WooCommerce need?

WooCommerce needs more memory than a basic site, and the amount grows with extensions and catalogue size. Check WooCommerce's published server requirements and ask your host to raise limits if your logs show memory errors.

Why did WooCommerce stop loading after an update?

An extension or theme may not support the new version, or a database update may be pending. Run any database update, update all extensions and check the status report for outdated template overrides.

Sources

  1. Understanding the WooCommerce System Status Report WooCommerce
  2. Server requirements WooCommerce
  3. Debugging in WordPress WordPress Developer Resources
  4. Health Check and Troubleshooting WordPress.org
  5. Supported versions PHP

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.