WooCommerce Checkout Not Loading? 11 Proven Fixes (2026)

Your customer adds a product to the cart, clicks “Proceed to Checkout,” and the page either never finishes loading, shows an endless spinner, or goes completely blank. Every second that checkout stays broken is a lost sale.

WooCommerce checkout not loading is one of the most urgent issues I deal with as a WooCommerce developer. I have fixed this on stores running every major hosting platform, page builder, and payment gateway combination. The cause is almost always one of the 11 problems below.

1. JavaScript Error Is Blocking Checkout Scripts

WooCommerce checkout depends heavily on JavaScript. The “Review Order” section, payment method selection, shipping calculation, and the “Place Order” button all load through AJAX calls. A single JavaScript error from any plugin or theme can break the entire chain. The official WooCommerce documentation confirms that AJAX failures are the primary cause of the endless spinner.

How to Diagnose

Open your checkout page in Chrome. Right-click anywhere and select Inspect > Console. Look for red error messages. The error will usually name the file and line number causing the problem. Common culprits include:

• A caching or minification plugin that merged checkout scripts incorrectly
• A theme that loads its own jQuery version conflicting with WooCommerce’s
• A popup, analytics, or cookie consent plugin injecting broken JavaScript

The Fix

If you see an error pointing to a specific plugin’s JS file, deactivate that plugin and test checkout. If the error references a minified file like combined.min.js, your optimization plugin (WP Rocket, LiteSpeed Cache, Autoptimize) is combining scripts in a way that breaks WooCommerce. Go to the plugin’s settings and exclude WooCommerce checkout scripts from minification and combination. In LiteSpeed Cache, add /checkout to the “JS Excludes” list.

2. WordPress Address and Site Address Do Not Match

This is a deceptively simple cause of WooCommerce checkout not loading. AJAX requests only work within the same domain. If your WordPress Address (URL) and Site Address (URL) differ, even by a trailing slash or www vs non-www, the AJAX calls that power the checkout will fail silently.

The Fix

Go to Settings > General in your WordPress dashboard. Make sure both fields are identical:

• https://yourdomain.com and https://yourdomain.com – correct
• https://yourdomain.com and https://www.yourdomain.com – broken
• https://yourdomain.com and https://yourdomain.com/ – can break AJAX on some servers

Fix the mismatch, save settings, and clear all caches. Test checkout in an incognito window.

3. Caching Plugin Is Serving a Static Checkout Page

The checkout page is dynamic. It must load fresh for every visitor because it processes cart contents, user sessions, shipping calculations, and payment tokens in real time. If your caching plugin caches the checkout page, visitors see a static snapshot that cannot process any of these actions.

The Fix

Your caching plugin must exclude these pages from page caching:

• /cart/
• /checkout/
• /my-account/

Most caching plugins add these exclusions automatically when they detect WooCommerce, but it does not always work. Verify manually:

