PrestaShop Performance Optimization: Accelerate Your Store

PrestaShop Performance Optimization

In a typical PrestaShop 8.x store with 2000+ products, TTFB fluctuates between 1.5 and 4 seconds. This pushes Core Web Vitals into the red zone: LCP exceeds 4s, and CLS accumulates from uncompressed images. Owners complain about slow admin panels and freezes during catalog updates. The default configuration includes Smarty compilation without cache, ORM with N+1 queries, and file-based caching. We've rebuilt dozens of such stores: the right stack—Redis, OPcache, optimized MySQL indexes, and proper nginx—delivers TTFB of 200–500 ms. Over the years, we have completed more than 30 projects for speeding up PrestaShop, and we guarantee results. The problem worsens with increasing server load: each additional second of loading time reduces conversion by 2% (Google study).

Why PrestaShop Slows Down on Default Configuration

A standard PrestaShop installation prioritizes versatility over speed. Bottlenecks:

• Smarty templates compile without caching—each request rebuilds templates.
• CCC (Combine, Compress, Cache) is not enabled by default—CSS and JS load separately.
• File caching is slow with a large number of products.
• Database queries lack indexes on key tables (ps_product_lang, ps_category_product, ps_search_word).

We diagnosed a store with 5000 products: a category page loaded in 3.2 seconds. After configuring Redis, enabling CCC, and adding indexes, the time dropped to 0.4 seconds—that's 8 times faster.

How to Speed Up PrestaShop

1. Enable built-in caching — turn on Smarty cache, CCC, and minification.
2. Switch to Redis — replace file cache with Redis. Redis PrestaShop integration is straightforward and delivers up to 5 times faster caching than file-based storage.
3. Optimize the database — add indexes, configure slow query log.
4. Configure OPcache — allocate 256MB and 20000 files.
5. Enable WebP — reduce image size by 25–40%.
6. Audit modules — disable unused ones, especially SEO and live chat.

Built-in PrestaShop Caching

Admin > Advanced Parameters > Performance — the main optimization panel.

Smarty:

• Template compilation: Never recompile template files
• Cache: Yes
• Multi-front optimizations: Yes
• Clear cache: Never clear cache files

CCC:

• Smart cache for stylesheets: Yes
• Smart cache for JavaScript: Yes
• Apache optimization: Yes (generates .htaccess rules)
• Minify HTML: Yes

Media servers — specify a CDN domain for static content, if used.

Memcache/Redis as Cache Backend

Switching from file cache to Redis yields a 30–50% boost. Config: Admin > Advanced Parameters > Performance > Caching — select the system, add server 127.0.0.1:6379. For Redis, additionally in config/config.inc.php:

define('_PS_CACHE_ENABLED_', '1');
define('_PS_CACHING_SYSTEM_', 'CacheRedis');

CacheRedis in PrestaShop 8 works via Predis. Using the phpredis extension is 15–20% faster.

Comparison of caching methods:

PHP OPcache

opcache.enable=1
opcache.memory_consumption=256
opcache.max_accelerated_files=20000
opcache.validate_timestamps=0
opcache.revalidate_freq=0
opcache.interned_strings_buffer=32
opcache.fast_shutdown=1

PrestaShop has a large codebase—max_accelerated_files=20000 is mandatory; the default 10000 is insufficient.

MySQL: Indexes and Slow Log

ALTER TABLE ps_product_lang
  ADD INDEX idx_id_lang (id_lang, id_product);

ALTER TABLE ps_category_product
  ADD INDEX idx_id_category_pos (id_category, position);

ALTER TABLE ps_search_word
  ADD INDEX idx_word (word(50));

Slow query log:

[mysqld]
slow_query_log = 1
slow_query_log_file = /var/log/mysql/prestashop-slow.log
long_query_time = 1
log_queries_not_using_indexes = 1

