Every piece of advice about product pages says the same thing: add more. Add measurements, add material details, add care instructions, add reviews, add a size guide. We have written some of that advice ourselves.
What almost nobody writes is the other half of the sentence. Each of those additions arrives as something the browser has to download, parse and lay out, and a product page that answers every question but takes six seconds to appear has not answered anything — the shopper left before the answers rendered.
What "slow" actually means now
It stopped being a matter of opinion. Google publishes three numbers, and a page is either inside them or it is not:
- Largest Contentful Paint under 2.5 seconds — how long until the biggest thing on screen has drawn. On a product page that is usually your main photo.
- Interaction to Next Paint under 200 milliseconds — how long the page takes to visibly respond when someone taps. Tapping a size-guide tab and watching nothing happen is this number failing.
- Cumulative Layout Shift under 0.1 — how much the page jumps around while loading. If a block loads late and pushes the Add to cart button down as a shopper reaches for it, that is this number.
The part that catches people out is how these are judged: at the 75th percentile of real page loads. Not your average. Not your laptop on office wifi. Three out of four visits have to be good, which means the slowest quarter of your visitors — older phones, patchy mobile data — decide your score.
The weight rarely comes from the words
The text you add to a product page is close to free. A thousand words of measurements and care instructions is a couple of kilobytes. That is not what makes pages slow.
What makes pages slow is the machinery brought in to display it. Shopify says this plainly in its own help material: apps add features but can also slow down your store, and too many apps loading assets on your storefront hurts performance. Their app guidance puts a number on the acceptable cost — an app should not reduce your Lighthouse performance score by more than 10 points, measured as a weighted average across your home page, product pages and collection pages, with product pages counting for 40% of it.
Ten points, per app. Install six apps that each sit just inside that limit and the arithmetic stops being reassuring. Shopify's own Theme Store requires a theme to average at least 60 before you have installed anything at all.
Four questions to ask before you install anything
You do not need to become a performance engineer. You need to ask four things and write down the answers.
- Does it load on every page, or only where I put it? This is the biggest single difference and it is invisible from the listing. An app built as a theme app extension loads its assets on the pages where you placed its block. An app that injects a script into your theme runs everywhere — including your home page, your policies, your checkout path — whether or not that page uses the feature.
- Does it edit my theme code? Shopify's documentation is direct about this: theme app extensions do not edit theme code, which lowers the risk of breaking your theme. An app that pastes code into your theme leaves that code behind when you uninstall, and finding it later is your problem.
- Does it reserve space before it loads? A block that appears after everything else and shoves the page down is a layout-shift failure you will feel as mis-taps. This is easy to check by eye: load a product page on a phone and watch whether anything jumps.
- What did it cost? Which brings us to the only step that actually settles the argument.
Measure before and after — it takes ten minutes
Run PageSpeed Insights on one product page before you install, and again after. Not on your home page; product pages carry the most weight in Shopify's own calculation, and they are where the information lives.
Two cautions worth knowing before you read the result. Scores move between runs, so Shopify advises averaging several consecutive tests rather than trusting one. And the lab score is not the same thing as your real visitors' experience — the field data, when the report has enough of it, is the number that reflects actual phones on actual networks.
Do this per app, not once a year in a panic. A ten-point drop is easy to accept when you can see what you bought with it and easy to refuse when you cannot.
What to do this week
- Test one product page on a phone, on mobile data, with the wifi off. Not a simulation. This takes two minutes and is more convincing than any score.
- List your installed apps and mark the ones you no longer use. Shopify's guidance is to remove what is not essential — an unused app that still loads assets is pure cost.
- Check what loads on a page that needs none of it. Your privacy policy page has no products, no reviews and no size guides. If things are loading there anyway, you have found something running globally that need not be.
- Then keep adding the information. This article is not an argument against complete product pages. It is an argument for asking what each addition costs, so that the answer is a few kilobytes of text rather than another script on every page of your store.
Being able to add the information without the page paying for it is the whole design brief behind Mitasu for Apparel: one block, only on the pages where you place it, and no script that runs store-wide.
Sources: web.dev — Web Vitals; web.dev — How the Core Web Vitals metrics thresholds were defined; Shopify — Best practices for apps in the Shopify App Store; Shopify Help Center — Improving your online store performance; Shopify — Performance best practices for themes.
