# Shopify Plus speed and Core Web Vitals, measured and fixed.

> A fixed-fee sprint for Shopify Plus stores that are slow or run too many apps. We remove render-blocking apps, heavy templates and conflicting cart logic, and measure Core Web Vitals before and after. It starts with a baseline from your real visitor data.

Shopify Plus development · Performance & Conversion Sprint

- **Starts with:** A fixed-fee Performance Sprint
- **Typical build:** Fixes shipped in order of measured impact
- **You own:** The fixes, the measurements and the app audit

## When does a Shopify Plus store need a sprint?
- Core Web Vitals fail on product, collection or cart templates.
- Pages respond slowly to taps on filters, variants or add to cart.
- Apps you uninstalled still leave code in the theme.
- Several apps touch the cart, and discounts or totals sometimes disagree.
- The store needs to be faster now, before any redesign.

## How does a Performance Sprint run?
1. **Measure the baseline** — Field data from real visitors and lab tests on key templates.
2. **Audit apps and scripts** — Every app, pixel and script: what it loads, where, and what it slows.
3. **Prioritise the fixes** — Ranked by impact on the templates that carry revenue, agreed before work starts.
4. **Ship the fixes** — Remove, defer or replace scripts; lighten templates; untangle cart logic.
5. **Measure again** — Compare against the baseline, report what changed and what to do next.

## A faster store and the evidence for it
- A baseline of Core Web Vitals per template
- An audit of every app, pixel and script
- A prioritised list of fixes, agreed before work
- Fixes shipped to templates, scripts and cart logic
- A before-and-after report on the same measures
- A performance budget to keep the store fast

## What usually goes wrong
- **Chasing a lab score instead of real visitors** — Field data is what customers feel; lab scores are clues.
- **Removing apps without checking what they do** — Map each feature first, so nothing customers use disappears.
- **Lazy-loading the main product image** — It delays the page’s largest image; load it first.
- **Promising a conversion lift before measuring** — We report what changed; we don’t predict revenue.

## Questions
### What is a good INP on Shopify?

Google publishes thresholds for good, needs improvement and poor, judged on real visits rather than lab tests. We measure INP from field data on the templates that matter most, such as product, collection and cart, and work towards the good band on each.

### Which apps slow a Shopify store most?

Usually the ones that load scripts on every page: reviews, chat, pop-ups, personalisation and tracking pixels. Code left behind by uninstalled apps is common too. We measure each one, because the same app can be light on one store and heavy on another.

### Will we lose features?

Not without your agreement. We map what each app or script does before touching it. Often the fix is to defer, replace or rebuild a feature in the theme, not remove it, and anything that goes is on a list you approve.

### How do you measure the result?

With the same measures before and after: Core Web Vitals from real visitors, plus lab tests on each key template. Field data takes time to settle, so we keep reporting it as it arrives. We show what changed; we don’t promise a conversion figure.

### What happens after the sprint?

You keep the fixes, the report and a performance budget. To keep the store fast as apps and campaigns change, an Engineering Partnership on Care or Core carries the work on. If the sprint shows the theme itself is the limit, we’ll say so.

[Request a Performance Sprint](https://www.studioantipodes.com/start-a-project)