Page speed and Google Shopping: what to fix first

Google’s landing page help says slow load times can lead to landing page disapprovals, and points you to PageSpeed Insights to find what is slowing you down. Measure a product page on a phone, fix the heaviest delay first, and aim for Google’s Core Web Vitals targets.

Minor4 min read

By Edvinas Ivanauskas How the guides are reviewed

Why this matters

Google's “How to fix: Landing page not working” page puts speed on the checklist: “Use tools like Google PageSpeed Insights to identify and fix issues that may be slowing down your mobile or desktop landing pages.” The same step warns that slow load times can end in landing page disapprovals. The “About landing page requirements” page explains why speed matters for Shopping: “Long loading times may be inconvenient, and could prevent Google from getting information from your website.” And the “Link [link]” attribute page puts the shopper's side plainly: “Lengthy loading times cause your users to have a negative experience.”

Google Search Central supplies the targets, the Core Web Vitals. For loading: “strive to have LCP occur within the first 2.5 seconds of the page starting to load”. For responsiveness: “strive to have an INP of less than 200 milliseconds”. For stability: “strive to have a CLS score of less than 0.1”. Its summary: “We highly recommend site owners achieve good Core Web Vitals for success with Search and to ensure a great user experience generally.”

Stability has a Shopping angle of its own. The landing page requirements say “Make sure your pricing and availability information is consistent through the process of page load.” and “Do not change displayed product information after initial loading.” A currency or discount app that rewrites the price a second after the page appears is a speed problem and a price problem at once.

Often the weight is not the theme at all. It is the apps: reviews, chat, upsells, pop-ups and trackers, each adding a script, plus hero images uploaded straight off a camera. Removing an app you forgot you installed can do more than any setting, and it costs nothing.

The free scan does not time your pages; PageSpeed Insights is the right free tool for that. The scan opens your store in a real browser at phone width and flags a page with no mobile viewport setting, and contact details or policy links the desktop footer shows that the phone version leaves out. Read landing page errors for what happens when a page does not load at all.

Typical evidence

Slow pages leave less room for the content

A page can render slowly when synchronous third-party scripts block the main content. Measure real page performance and make product and policy text available quickly; a public scan cannot know another system’s time budget.

Time to interactive0.0s

0sperformance review point12s

Use the marker as a review prompt, not a published crawl limit. Improve slow first-byte times, defer non-critical scripts, and measure the live page again.

Low direct risk, high amplification: a page an automated browser cannot finish reading leaves incomplete data for a storefront audit. Check the policy and product pages with the same access conditions a visitor meets.

The public signals this check looks for:

On a phone, the price and Add to cart button appear only after several seconds of blank or…
On a phone, the price and Add to cart button appear only after several seconds of blank or shifting layout.
A stack of apps, reviews, chat, upsells, pop-ups and trackers, each loads its own scripts …
A stack of apps, reviews, chat, upsells, pop-ups and trackers, each loads its own scripts before the product details appear.
Hero and product images are uploaded at camera size and scaled down in the browser
Hero and product images are uploaded at camera size and scaled down in the browser.
The price or stock message changes after the page loads, because a currency, discount or s…
The price or stock message changes after the page loads, because a currency, discount or stock app rewrites it.
Fonts, sliders and video in the first screen hold up everything below them
Fonts, sliders and video in the first screen hold up everything below them.
Every page takes a long time to send its first byte, because of slow hosting or no caching…
Every page takes a long time to send its first byte, because of slow hosting or no caching.

What it looks like once it is right

The same page serves a resized image, drops two unused apps, reserves space for the reviews, and has the price in the page from the start. PageSpeed Insights on mobile shows its Core Web Vitals in the good range.

Common mistakes

Common mistake

A product page loads a 4 MB hero image, three review widgets and a chat script before the price appears. On a phone the price shows after several seconds, and the Add to cart button jumps down the page when the reviews arrive.

Fix checklist

Run a product page, a collection page and your homepage through PageSpeed Insights on mobile. Write down the Core Web Vitals results and the top suggestions before you change anything.
Uninstall apps you no longer use, and check the theme for leftover code from apps you already removed; some leave scripts behind.
Resize and compress images to the size they display at, use your platform’s modern image formats, and lazy-load images below the first screen.
Reserve space for images, banners and review widgets, so the layout does not jump as they load.
Make sure the price, currency and stock message are in the page when it first loads, not written in afterwards by a script.
If the first response is slow on every page, talk to your host or platform about caching, or move to better hosting.
Re-run PageSpeed Insights after each change, one change at a time, so you know which fix earned its keep.

Defer the scripts that block the content

The HTML can arrive fast and the page can still render slowly when third-party tags load synchronously before the main content. Move non-essential work after core content and measure the page again; a scan cannot know another system’s time budget.

Before — synchronouscontent at 8.4s

chat widget

analytics

retargeting

product content

performance review point

After — deferredcontent at 1.6s

product content

chat widget

analytics

Start by measuring first-byte time and real rendering on the affected page. Defer non-critical scripts and use a CDN where it helps shoppers; avoid presenting one threshold as a platform guarantee.

Questions merchants ask

Can a slow website get Google Shopping products disapproved?

Google's “Landing page not working” help page says slow load times can lead to landing page disapprovals, and asks you to use tools like PageSpeed Insights to fix what is slowing your pages down. It names no single cut-off time, so aim for the Core Web Vitals targets and test on a phone.

What page speed does Google recommend?

Google's Core Web Vitals targets are Largest Contentful Paint within 2.5 seconds of the page starting to load, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Measure them for a product page on mobile in PageSpeed Insights.

What should I fix first on a slow store?

Whatever PageSpeed Insights puts at the top of its list for a product page on mobile. Often that is oversized images, or app scripts that load before the product details; removing one unused app can do more than any setting. Change one thing at a time and re-test.

Remediation

Risk signal

Shoppers do not wait long for a slow product page, and Google’s own help ties slow load times to landing page trouble. Measure on a phone, cut the heaviest app first, and test again after every install.

PriorityLow priority on its own — clear it as housekeeping so the record is complete.

EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

Last reviewed 25 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.