Technical SEO
Product Page Speed: Fixing Heavy Galleries, Videos and Widgets
By Shayan Ahmad · · 6 min read

Product pages are usually the heaviest templates on an online store. They carry large image galleries, videos, review widgets, recommendation blocks, chat buttons, size guides, payment badges and a growing pile of app scripts. Each one was added for a good reason. Together, they often make the page slow to show its main image, slow to respond to taps and prone to jumping around as it loads.
This guide is for developers and technically minded store owners. It covers the usual slow elements on product templates, how to tell which ones are hurting you, and lighter ways to keep the same features.
What "Fast" Means for a Product Page
Google's Core Web Vitals are a useful framework because they measure what shoppers actually feel:
- Largest Contentful Paint (LCP): how quickly the main content, usually the first product image, appears. Google's "good" threshold is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps a size, colour or add-to-cart button. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the layout jumps while loading. Good is 0.1 or less.
Check these for your product template, not just your homepage. The Core Web Vitals report in Google Search Console groups similar URLs, so you can see whether product pages as a group have problems. For a quick reading on a single page, try our free page speed check.
Heavy Image Galleries
The gallery is usually the biggest single cause of slow LCP on product pages.
The common problems
- Full-resolution images loaded for every thumbnail and every slide at once.
- The main image lazy-loaded, so the browser waits before fetching it.
- Gallery sliders that rely on a large script before showing anything.
- Images without set dimensions, causing the layout to jump.
Lighter alternatives
- Prioritise the first image. Load the main product image immediately, never lazy-load it, and consider giving it a high fetch priority so the browser requests it first.
- Lazy-load the rest. Additional slides and thumbnails can load as they come into view.
- Serve responsive sizes. Use the platform's image resizing so phones get smaller files than desktops. On Shopify, image URLs can request a specific width.
- Use modern formats. Most platforms can serve WebP or AVIF automatically.
- Set width and height. Reserving space for each image prevents layout shift.
- Render the first image without the slider. Show the main image in plain HTML, then let the gallery script enhance it once loaded.
Product Videos
Video helps shoppers understand a product, but embedded players are expensive.
The common problems
A standard embedded video player loads its own scripts, styles and preview data as soon as the page loads, even if nobody presses play. Autoplaying background videos at the top of the page can delay the main content and use up mobile data.
Lighter alternatives
- Use a click-to-load preview. Show a lightweight thumbnail image with a play button, and load the real player only when someone clicks. This is often called a facade.
- Place video below the main image. Keep the first image as the main content and put video in the gallery or further down.
- Keep self-hosted clips short and compressed. If you host short product loops yourself, use small, compressed files with a poster image, and avoid autoplaying them on mobile.
Third-Party Widgets
This is where most product templates quietly gain weight. Each app or widget usually adds its own scripts and sometimes its own fonts and styles.
Review widgets
Review apps often load a large script and then insert stars and reviews after the page loads, which can cause layout shift. Reserve space for the star rating near the title, load the full review section lower down only when it comes into view, and where your app allows, output review content in the page HTML rather than injecting it later.
Chat and support buttons
Live chat widgets are often among the heaviest scripts on a page. Load them after the page has finished loading or only when someone clicks a simple chat button that you control. Very few shoppers need chat in the first second.
Recommendation and upsell blocks
"You may also like" and "Frequently bought together" blocks can load extra scripts and product data. Use your platform's native recommendations where possible, and load blocks below the fold as they come into view.
Trust badges, countdown timers and pop-ups
Small additions add up. Countdown timers and stock alerts that update constantly can hurt responsiveness. Pop-ups that appear immediately can harm the experience and shift the layout. Ask whether each one genuinely helps sales.
Fonts, Variant Pickers and Theme Code
Not every slowdown comes from apps. The theme itself can add weight to the product template.
Web fonts
Several font families and weights can delay text from appearing or cause it to swap visibly. Limit the number of weights, preload only the font used above the fold, and use a font-display setting that shows fallback text straight away.
Variant pickers
Selecting a size or colour should feel instant. On products with many variants, some themes run heavy scripts on every tap, rebuilding the gallery, price and stock messages at once. This is a common cause of poor INP. Keep the work done on each selection small, and update only what has changed.
Unused theme features
Feature-rich themes often load code for sections you never use, such as quick view, sticky add-to-cart bars or animations. If your theme lets you switch features off, do it, and check that their scripts stop loading.
How to Find What Is Slowing Your Template
- Run a lab test on a typical product page. Use a tool such as Lighthouse in Chrome DevTools and look at the LCP element, long tasks and third-party scripts.
- Check the network waterfall. In DevTools, sort requests by size and by domain to see which apps load the most.
- Test with widgets turned off. Disable one app at a time on a staging or duplicate theme and compare results.
- Look for leftovers. Uninstalled apps sometimes leave code in theme files that still loads on every page.
- Compare with field data. Lab tests are a guide; Search Console shows what real visitors experience.
Prioritising Fixes
Not every fix is worth the same effort. A sensible order:
- Make the first product image load fast and without layout shift.
- Defer chat, video players and other heavy third-party scripts until they are needed.
- Remove apps and leftover code that no longer earn their place.
- Lazy-load below-the-fold blocks such as reviews and recommendations.
- Fine-tune image sizes, fonts and remaining scripts.
Speed changes should be judged on sales too, not just scores. A faster page that loses a feature shoppers relied on is not a win. Our conversion rate optimisation work looks at both sides together, and our technical SEO service handles template-level performance fixes with developers.
Visual-heavy niches, where galleries and video are essential, feel this trade-off most. Our article on SEO for makeup brands covers one such niche.
FAQs
Does product page speed affect rankings?
Page experience, including Core Web Vitals, is one of many signals Google uses. It rarely outweighs relevance, but slow pages also lose shoppers, so speed affects revenue even where rankings do not move.
Should I lazy-load all product images?
No. Lazy-load additional images, but load the main product image immediately. Lazy-loading the first image is one of the most common causes of slow LCP.
Is it better to host product videos myself?
It depends. Short, compressed clips can be light if self-hosted. Longer videos are usually better on a video platform, embedded with a click-to-load preview so the player only loads when needed.
Want a Faster Product Template?
If your product pages feel slow and you are not sure which app or element is to blame, we can find out. Start with a free SEO audit and we will point out the heaviest elements on your template.
- page speed
- core web vitals
- product pages
- third-party scripts
- image optimisation
Have a question about this for your own site?
A 15-minute call is usually enough to tell whether it applies to you and what to do first.


