Speed up PrestaShop pages by adding lazy loading and decoding attributes to store images
Automatic SEO Images Lazy Tags is a module for PrestaShop stores that gives visible images first priority and delays catalogue and content images further down the page until they are needed. Installation activates a sensible default, while every adjustment remains on one compact settings screen.
Image-heavy categories and long product descriptions often make the browser fetch pictures that are still far outside the current view. Those requests compete with the main product photograph, name, price and buying controls, especially on a mobile connection.
A global switch controls the feature, an individual exception keeps any selected image immediate, and a separate option lets the browser prepare images without holding up the visible page. Existing image decisions remain intact, and neither the image files nor the saved descriptions are rewritten.
The module applies one consistent policy to product pages, category and search results, home-page product sections, recommendations, banners and images inside product, category, brand and information-page content. Main and first-screen images remain immediate, later images wait their turn, and the same behaviour continues after filtering and pagination.
The result is a quicker first view, less unnecessary image transfer, automatic treatment of existing and future content, and precise control when a particular image needs different handling.
What changes when the module is installed?
Automatic SEO Images Lazy Tags manages when images are fetched throughout a PrestaShop store. Visible and important images arrive first, while eligible images farther down a page wait until the visitor approaches them. The module starts active with practical defaults and keeps every setting on one screen.
- Immediate start. Existing pages follow the new image policy as soon as the module is installed.
- First-view priority. Main product photos and other critical visuals remain immediate.
- Store-wide coverage. Catalogue placements, editorial content and dynamically refreshed results follow the same rule.
- Respect for existing work. Content, files and deliberate image choices remain intact.
- Focused control. Global use, individual exceptions and browser image preparation are managed separately.
- A lighter first view. Images that are not yet useful stop competing with the products already on screen.
One installation therefore covers the catalogue already in the store and the products and pages added later, without a page-by-page editing project.
Which images keep first priority?
The module distinguishes the first view from the rest of the page. A main product photograph, a visible category image or a top banner stays immediate, while later gallery photographs, products farther down a list and images deep inside a description wait until they are close to the screen.
An individual exception is also available for any image that must appear at once. This combines safe automatic decisions with exact merchant control, so improving the first view never means delaying the visual that sells the product.
Where does automatic image loading apply?
Product pages, category and search lists, home-page product selections, recommendations, related products, category thumbnails and storefront banners all follow the same loading policy. Results replaced after filtering or pagination keep that behaviour, with no second setup for the refreshed list.
The coverage also reaches images already placed inside product descriptions, category and brand text, and information pages. It works with supported shop themes and continues after theme updates, giving a large catalogue one consistent rule instead of a collection of isolated fixes.
What happens to existing content and theme choices?
The module works while the shop prepares a page and does not rewrite saved descriptions or alter image files. Existing content receives the policy automatically, newly added content follows it too, and removing the module leaves the original material as it was.
When a theme or editor has already made an explicit image-loading choice, that choice remains authoritative. Images embedded by the editor are handled safely regardless of letter case or ordinary source formatting, while embedded images that should stay self-contained are left alone.
How much control fits on one screen?
The standard setup needs no tuning: automatic image loading and smoother browser preparation are active after installation. A main switch pauses the behaviour for the whole store, and the browser-preparation option has its own switch.
The exclusion marker provides the deeper layer. Its name is adjustable to match the shop, and applying it to one chosen image keeps that image immediate without changing the policy everywhere else. The configuration stays short while still covering the exceptions that matter in a real catalogue.
What stays untouched in the shop?
The module changes the order in which eligible images are fetched. It does not compress, convert or replace the photographs, requires no outside image account and sends no customer or image data to another service. The shop retains its original files and visual quality.
No extra storefront program has to watch the page or be restarted after a filtered result appears. The practical outcome is less work at the first view, fewer images transferred before they are useful, and a performance improvement that follows the catalogue as it grows.
-
Referencemprseoimageslazytags
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.7 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront & Back-office
-
GDPR RelevantNo
-
Business GoalIncrease Traffic
-
External Account NeededNo
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageAttract Visitors
-
Works With PlatformNo External Platform
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Speed up image-heavy PrestaShop pages by adding browser-native lazy loading to eligible product images, listing images, and editable HTML content. The module adds loading="lazy" and, when enabled, decoding="async" at PrestaShop presenter/content level, so it avoids rewriting the whole rendered page.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1321
questions
9
categories
2014
building modules since
1.6–9
PrestaShop versions
v1.0.112026-05-27
- Addedcomplete FR/DE/ES/IT/PL translations
- FixedRegister lazy image tag autoload namespace
- FixedMigrate config to ConfigTable, fix parse error in deleteConfigs
Loading full changelog...
Works Well With Automatic SEO Images Lazy Tags
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
Automatic SEO Images Lazy Tags is already making image-heavy pages feel faster by deferring offscreen product, listing and content images. Speed handled, but the images it defers may still carry weak or missing descriptions, which leaves accessibility and image-search context unaddressed.
Automatic SEO Images Alt Tags covers that description side, generating alt text from templates for product, listing and category images without manual field editing. The two tools improve the same images along different axes: one controls when they load, the other clarifies what they depict, each managed on its own.
Together you get pages that are both lighter and better described. Shoppers using assistive technology gain useful context while everyone benefits from faster perceived load, so the performance work you started with lazy loading is matched by an accessibility and image-context improvement, rather than leaving one of the two half-done.
Complement
Automatic SEO Images Lazy Tags tackles one visible cause of slow pages by deferring offscreen images, but image loading is only part of what makes a PrestaShop store fast. Cache layers, asset handling and server-side bottlenecks all shape real-world speed and sit outside what an image attribute can influence.
Performance Revolution covers that broader territory, giving your team practical controls for caching, warming, asset handling and bottleneck analysis in one back office area, with Redis, APCu and auto-detect options. It works alongside lazy loading as a separate, wider-scope tool rather than replacing it.
The payoff is speed addressed at more than one level. Lazy loading keeps image-heavy pages light while Performance Revolution works on caching and bottlenecks behind them, so slow pages are less likely to waste paid traffic or push shoppers to abandon before checkout, with each tool handling the part of performance it is built for.
Complement
A store using Automatic SEO Images Lazy Tags has improved front-end image delivery, but much of PrestaShop's real speed depends on server-side caching that an image attribute cannot reach. If Redis is misconfigured or unverified, pages can stay slow no matter how images load.
Redis Dashboard & Key Manager covers that infrastructure side, giving you a back office panel to configure, test and clean Redis, with connection settings and live metrics such as version, uptime and memory. It works alongside lazy loading as a separate concern: one lightens the browser's image work, the other helps confirm your cache backend is connected and healthy.
Running both, you address speed from the browser and from the cache layer. Lazy loading defers images shoppers cannot see yet while Redis Dashboard & Key Manager makes your Redis setup easier to verify and maintain, so you are less likely to leave performance on the table because the cache was quietly broken behind otherwise well-optimised pages.
Measurement
Automatic SEO Images Lazy Tags handles one well-known speed improvement, but on a real store it is hard to know whether deferred images are your actual bottleneck or a minor factor next to slow queries, cache problems or heavy theme assets.
Performance Audit answers that as a service, profiling your live site across PHP, slow queries, cache and CCC, Core Web Vitals, the image pipeline, theme assets, hosting and CDN, then ranking each bottleneck by its real impact on load time and conversions. It diagnoses rather than changes anything, complementing the module.
The benefit is evidence over guesswork. You keep lazy loading active for its front-end gains while the audit tells you, in priority order, where the remaining speed problems actually are, so your next performance investment targets the cause with the biggest effect rather than another assumed fix.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