• LiteSpeed Cache: LiteSpeed Cache > Cache > Do Not Cache URIs. Add /checkout
• WP Rocket: Settings > WP Rocket > Advanced Rules > Never Cache URLs
• SiteGround Optimizer: SG Optimizer > Supercacher > uncheck “Enable Dynamic Caching” for WooCommerce pages
• Cloudflare: Create a Page Rule for yourdomain.com/checkout/* with Cache Level: Bypass

If you have server-level caching (Varnish, Redis full-page cache), contact your hosting provider and ask them to exclude WooCommerce pages. This is a common misconfiguration on managed hosting that I deal with regularly as part of my speed optimization work.

4. Checkout Page Is Not Assigned in WooCommerce Settings

WooCommerce needs to know which page is your checkout page. If this assignment is missing, broken, or pointing to a trashed page, checkout will not load.

The Fix

Go to WooCommerce > Settings > Advanced > Page Setup. Check that the “Checkout page” dropdown points to a published page. If the page was deleted, create a new page called “Checkout,” add the [woocommerce_checkout] shortcode (for classic checkout) or the WooCommerce Checkout block (for block-based checkout), publish it, and assign it here.

If you are using WooCommerce 8.3+ with the block-based checkout, make sure the page contains the Checkout block, not the old shortcode. Mixing these up causes a blank or partially loaded page.

5. Order Attribution Feature Is Breaking Checkout

This is a newer cause that started appearing after WooCommerce 8.5. The Order Attribution tracking feature injects additional JavaScript on the checkout page to track where customers came from. On some server configurations, this script causes the checkout to hang indefinitely.

The Fix

Go to WooCommerce > Settings > Advanced > Features and disable “Order Attribution Tracking.” Save and test checkout. This fix has resolved the WooCommerce checkout not loading issue on multiple client stores where every other troubleshooting step failed.

6. Payment Gateway Plugin Conflict

Payment gateways load their own scripts on the checkout page: Stripe loads Stripe.js, PayPal loads its SDK, Square loads its payment form. When multiple gateways load simultaneously, their scripts can conflict. A broken or misconfigured gateway can also prevent the entire checkout section from rendering.

The Fix

Go to WooCommerce > Settings > Payments. Disable all payment methods except one (use “Cash on Delivery” for testing). Test checkout. If it loads, the problem is one of your payment gateways.

Re-enable them one at a time. When checkout breaks again, you have found the conflict. Common fixes:

• Update the gateway plugin to the latest version
• Verify API keys are correct (test and live mode)
• Check that your SSL certificate is valid, as gateways like Stripe refuse to load on insecure pages
• If running both Stripe and PayPal, make sure they are not both trying to render Apple Pay/Google Pay buttons

For deeper WooCommerce payment gateway conflict troubleshooting, I have a separate detailed guide.

7. PHP Memory Limit or Timeout

If your server’s PHP memory limit is too low, the checkout page may partially load and then die. WooCommerce checkout runs multiple hooks, calculates taxes, checks inventory, and processes payment gateway scripts. On stores with many products, plugins, or complex shipping rules, this can exceed the default 64MB memory limit.

The Fix

Check your current limits in WooCommerce > Status > System Status. Look for:

• PHP Memory Limit: should be at least 256MB
• PHP Time Limit: should be at least 120 seconds
• PHP Version: should be 8.0 or higher (8.1+ recommended)

To increase the memory limit, add this to your wp-config.php file:

define( 'WP_MEMORY_LIMIT', '256M' );

If your host restricts this, contact them to increase the limit at the server level. Cheap shared hosting plans often cap memory at 128MB, which is not enough for a WooCommerce store with more than a handful of plugins.

8. SSL or Mixed Content Issue

Payment gateways require HTTPS. If your checkout page loads over HTTP, or if some resources (images, scripts, stylesheets) load over HTTP while the page is HTTPS, the browser may block payment scripts from loading. This causes a blank payment section or a checkout that appears to load but has no payment options.

The Fix

Make sure your site has a valid SSL certificate and that WordPress is configured to use HTTPS. Check Settings > General and ensure both URLs start with https://.

To find mixed content, open checkout in Chrome, click the padlock icon in the address bar, and check for “Not secure” warnings. Alternatively, use the browser console and look for “Mixed Content” warnings. Fix any HTTP references in your theme, plugin settings, or content.

If you recently migrated the site or changed hosting, the old HTTP URLs may still be in the database. A search-and-replace using WP-CLI or the Better Search Replace plugin will fix this across all content.

9. Theme Conflict with WooCommerce Checkout Template

Themes override WooCommerce templates by including their own versions in the theme’s woocommerce/ folder. If the theme’s checkout template is outdated, it may reference functions or hooks that no longer exist in the current WooCommerce version. This causes a fatal error or blank page on checkout.

The Fix

Go to WooCommerce > Status > System Status and scroll to “Template Overrides.” If you see overrides marked with a warning icon, those templates are outdated. Either update them to match the current WooCommerce version or remove the override so WooCommerce uses its default template.

To quickly confirm whether the theme is the problem, switch to the default Storefront theme temporarily. If checkout loads, your theme is the issue. Contact the theme developer for an update, or hire a developer to update the template override files.

10. Security Plugin or Firewall Blocking AJAX Requests

Security plugins like Wordfence, Sucuri, iThemes Security, and server-level firewalls (ModSecurity, Cloudflare WAF) can block the AJAX requests that WooCommerce checkout depends on. The checkout page loads the shell, but the payment methods, order totals, and shipping options never appear because the AJAX request returns a 403 or 406 error.

The Fix

Open Chrome DevTools, go to the Network tab, filter by XHR, and reload the checkout page. Look for any request returning a 403, 406, or 500 status code. If you see a blocked wc-ajax request:

• Wordfence: Check Firewall > Blocking and see if WooCommerce AJAX URLs are being flagged. Whitelist them.
• Cloudflare WAF: Go to Security > Events and look for blocked requests from your checkout domain. Create a WAF exception rule for your checkout path.
• ModSecurity (cPanel hosts): Ask your host to check the ModSecurity audit log for blocked checkout requests and add exceptions.

11. Outdated WooCommerce, WordPress, or PHP Version

Running an old version of WooCommerce on a new version of WordPress (or vice versa) causes compatibility issues. The same applies to PHP. WooCommerce has dropped support for PHP 7.4 and below, and running deprecated versions leads to fatal errors that surface most visibly on the checkout page because it runs the most code.

The Fix

Update in this order to minimize risk:

1. Back up your site first (UpdraftPlus, hosting snapshot, or WP-CLI export)
2. Update WordPress core
3. Update WooCommerce
4. Update all active plugins
5. Update your theme
6. Test checkout on staging before pushing to production

If you are on PHP 7.4 or lower, ask your host to upgrade to PHP 8.1 or 8.2. Test on a staging site first. Some older plugins may not support PHP 8.x, and you will need to replace or update them.

Quick Debugging Sequence for WooCommerce Checkout Not Loading

Run through this in order. Stop at the step that fixes it. For a deeper look at what is happening under the hood, install Query Monitor – it shows PHP errors, slow database queries, and hook firing order directly in your admin bar.

1. Check browser console for JavaScript errors (Inspect > Console)
2. Check Network tab for failed AJAX requests (filter by XHR, look for red entries)
3. Verify WordPress/Site URLs match (Settings > General)
4. Verify checkout page assignment (WooCommerce > Settings > Advanced)
5. Disable Order Attribution (WooCommerce > Settings > Advanced > Features)
6. Purge all caches and test in incognito
7. Deactivate all plugins except WooCommerce and test
8. Switch to Storefront theme and test
9. Check PHP memory and version (WooCommerce > Status)
10. Check security plugin/firewall logs for blocked requests
11. Update everything – WordPress, WooCommerce, plugins, theme, PHP

When to Hire a Developer

If your WooCommerce checkout is not loading and the debugging sequence above did not resolve it, the problem is likely a theme template override issue, a hosting-level caching or firewall configuration, or a deep plugin conflict that requires reading PHP error logs and tracing AJAX request failures. This is core WordPress bug fixing work.

I have fixed WooCommerce checkout not loading on stores running LiteSpeed, SiteGround, Hostinger, Cloudways, and WP Engine. The fix typically takes 1 to 3 hours depending on the root cause. Related issues like WooCommerce dynamic pricing not working or payment gateway conflicts often surface during the same debugging session and get resolved together.

Need your checkout fixed? Book a call or send me a message with a link to your site and a description of the issue. I will diagnose it and give you a fixed-price quote before starting any work.

Frequently Asked Questions

Why is my WooCommerce checkout page stuck on a loading spinner?

The endless spinner means the AJAX request that loads payment methods and order totals is failing. The most common causes are a JavaScript error from a conflicting plugin, a caching plugin serving a static version of the checkout page, or a firewall blocking the wc-ajax request. Open your browser console (Inspect > Console) and Network tab (filter by XHR) to identify the exact failure.

Why is my WooCommerce checkout page blank?

A completely blank checkout page usually means a PHP fatal error. Enable WordPress debug mode by adding define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); to your wp-config.php file, then check wp-content/debug.log for the error. Common causes are an outdated theme template override, a PHP memory limit exceeded, or a plugin calling a function that no longer exists.

Can caching plugins break WooCommerce checkout?

Yes. Page caching, HTML minification, and JavaScript combination can all break WooCommerce checkout. The checkout page must be excluded from page caching, and WooCommerce scripts should be excluded from JS minification and defer settings. Most caching plugins add these exclusions automatically for WooCommerce, but they do not always work correctly, especially after plugin updates.

How do I fix WooCommerce checkout not loading after an update?

If checkout stopped working after a WooCommerce or WordPress update, the most likely cause is an outdated theme template override or a plugin that is not compatible with the new version. Check WooCommerce > Status > System Status for “Template Overrides” warnings. Switch to the Storefront theme temporarily to confirm whether the issue is theme-related.

Why does WooCommerce checkout work in incognito but not in a normal browser?

This points to a browser extension or cached data causing the issue. Clear your browser cache and cookies, then test again. If the problem only affects you and not customers, it is likely a browser-side issue. If it affects all users, check your server-side caching configuration.

What does a 403 error on WooCommerce checkout mean?

A 403 Forbidden error on the checkout AJAX request means a security plugin or server firewall is blocking the request. Check Wordfence, Sucuri, or your host’s ModSecurity logs. The fix is to whitelist WooCommerce AJAX endpoints in your security configuration.

Why does WooCommerce checkout show no payment methods?

If the checkout page loads but the payment section is empty, either no payment gateways are enabled, the enabled gateways have configuration errors (wrong API keys, currency mismatch), or the gateway scripts are being blocked by a content security policy or firewall. Go to WooCommerce > Settings > Payments and verify at least one gateway is enabled and configured correctly.

How do I check if my checkout page is correctly assigned in WooCommerce?

Go to WooCommerce > Settings > Advanced > Page Setup. The “Checkout page” dropdown should point to a published page that contains either the [woocommerce_checkout] shortcode or the WooCommerce Checkout block. If the page is in trash, draft, or missing entirely, WooCommerce cannot route customers to checkout.

Can the WooCommerce Order Attribution feature break checkout?

Yes. The Order Attribution tracking feature introduced in WooCommerce 8.5 has been reported to cause endless loading on checkout for some server configurations. Disabling it at WooCommerce > Settings > Advanced > Features has resolved the issue for multiple store owners. This is a safe feature to disable as it only affects order source tracking, not checkout functionality.

How long does it take to fix a broken WooCommerce checkout?

Most WooCommerce checkout loading issues can be diagnosed and fixed within 1 to 3 hours. Simple causes like caching misconfiguration or a missing page assignment take minutes. Complex causes like theme template conflicts, firewall rules, or payment gateway script collisions may take longer. The debugging sequence in this guide covers all common causes in priority order.