Steve Morin
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: website migrationYou might take a look at a plugin called “All in one migration” It makes it very easy.
Hey Seth,
I’m a developer (not affiliated with this plugin or ShipStation), but I’ve dug through live-rate latency like this before — here’s where I’d start, in case it saves you some time.
The 10 seconds is really two problems stacked: how long a single rate call takes, and how often it gets fired. Worth separating those before changing anything.
Fastest way to find the culprit: temporarily disable CheckoutWC and run the same checkout on native WooCommerce, timing the rates. If it speeds up, CheckoutWC’s AJAX recalculation is a big part of it. If it’s still ~10s, the bottleneck is the ShipStation API call itself and CheckoutWC is mostly off the hook. While you do that, open browser DevTools > Network and watch the update_order_review / update_shipping_method requests — count how many fire per interaction and time each one. One slow call vs. a pile of calls is a completely different fix.
A few config-side things that helped me:
- Trim the carriers/services you query where you can. Each carrier is basically its own upstream lookup, so fewer = faster calls.
- If you’ve got address validation or virtual box-packing enabled, those add time to every call. See if you actually need validation at the rate step.
- Make sure nothing is busting WooCommerce’s shipping rate cache. Some currency/wholesale plugins (or stray snippets) randomize the cache key and force a fresh recalc on every interaction.
- Confirm an object cache (Redis) is active on your VPS and that DreamHost isn’t throttling outbound HTTP.
On CheckoutWC specifically: since checkout pages can’t be cached, their flow leans on frequent AJAX updates, so it’s worth asking their support about the debounce settings and whether their flow bypasses Woo’s per-package rate cache. That Network capture is good evidence to hand them.
FWIW the free plugin’s changelog mentions a caching layer was added a while back, so some caching already exists — but whether a paid tier adds anything specifically for AJAX checkout flows is really a question for IQComputing directly.
Hope some of that helps — curious which way the CheckoutWC test goes for you.