# Fast product page, slow checkout

URL: https://intelligizedigital.com/blog/a-fast-product-page/
Updated: 2026-10-25
Summary: A fast product page can hide a slow checkout: add to cart, shipping rates and delivery dates stall. How to time the buy path and add fallbacks.

[Speed](https://intelligizedigital.com/blog/?topic=speed)

## A fast product page can still hide a slow checkout

Clearing the Core Web Vitals thresholds does not fix a checkout waiting on a script the warehouse never sees. The vitals measure loading, response and layout on the pages visitors land on. The buy happens after that, through add to cart, a stock check, a delivery estimate, shipping rates and payment. Time each of those from the tap to a usable answer, and give every external call a timeout and a fallback.

23 October 2026 Intelligize Digital
4 min read [All notes](https://intelligizedigital.com/blog/)

### Key points

- If the add-to-cart button shows a spinner within 80 milliseconds, INP records a good interaction even when the cart takes four seconds to update.

- Once the landing page is fast, the slow parts sit behind clicks.

- A step that is fast on average and fails one time in fifty loses one buyer in fifty at that step.

- A shipping-rate callback that times out should return a flat rate you can honour.

### On this page

- What Core Web Vitals measure

- Where the wait moves: the slow checkout

- A typical product page

- Measure the buy path

- Fallbacks that keep the order

- Checklist for the buy path

Not answered here? Ask on the free 30-minute audit call.

[Book a free audit](https://intelligizedigital.com/free-audit/)

### What Core Web Vitals measure

Three numbers, read at the 75th percentile of real visits. Largest Contentful Paint should be 2.5 seconds or less, Interaction to Next Paint 200 milliseconds or less, and Cumulative Layout Shift 0.1 or less. The field data comes from the Chrome UX Report, and Search Console groups it by similar URLs.

Two limits matter for a store. Field data needs enough traffic, so low-volume pages such as checkout steps often have no figures of their own. And INP stops the clock at the next paint after an interaction. If the add-to-cart button shows a spinner within 80 milliseconds, INP records a good interaction even when the cart takes four seconds to update.

Lab tools have the same blind spot. A default Lighthouse run loads one page and never taps a button, so it reports nothing about the cart or checkout.

### Where the wait moves: the slow checkout

Once the landing page is fast, the slow parts sit behind clicks. Add to cart calls the cart API, and then every app listening for that event runs: an upsell drawer, a free-shipping bar, analytics tags. A delivery-date widget sends the postcode to a 3PL. A stock badge asks the ERP in real time. At checkout, shipping rates may come from a carrier-rate callback that calls yet another service. Address autocomplete, a fraud script and the payment frame each load their own code.

Each of these was added by a different team for a reason, a marketing app one quarter and a delivery promise the next. They are rarely tested together, and almost never on a slow phone.

None of these show up in the product page’s report, and the warehouse sees only the orders that made it through.

### A typical product page

Picture a store like this one. The product page passes all three vitals, with LCP at 1.9 seconds and INP at 120 milliseconds. A tap on add to cart paints a spinner in 70 milliseconds. The cart drawer opens 3.4 seconds later, because an upsell app waits for a recommendation API before it renders. At checkout the buyer enters a pincode, and the delivery-date call to the 3PL takes six seconds on a busy afternoon. Shipping rates appear only after it returns. When it times out, the rate list is empty and the buyer cannot continue.

### Measure the buy path

Give each step a start and an end: tap on add to cart to cart updated, address entered to rates shown, pay tapped to confirmation page. Mark them in the browser with performance.mark and performance.measure, send the measures with your analytics, and read the 75th and 95th percentiles each week.

Log the server side too. Record the duration of each rate callback, stock lookup and delivery-date call, and count the timeouts. A step that is fast on average and fails one time in fifty loses one buyer in fifty at that step.

Test on a mid-range Android phone over a throttled connection as well as on the office laptop.

Put the timings beside the funnel. Compare the share of sessions that reach the shipping step and never see rates with the rate-call duration for the same hour. If both rise on busy afternoons, the cause is the call, and a theme change will not move it.

### Fallbacks that keep the order

A shipping-rate callback that times out should return a flat rate you can honour. An empty list ends the order. A delivery estimate can come from a precomputed table by pincode zone and dispatch cut-off, refreshed whenever the 3PL changes its data. Stock shown at add to cart can come from the last value the ERP pushed, with the final check made when the order is created. The payment frame is the one step you cannot cache. Keep a second payment method enabled at checkout, so a gateway outage does not stop every order, and test both with a small real payment each month.

Template, image and app weight sit under [speed optimisation](https://intelligizedigital.com/services/speed-optimisation/). The click-to-response numbers for the buy path belong with [conversion optimisation](https://intelligizedigital.com/services/conversion-optimisation/), and moving stock and delivery data out of live calls is [ERP integration](https://intelligizedigital.com/services/erp-integration/) work.

### Checklist for the buy path

5 checks

- List every script and API call between add to cart and the order confirmation, with its owner.

- Give each call a timeout and a fallback answer.

- Serve stock and delivery estimates from a cache the ERP updates on change, and keep live calls off the click.

- Remove checkout apps when nobody can name the job they do.

- Record click-to-response for each step weekly, next to the vitals.

Certifications

### Certifications and partner programmes

Intelligize Digital is a registered partner of these platforms and hosts.

- [Shopify Shopify Partner](https://intelligizedigital.com/partners/shopify/)
- [BigCommerce BigCommerce Partner](https://intelligizedigital.com/partners/bigcommerce/)
- [WP Engine WP Engine partner](https://intelligizedigital.com/partners/wp-engine/)
- [Automattic Automattic for Agencies](https://intelligizedigital.com/partners/automattic/)
- [Nexcess Nexcess partner](https://intelligizedigital.com/partners/nexcess/)
- [Hostinger Hostinger partner](https://intelligizedigital.com/partners/hostinger/)

- BigCommerce Certified
- **Liquid Storefronts for Theme Developers** Shopify Certified
- **Headless at Shopify for Developers** Shopify Certified
- **Shopify Foundations** Shopify Certified
