WooCommerce Block Checkout: A Conversion Checklist for 2026

WooCommerce block checkout conversion checklist banner

WooCommerce’s block-based checkout replaced the old shortcode checkout as the default, and it’s generally faster and lighter — fewer dependencies, better lazy-loading. But switching to it doesn’t automatically fix conversion: most stores still run 10 or more checkout fields when the practical target is 7, and offer only one payment method when stores with three or more see meaningfully higher completion rates. This checklist covers what actually moves the needle on a block checkout.

Field Count: The Single Biggest Lever

Every checkout field is a small chance for the customer to stop. The commonly cited target is no more than 7 fields, yet most WooCommerce checkouts ship with 10 or more once you count both billing and shipping address blocks in full. Practical reductions on a block checkout:

  • Turn off the company name, address line 2, and phone fields unless you genuinely need them for fulfillment.
  • Enable “ship to a different address” as an opt-in toggle rather than showing a full second address block by default.
  • Keep guest checkout on. Forcing account creation before payment is one of the most consistent causes of cart abandonment.

Payment Options

Stores offering three or more payment methods see up to 30% higher conversion than stores offering just one. On a block checkout, the express payment area (Apple Pay, Google Pay) sits at the top of the form and lets returning customers skip the address fields entirely — enabling it is one of the highest-return changes you can make. Beyond that, cover cards, at least one wallet, and a “buy now, pay later” option if it fits your average order value.

Area Common state Target
Checkout fields 10+ 7 or fewer
Guest checkout Often disabled Enabled
Payment methods 1 3+ (cards, a wallet, optionally BNPL)
Express checkout (Apple/Google Pay) Off On, shown above the form
Checkout page speed Not measured Tested and optimized like any key page

Speed Still Matters Here

The block checkout is lighter than the shortcode version, but it’s not immune to a slow page. Checkout inherits the same performance problems as the rest of the store — unoptimized images, no caching or CDN, a heavy theme — and a slow checkout loses customers who had already decided to buy. The same server-side techniques in WooCommerce Performance in 2026: How to Speed Up Your Store apply directly to the checkout page.

Test Any Change Against Real Orders

Every checkout customization — a removed field, a new payment method, a plugin that adds a delivery date or a custom field — is a change to the single most important flow on the store. Test each one with a real test order end to end, on both desktop and mobile, before it reaches customers. A checkout that silently breaks for one payment method or one shipping zone can cost more than any conversion tweak gains. If you’d like your checkout reviewed for field count, payment coverage, and speed, get in touch.

Frequently Asked Questions

Is the WooCommerce block checkout faster than the old shortcode checkout?

Generally yes — it has fewer dependencies and better lazy-loading. But it still inherits site-wide performance issues like unoptimized images, missing caching, or a heavy theme, so it’s not automatically fast.

How many checkout fields should I have?

Aim for 7 or fewer. Most stores exceed that once both full billing and shipping address blocks are counted — trimming optional fields like company name and address line 2, and making a separate shipping address opt-in, is the quickest way down.

Does adding more payment methods really increase conversion?

Data consistently shows stores with three or more payment options convert notably better than single-option stores — often cited around 30% higher. Enabling express checkout (Apple Pay, Google Pay) at the top of the form is usually the highest-impact single addition.

Featured image: original illustration.


Ready to start your project?

Share your brief and we’ll propose the right approach — a full site, a landing page, or a custom plugin.