A typical culprit is the getProducts() query with sorting by sales without an index on ps_product_sale. Adding an index reduces query time from 2 seconds to 10 ms.

Modules and Their Impact on Speed

Each active module adds hooks. Diagnosis: temporarily enable _PS_DEBUG_PROFILING_ in config/defines.inc.php—a Debugger bar appears showing execution time per hook.

Problematic module categories:

• SEO modules—often make 3–10 additional queries per page.
• Live chat modules—load external scripts synchronously.
• Review modules—COUNT queries without cache for each product in the listing.

After disabling unnecessary modules, server load drops by half.

Nginx Configuration

# Static files
location ~* \.(jpg|jpeg|png|webp|gif|ico|svg|woff2|css|js)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
    access_log off;
    try_files $uri =404;
}

# Gzip
gzip on;
gzip_types text/plain text/css application/json application/javascript image/svg+xml;
gzip_comp_level 5;
gzip_min_length 512;
gzip_vary on;

# Prevent direct access to PrestaShop classes
location ~* \.(log|tpl|twig|sass|yml|lock)$ {
    deny all;
}

WebP and Images

PrestaShop 1.7.7+ supports WebP: Admin > Design > Image settings — enable WebP formats. Image size decreases by 25–40%. On a listing page of 24 products, this saves 500–800 KB. After enabling, regenerate thumbnails.

What Is Included in the Optimization Work?

Our comprehensive PrestaShop optimization includes the following stages and deliverables:

Deliverables

• Detailed documentation of all changes
• Access to performance reports and dashboards
• Team training session on maintaining speed
• 7 days of post-optimization support

Result: TTFB drops to 200–500 ms, LCP enters the green zone of Core Web Vitals. You receive a report with recommendations and a guarantee on the work performed.

Experience and Guarantees

Our team has many years of experience in web development and has completed over 50 e-commerce optimization projects. We use only proven methodologies and provide a written guarantee on the result. Contact us for a free PrestaShop audit. Get a consultation and start optimizing today.

Timeline and Cost

Timeline: from 2 to 5 days depending on complexity. Cost is calculated individually after the audit. Our ecommerce speed optimization starts from $500 and can boost revenue by 20% based on conversion improvements. For a store with $50,000 monthly revenue, that's an additional $10,000 per month.

Improve your PrestaShop speed today. Focus on prestashop database optimization and prestashop 8 performance enhancements to maximize store loading speed. Ensure your prestashop ttfb is under 200ms with our proven methods.

Why are Core Web Vitals critical for technical SEO?

PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.

Core Web Vitals: what really affects rankings

Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.

LCP: why 8 seconds is not an image problem

LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.

Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.

Solution:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. Remove render-blocking scripts above hero with defer

Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.

If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.

CLS: what causes layout shifts and how to stop them

CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.

Sources:

• Images without dimensions. <img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
• Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via min-height or load before main content.
• Web fonts. font-display: swap with size-adjust minimizes CLS.
• Dynamic content — add skeleton placeholder with dimensions.

INP: why interface freezes for 500ms

INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.

Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.

Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:

• Processing large list without requestIdleCallback or requestAnimationFrame
• Heavy event listeners without debounce/throttle
• Synchronous setState in React triggering full re-render
• Third-party scripts on main thread

Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.

How do structured data and Schema.org improve search visibility?

Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.

Markup types by scenario:

• E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
• Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
• Local business: LocalBusiness with address, telephone, openingHours, geo.
• FAQ: FAQPage with mainEntity — questions appear as expandable block.

Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.

How to conduct a technical SEO audit

Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.

Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.

JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.

Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.

Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.

What does the optimization process look like?

What deliverables do you receive?

• Documentation: report of found issues, priority roadmap, timelines for each stage.
• Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
• Training: one or two calls reviewing typical mistakes for your team.
• Support: one month accompaniment after deployment — metric checks, regression fixes.

How many positions can you regain through technical SEO?

We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.

Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.