Cart sessions that hit a slow PDP and abandoned at checkout. Direct evidence that perf is costing revenue, gives ammo to the hosting upgrade conversation.
At a glance
Cart sessions that hit a slow product page and then abandoned at checkout. Direct evidence that page-speed is costing the WooCommerce store revenue.
Calculation
Calculated automatically from your WooCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A self-hosted UK fashion brand on Bluehost shared hosting. GA4 + CrUX both connected. 30-day window: 14 Mar 26 to 12 Apr 26.
Three observations:
- Self-hosted variance is the recurring theme. This brand’s slow-PDP bucket is concentrated on the cart and PDP pages where WC’s cart fragments (PHP-rendered) are not effectively cached. Bluehost throttles concurrent PHP processes, so traffic spikes hit the slow tail. A move to managed-Woo (Pressable) cut the slow-PDP bucket by ~70% in a similar test.
- The £2,420 / 30D figure is conservative. It only counts carts that abandoned, not the broader funnel friction (visitors who never added to cart because the PDP felt sluggish). The full revenue cost is typically 2-3x this number.
- Plugin-induced data shape variance: WP Rocket / W3 Total Cache. Caching plugins on slow hosts can produce a bimodal TTFB distribution: cached page loads in 200ms, uncached in 2,000ms. The card’s p75 threshold catches the uncached tail. Stores with aggressive caching may see this card under-report because most sessions hit cached pages.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in WooCommerce / GA4 / CrUX: Woo: WP Admin → WC → Reports → does not have an abandoned-cart-by-speed view. GA4: Reports → Engagement → Events → page_load_time. CrUX: PageSpeed Insights for the cart and PDP pages. The combined view is unique to Vortex IQ. Why our number may differ from a manual GA4 calculation:
Cross-connector reconciliation:
Known limitations / merchant FAQs
Self-hosted vs managed-Woo, why is this card most actionable for self-hosted? Slow shared hosting is the single biggest driver of slow PDPs on Woo. Managed-Woo hosts run capacity-managed infrastructure; self-hosted shared cannot. Status-filter selection, why focus on cart abandonment? Cart abandonment with measurable cart value is the most actionable downstream of slow PDPs. PDP-only abandonment (visited PDP, never added to cart) is harder to attribute to speed alone. Refund-object accounting? Not applicable. Plugin-induced data shape variance, what should I watch?- Caching plugins (WP Rocket, W3 Total Cache): bimodal speed distribution.
- AMP plugins: split traffic into AMP / non-AMP cohorts.
- Page builders (Elementor, Divi, Beaver Builder): heavier JS payloads, structurally slower PDPs.
- Confirm cart-abandonment definition (GA4 funnels vs Woo
pendingorders). - Check timezone alignment.
- Verify the slow-PDP threshold (this card uses p75 baseline; configure per workspace).