Reviewed October 22, 2026
Why your homepage feels fast but your product pages crawl
The homepage gets the attention, the audits, and the hero image diet, then shoppers land from ads on product pages that were never optimized at all. Why product pages accumulate weight homepage audits never see, and where to look first.
Different pages, different gravity
A homepage is mostly a poster: a hero, some tiles, a featured collection. A product page is an application. Variant selectors, image galleries with zoom, review widgets, size charts, sticky buy bars, recommendation carousels, and a stack of app blocks all load on the same page, each installed at a different time by a different person for a good reason.
Then there is where shoppers actually land. Paid and organic traffic overwhelmingly arrives at product and collection pages, not the homepage. The page you optimized is the page fewest buyers see first, and the pages carrying your revenue carry months of accumulated additions nobody ever weighed as a set.
The usual suspects on product pages
Reviews and ratings apps are frequent heavyweights, loading their own scripts and styles on every product page whether or not the product has reviews. Image zoom and gallery libraries add weight too, and product media itself is often the largest payload on the page: multiple angles, lifestyle shots, and a video, all eager loaded instead of waiting their turn below the fold.
App blocks deserve a page level audit of their own. Each embedded widget, quiz, size finder, loyalty prompt, back in stock form, writes its own scripts into the page. Individually they are defensible. Collectively they can outweigh the theme, and product pages are where they all gather, since that is where the buying decisions they target happen.
How to see your product page clearly
Run your speed checks on the product page that gets the most paid traffic, not the homepage, and use the median of several runs. Break the page weight down by type in your browser's network tools: scripts, images, fonts, and third party requests each tell a different story about who is responsible.
Then load the page with third party scripts blocked and compare. That single experiment shows you the tax your apps collectively charge, in seconds a shopper feels. It does not tell you which app to remove; it tells you the size of the prize, which turns a vague cleanup intention into a decision with a number on it.
Fixes in the order they pay
Lazy load everything below the first product image, including the gallery's later photos and the recommendation carousels. Defer or conditionally load app widgets so a review tool initializes when scrolled to, not at page open. Compress and right size product media, and question any video that autoplays for a product whose buyers mostly arrive on phones.
Finally, repeat whatever ritual you apply to the homepage after every change, applied to one representative product page. Stores do not get slow product pages through neglect of speed in general; they get them through optimizing the page they look at instead of the page their customers land on.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Third party apps and Shopify speed: how to audit the cost, Image formats on Shopify: WebP, AVIF, and what actually loads faster, and Lab data vs field data: why your speed score and your customers disagree.
Frequently asked questions
Why do speed tools give my homepage and product page such different scores?
Because they are effectively different websites sharing a theme. The product page carries galleries, variant logic, reviews, and app blocks the homepage lacks, plus heavier media. Always benchmark the page types your traffic actually lands on.
Which product page should I test?
Your highest traffic product page, usually the one your ads point to, since improvements there affect the most sessions. Also keep one media heavy product as a worst case reference so fixes are judged against the hardest page, not the easiest.
Do reviews apps really slow pages down that much?
They vary widely by vendor and configuration, but review widgets commonly add meaningful script weight and third party requests to every product page. Measure yours with scripts blocked versus allowed rather than assuming; the difference is your actual cost.
How often should I re audit product page speed?
After every app install and every theme update at minimum, and quarterly as a habit. Product page weight grows by accumulation, one reasonable addition at a time, so the audit has to be periodic rather than a one off cleanup.