Skip to content
All articles

Core Web Vitals on PrestaShop — the field guide

Published on 22 Jul 2026 · 3 min read · Updated on 28 Jul 2026

Core Web Vitals are the only performance criterion Google has explicitly folded into its ranking. On PrestaShop they are also the ground where many stores lose points without knowing it — heavy themes, stacked modules, unoptimised images. Three metrics are enough to know where you stand. Here they are, and what to fix first.

The three metrics, plainly

  • LCP (Largest Contentful Paint) — the time before the largest visible element appears (often the banner image or the product photo). Target: under 2.5 s. This is the metric most tied to the feeling that "the site is slow".
  • INP (Interaction to Next Paint) — responsiveness: the delay between a click and the page's visible answer. Target: under 200 ms. INP replaced FID in early 2024.
  • CLS (Cumulative Layout Shift) — visual stability: do elements jump around while the page loads? Target: under 0.1. The classic culprit: an image or an ad with no reserved dimensions.

Measure them on real data (the Core Web Vitals report in Search Console) rather than on a single synthetic test: what counts is the experience of your actual visitors.

Why PrestaShop often struggles

Four recurring causes:

  1. Uncompressed, badly sized images. A 2 MB product photo served at full resolution sinks the LCP. Modern format (WebP), adapted dimensions, lazy loading below the fold.
  2. Too much module JavaScript. Every module adds its own JS; stacked up, they degrade INP. Audit and disable what you do not use.
  3. A heavy theme. Premium themes multiply sliders and fonts. Every web font and every slider has a cost.
  4. No cache, no compression. Turn on the PrestaShop cache, CSS/JS minification and server compression (gzip or brotli).

The order to fix things in

Do not fix everything at once — prioritise by impact:

  1. Images first (LCP): the best effort-to-gain ratio on a store.
  2. Cache and compression next: a server setting, immediate effect across the whole site.
  3. Hunting JS modules (INP): slower work, but necessary if interactivity drags.
  4. Dimensions and reserved space (CLS): quick, and often forgotten.

Performance does not excuse you from content

A fast but empty site does not rank any better: speed is a tie-breaker, not a traffic generator. It works alongside a solid base — the PrestaShop SEO guide lays that base, structured data enriches the results, and content (a blog and product pages) brings the traffic. Optimise speed, but do not stop there.

Worth knowing: a blog served by a lightweight module does not weigh the store down, unlike an external solution stuffed with scripts — something to check under PrestaShop compatibility.

FAQ

Are Core Web Vitals a strong ranking factor? Moderate but real: with equal content, the faster page goes ahead. Never sacrifice content for speed.

Do I need a perfect score? No: hitting "good" (green) on all three metrics is enough. 100/100 has diminishing returns.

In short

LCP, INP, CLS: measure on real data, fix images first, then cache, JS and stability. Speed decides between equals — it replaces neither the SEO groundwork nor the content that actually brings visitors in.

For those who do the work

You hold the pen. Publium holds the rest.

Opportunity detection on Search Console data, drafts anchored in the catalog, tags to spec, publishing and follow-up. What stays yours: the angle, the judgment, the proofreading — the work that doesn’t automate.

Your details are only used to get back to you.

This site is protected by reCAPTCHA; the Google Privacy Policy & Terms of Service apply.