The 70% benchmark — and what "normal" actually means
Baymard's 2024 study puts the global average cart abandonment rate at 70.19% across all industries. For WooCommerce stores in Israel, mobile abandonment runs 8–12% higher than desktop, largely due to payment gateway redirect latency and mobile form UX problems specific to local payment processors.
The goal is not zero abandonment. Comparison shoppers, window browsers, and people saving items for later will never convert on the first visit — and no amount of checkout optimisation will change that. The goal is to identify the portion of abandonment that is caused by technical friction and eliminate it. That portion typically ranges from 18–35% of total abandonment, depending on how neglected the checkout currently is.
The diagnostic order matters: load time first, then form fields, then trust signals, then mobile UX. Each problem compounds the next — a slow checkout page that also has 12 unnecessary fields and an untrusted payment logo is not three separate problems of equal weight; the slow load is the reason the other two even get seen.
Checkout page load time is the first filter
Google's research quantifies the cost precisely: each 1-second delay in checkout page load reduces conversions by 7%. The WooCommerce checkout page is particularly vulnerable because it loads three distinct scripts before the "Place Order" button becomes clickable: the payment gateway , the shipping calculator, and the WooCommerce session heartbeat. Any one of these can be the bottleneck.
The correct diagnostic tool is Chrome DevTools Performance panel, not a page speed score. Load the checkout page on a throttled mobile connection (Chrome's "Slow 4G" preset), open the Network tab, and sort by duration. The longest request is your first fix. A shipping calculator that makes a round-trip server request on every country/postcode change is a common culprit — replace it with a flat-rate or pre-calculated shipping option and measure the impact.
Caching plugins have almost no effect on checkout page load because the checkout page cannot be cached — it is session-specific. The performance fix is at the script level: defer non-critical JavaScript, lazy-load the payment gateway iframe only when the user scrolls to the payment section, and remove any plugin that adds scripts to every page when it only needs to run on shop pages.
Form fields: the arithmetic of friction
Baymard's 2024 checkout usability study found that the average checkout has 39 form fields or steps, of which 24 are unnecessary. Their research quantifies the conversion cost: each unnecessary field removes 2–4% of completing checkouts. A checkout with 8 removable fields loses between 16–32% of conversions through friction alone.
The practical audit for a WooCommerce store: company name (remove for B2C stores entirely — almost nobody fills it accurately and it signals "this site is for businesses"), phone number (make optional, not required — most customers abandon when a required phone field appears mid-checkout), billing address when shipping and billing are the same (consolidate with a checkbox that is checked by default).
For Israeli stores: the ID number field required for VAT invoicing is non-negotiable legally — but placement matters. Position it as the last field before submission, label it explicitly as required for invoice purposes, and pre-fill it from the user's account if they are logged in. Every friction point at the end of a checkout costs more than the same friction at the start, because the user has already invested time.
Payment gateway trust signals — and what actively hurts
Three trust signals that improve conversion when placed correctly: SSL badge visible above the fold on the checkout page (not in the footer — above the payment form), accepted card logos displayed immediately above the "Place Order" button, and a single-sentence money-back or secure-checkout statement next to the CTA. Each of these is a 1–3% conversion improvement in isolation; together they can shift the needle 5–8%.
The signal that actively destroys trust: a payment gateway redirect to a third-party domain with a different visual design. The user sees your checkout, clicks "Pay Now", and lands on a page that looks nothing like your store — different colours, different fonts, a URL they don't recognise. This is the primary driver of last-second abandonment. The technical fix: use the gateway's hosted embed mode instead of a redirect.
For Israeli WooCommerce stores specifically: Tranzila and Cardcom both support iframe embed integration. The redirect mode is the default configuration because it requires no SSL certificate management on the store side — but the abandonment cost of the redirect typically outweighs the SSL setup complexity within two months of store operation.
Mobile checkout: where most WooCommerce stores fail silently
iOS Safari auto-zooms any input element with a font-size below 16px. On a checkout form, this viewport zoom shifts the layout, collapses the visible area, and frequently causes the payment form to reflow mid-entry — the user loses their place and often abandons. The fix is a single CSS rule: set font-size to 16px on all checkout input elements. It does not affect desktop layout and eliminates the auto-zoom on every iOS device.
Android Chrome fails differently: numeric keyboard does not appear for card number fields unless the input carries the attribute inputmode="numeric". Without it, the user gets the full alphabetic keyboard on a 4-inch screen, tries to find the number pad, and frequently gives up. WooCommerce's default checkout fields do not include this attribute — it requires either a custom plugin or direct PHP filter to the checkout field arguments.
Both of these are silent failures. No JavaScript error appears in the console, no 500 error is logged. The only signal is session recordings showing users dropping out at the payment step on mobile. Check both before assuming your checkout is mobile-ready.
Finding your specific bottleneck
Instrument three events in Google Analytics 4: checkout page load, shipping method selection, and payment button click. The percentage drop between any two consecutive events is your at that step — and that step is the bottleneck to fix first.
If the drop is between checkout page load and shipping method selection, the problem is load time or form complexity (too many fields before the user even reaches shipping). If the drop is between shipping selection and payment click, the problem is trust signals or payment method choice. If the drop is after payment click, the problem is the payment gateway itself — redirect, iframe latency, or card decline UX.
WooCommerce includes a basic funnel in the WooCommerce Analytics reports. For more granular event tracking, add custom GA4 events using WooCommerce's JavaScript hooks (add_to_cart, begin_checkout, purchase). Google Tag Manager makes this manageable without touching PHP. Once instrumented, you will have conversion data specific to your store — not industry benchmarks.
What is your checkout actually losing?
Tell me your current checkout conversion rate and where users are dropping off. I'll diagnose the specific bottleneck and tell you what to fix first.
Start the briefSources
- 1Baymard Institute — 2024 E-Commerce Checkout Usability Study — Global average cart abandonment: 70.19%. Average checkout has 39 form fields; 24 are unnecessary. Each removed field reduces abandonment 2–4%.
- 2Google / SOASTA — The State of Online Retail Performance (2017, still cited in Core Web Vitals documentation) — Each 1-second delay in checkout page load reduces conversions 7%. Mobile sessions with load times above 3 seconds have a 53% bounce rate.
- 3Tranzila — Developer documentation: iframe integration mode — Tranzila's iframe embed mode keeps the payment form within the merchant's page, eliminating the domain-change abandonment trigger of the standard redirect mode.
- 4Apple — Safari mobile text size adjustment — iOS Safari auto-zooms input elements with font-size below 16px to prevent unreadably small text. The auto-zoom interrupts checkout flow and cannot be disabled without affecting accessibility.
- 5WHATWG — HTML inputmode attribute specification — inputmode="numeric" triggers the numeric keyboard on iOS and Android for text inputs — required for card number, CVV, and postal code fields to avoid alphabetic keyboard presentation on mobile.