Spain · Madrid Completed: Apr 21, 2026 19:51 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 71 / 100
Based on 8 categories, 0 sections
Room to improve — your 24.8s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 10.5 MB (3.9 MB transferred)
Performance issues directly impact user engagement and conversion rates.
1 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/08bd0ecf-872c-401e-a435-bed818827847)<a href="https://beavercheck.com/results/08bd0ecf-872c-401e-a435-bed818827847"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fprestashop.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fprestashop.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 24.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~29%.
Page takes 24.8s to load
+12% bounceUsers abandon at ~3s — you're 22.3s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 1.0s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€425 investment → €0.92/month returns + EUR 120,500,000 risk avoided
€425
5h · 5 findings
€0.92 /mo
~€11 / year
EUR 120,500,000
if kept compliant
€128 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,041,668 / month at risk
~€120,500,011 / year if left unfixed
€120,500,000
+5 more
€0.92 /mo
12420.8 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
8.87 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
24.82 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.02 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
11.24 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
25.19 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
ul.marquee__inner > li.b-color-6 > picture > img ul.marquee__inner > li.b-color-6 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Bleu_Chauffe_... | 245.3 KiB | 242.3 KiB |
ul.marquee__inner--reverse > li.b-color-3 > picture > img ul.marquee__inner--reverse > li.b-color-3 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Surf_UK.jpg | 184.7 KiB | 181.7 KiB |
ul.marquee__inner--reverse > li.b-color-6 > picture > img ul.marquee__inner--reverse > li.b-color-6 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Visiofactory_... | 137.5 KiB | 134.5 KiB |
ul.marquee__inner > li.b-color-4 > picture > img ul.marquee__inner > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Kenable_UK.jpg | 129.9 KiB | 126.9 KiB |
ul.marquee__inner--reverse > li.b-color-5 > picture > img ul.marquee__inner--reverse > li.b-color-5 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Huygens_UK.jpg | 105.7 KiB | 102.6 KiB |
div.strate > div.grid > picture > img div.strate > div.grid > picture > img | dsv16luwmjfsl.cloudfront.net/wp-content/uploads/2023/02/home-800x408.jpg | 75.5 KiB | 61.4 KiB |
ul.marquee__inner--reverse > li.b-color-4 > picture > img ul.marquee__inner--reverse > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_VapeGreen_UK-500x313... | 67.0 KiB | 56.6 KiB |
ul.marquee__inner--reverse > li.b-color-4 > picture > img ul.marquee__inner--reverse > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_Bleu_Chauffe_UK-500x... | 40.8 KiB | 30.4 KiB |
ul.marquee__inner--reverse > li.b-color-6 > picture > img ul.marquee__inner--reverse > li.b-color-6 > picture > img | /wp-content/uploads/2023/03/Homepage_ironheart_UK-500x313... | 39.8 KiB | 29.4 KiB |
ul.marquee__inner > li.b-color-3 > picture > img ul.marquee__inner > li.b-color-3 > picture > img | /wp-content/uploads/2023/03/Homepage_LeChocolat_UK-500x31... | 38.4 KiB | 28.0 KiB |
ul.marquee__inner--reverse > li.b-color-3 > picture > img ul.marquee__inner--reverse > li.b-color-3 > picture > img | /wp-content/uploads/2023/03/Homepage_Magimix_UK-500x313.jpg | 38.2 KiB | 27.8 KiB |
div.sc-fodVek > div.sc-fFucqa > div.sc-dIUeWJ > img.Thumbprint__Img div.sc-fodVek > div.sc-fFucqa > div.sc-dIUeWJ > img.Thumbprint__Img | /2022/01/d35cbf0e-80e7-4b22-b1f0-22a6f9371134.png?bg=a4db... | 30.0 KiB | 25.6 KiB |
ul.marquee__inner > li.b-color-5 > picture > img ul.marquee__inner > li.b-color-5 > picture > img | /wp-content/uploads/2023/03/Homepage_StarName_UK-500x313.jpg | 29.8 KiB | 19.4 KiB |
ul.marquee__inner--reverse > li.b-color-4 > picture > img ul.marquee__inner--reverse > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_Huygens_UK-500x313.jpg | 29.7 KiB | 19.3 KiB |
Logo finsbury div > div.card-partner-logo > picture > img | /wp-content/uploads/2023/03/Push_listing_offre_Finsbury_2... | 15.8 KiB | 15.1 KiB |
Logo Le chocolat des Français div > div.card-partner-logo > picture > img | /wp-content/uploads/2023/03/Push_lechocolatdesfrancais_46... | 8.5 KiB | 5.8 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| js.hsforms.net/forms/embed/v2.js | 192.8 KiB | 2.9 s |
| try.abtasty.com/1b616f091198fe52210ca8ac0cced5f9.js | 3.1 KiB | 169 ms |
| prestashop.com/assets/index.CbxbcfkL.css | 862 B | |
| prestashop.com/assets/index.f8ZJPxZp.css | 9.2 KiB | 333 ms |
| prestashop.com/assets/pageView.DPVMloe3.css | 3.8 KiB | 166 ms |
| prestashop.com/assets/index.B-F31afT.css | 881 B | |
| prestashop.com/assets/disableScroll.WUojVBS5.css | 958 B | |
| prestashop.com/assets/entry.DxqvyvQy.css | 4.6 KiB | |
| prestashop.com/assets/default.DWQT-_dr.css | 504 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| prestashop.com/assets/Y3IQEUIe.js | 263.0 KiB | 124.4 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WHRX84&l=dataLayer | 178.3 KiB | 107.5 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WHRX84 | 178.4 KiB | 82.5 KiB |
| prestashop.com/0n0h/ | 141.8 KiB | 81.8 KiB |
| static.axept.io/sdk.js | 182.5 KiB | 73.4 KiB |
| js.hsforms.net/forms/embed/v2.js | 185.5 KiB | 72.8 KiB |
| www.googletagmanager.com/gtag/destination?id=DC-11945881&cx=c>m=4e64h1 | 130.1 KiB | 61.5 KiB |
| www.clickcease.com/monitor/stat.js | 42.9 KiB | 38.4 KiB |
| try.abtasty.com/1b616f091198fe52210ca8ac0cced5f9/main.ab8d9fe331f2017201ee.js | 59.1 KiB | 33.1 KiB |
| prestashop.com/assets/DgpwG8-t.js | 32.3 KiB | 20.3 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| prestashop.com/assets/Y3IQEUIe.js | 2.9 s | 1.0 s | 4.3 ms |
| prestashop.com/ | 1.1 s | 43 ms | 3.5 ms |
| Unattributable | 1.0 s | 136 ms | 0.0 ms |
| analytics.ahrefs.com/analytics.js | 949 ms | 838 ms | 0.8 ms |
| static.axept.io/sdk.js | 286 ms | 199 ms | 47 ms |
| prestashop.com/0n0h/ | 252 ms | 217 ms | 29 ms |
| www.googletagmanager.com/gtm.js?id=GTM-WHRX84 | 209 ms | 163 ms | 42 ms |
| prestashop.com/cdn-cgi/challenge-platform/scripts/jsd/main.js | 199 ms | 189 ms | 1.9 ms |
| js.hsforms.net/forms/embed/v2.js | 189 ms | 132 ms | 46 ms |
| try.abtasty.com/1b616f091198fe52210ca8ac0cced5f9/main.ab8d9fe331f2017201ee.js | 188 ms | 160 ms | 21 ms |
| www.googletagmanager.com/gtag/destination?id=DC-11945881&cx=c>m=4e64h1 | 145 ms | 116 ms | 28 ms |
| www.googletagmanager.com/gtm.js?id=GTM-WHRX84&l=dataLayer | 72 ms | 27 ms | 38 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.3 s |
| Other | 2.6 s |
| Style & Layout | 813 ms |
| Rendering | 470 ms |
| Script Parsing & Compilation | 292 ms |
| Garbage Collection | 153 ms |
| Parse HTML & CSS | 68 ms |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| :root{--color-1:#fff;--color-2:#000;--color-3:#a4dbe8;--color-4:#bde9c9;--color-5:#decde7;--color-6… | 13.1 KiB | 12.0 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img | /2023/04/e9b42d34-434b-478a-a493-c634d3719a24.png?auto=fo... |
a.cta-login--pattern > span > span.cta-login-icon > img a.cta-login--pattern > span > span.cta-login-icon > img | dsv16luwmjfsl.cloudfront.net/wp-content/uploads/2025/01/Solution_Icon-2.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Control div.col-md-1--1 > div.tabs > div.tablist > button#tab-0 |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.nav > div.mobile > nav.main > button.close div.nav > div.mobile > nav.main > button.close |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.theHeader__container > div.actions > div > a.cta-login--pattern div.theHeader__container > div.actions > div > a.cta-login--pattern |
div.grid > div.col-lg-8 > div.card-article > a div.grid > div.col-lg-8 > div.card-article > a |
div.grid > aside.col-lg-4 > div.card-article > a div.grid > aside.col-lg-4 > div.card-article > a |
div.grid > aside.col-lg-4 > div.card-article > a div.grid > aside.col-lg-4 > div.card-article > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
I refuse div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss |
Fine for me div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
div.sc-fodVek > div.sc-fFucqa > div.sc-dIUeWJ > img.Thumbprint__Img div.sc-fodVek > div.sc-fFucqa > div.sc-dIUeWJ > img.Thumbprint__Img | /2022/01/d35cbf0e-80e7-4b22-b1f0-22a6f9371134.png?bg=a4db... | 200 x 134 | 200 x 134 | 300 x 201 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
div.theHeader__container > div.actions > div > a.cta-conversion--pattern div.theHeader__container > div.actions > div > a.cta-conversion--pattern |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.15 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.57 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
17 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.03 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.68 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.strate > div.grid > picture > img div.strate > div.grid > picture > img | dsv16luwmjfsl.cloudfront.net/wp-content/uploads/2023/02/home-1920x978.jpg | 422.0 KiB | 304.6 KiB |
ul.marquee__inner > li.b-color-6 > picture > img ul.marquee__inner > li.b-color-6 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Bleu_Chauffe_... | 245.3 KiB | 236.9 KiB |
ul.marquee__inner--reverse > li.b-color-3 > picture > img ul.marquee__inner--reverse > li.b-color-3 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Surf_UK.jpg | 184.7 KiB | 176.3 KiB |
ul.marquee__inner--reverse > li.b-color-6 > picture > img ul.marquee__inner--reverse > li.b-color-6 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Visiofactory_... | 137.5 KiB | 129.0 KiB |
ul.marquee__inner > li.b-color-4 > picture > img ul.marquee__inner > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Kenable_UK.jpg | 129.9 KiB | 121.5 KiB |
ul.marquee__inner--reverse > li.b-color-5 > picture > img ul.marquee__inner--reverse > li.b-color-5 > picture > img | /wp-content/uploads/2023/03/Homepage_mobile_Huygens_UK.jpg | 105.7 KiB | 97.2 KiB |
ul.marquee__inner--reverse > li.b-color-4 > picture > img ul.marquee__inner--reverse > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_VapeGreen_UK-500x313... | 67.0 KiB | 41.6 KiB |
div.sc-fodVek > div.sc-fFucqa > div.sc-dIUeWJ > img.Thumbprint__Img div.sc-fodVek > div.sc-fFucqa > div.sc-dIUeWJ > img.Thumbprint__Img | /2022/01/d35cbf0e-80e7-4b22-b1f0-22a6f9371134.png?bg=a4db... | 30.0 KiB | 25.6 KiB |
ul.marquee__inner--reverse > li.b-color-4 > picture > img ul.marquee__inner--reverse > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_Bleu_Chauffe_UK-500x... | 40.8 KiB | 15.3 KiB |
ul.marquee__inner--reverse > li.b-color-6 > picture > img ul.marquee__inner--reverse > li.b-color-6 > picture > img | /wp-content/uploads/2023/03/Homepage_ironheart_UK-500x313... | 39.8 KiB | 14.3 KiB |
ul.marquee__inner > li.b-color-3 > picture > img ul.marquee__inner > li.b-color-3 > picture > img | /wp-content/uploads/2023/03/Homepage_LeChocolat_UK-500x31... | 38.4 KiB | 13.0 KiB |
ul.marquee__inner--reverse > li.b-color-3 > picture > img ul.marquee__inner--reverse > li.b-color-3 > picture > img | /wp-content/uploads/2023/03/Homepage_Magimix_UK-500x313.jpg | 38.2 KiB | 12.7 KiB |
Logo finsbury div > div.card-partner-logo > picture > img | /wp-content/uploads/2023/03/Push_listing_offre_Finsbury_2... | 15.8 KiB | 6.4 KiB |
Logo Le chocolat des Français div > div.card-partner-logo > picture > img | /wp-content/uploads/2023/03/Push_lechocolatdesfrancais_46... | 8.5 KiB | 5.8 KiB |
ul.marquee__inner > li.b-color-5 > picture > img ul.marquee__inner > li.b-color-5 > picture > img | /wp-content/uploads/2023/03/Homepage_StarName_UK-500x313.jpg | 29.8 KiB | 4.4 KiB |
ul.marquee__inner--reverse > li.b-color-4 > picture > img ul.marquee__inner--reverse > li.b-color-4 > picture > img | /wp-content/uploads/2023/03/Homepage_Huygens_UK-500x313.jpg | 29.7 KiB | 4.2 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| js.hsforms.net/forms/embed/v2.js | 192.8 KiB | 588 ms |
| prestashop.com/assets/index.CbxbcfkL.css | 872 B | |
| try.abtasty.com/1b616f091198fe52210ca8ac0cced5f9.js | 3.1 KiB | 249 ms |
| prestashop.com/assets/disableScroll.WUojVBS5.css | 931 B | |
| prestashop.com/assets/pageView.DPVMloe3.css | 3.8 KiB | |
| prestashop.com/assets/default.DWQT-_dr.css | 452 B | |
| prestashop.com/assets/index.f8ZJPxZp.css | 9.1 KiB | 52 ms |
| prestashop.com/assets/entry.DxqvyvQy.css | 4.6 KiB | |
| prestashop.com/assets/index.B-F31afT.css | 968 B | 52 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| prestashop.com/assets/Y3IQEUIe.js | 263.0 KiB | 114.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WHRX84&l=dataLayer | 178.3 KiB | 107.5 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WHRX84 | 178.4 KiB | 82.5 KiB |
| prestashop.com/0n0h/ | 141.8 KiB | 81.6 KiB |
| static.axept.io/sdk.js | 182.3 KiB | 73.2 KiB |
| js.hsforms.net/forms/embed/v2.js | 185.4 KiB | 72.8 KiB |
| www.googletagmanager.com/gtag/destination?id=DC-11945881&cx=c>m=4e64h1 | 130.1 KiB | 61.5 KiB |
| www.clickcease.com/monitor/stat.js | 42.9 KiB | 38.4 KiB |
| try.abtasty.com/1b616f091198fe52210ca8ac0cced5f9/main.ab8d9fe331f2017201ee.js | 59.1 KiB | 33.1 KiB |
| prestashop.com/assets/DgpwG8-t.js | 32.3 KiB | 20.2 KiB |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| :root{--color-1:#fff;--color-2:#000;--color-3:#a4dbe8;--color-4:#bde9c9;--color-5:#decde7;--color-6… | 13.1 KiB | 11.8 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img | /2023/04/e9b42d34-434b-478a-a493-c634d3719a24.png?auto=fo... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Discover PrestaShop
The technology behind your ecommerce success div.expand > div.inner > ul > li |
Create an online store
Discover all the ways you can sell online with PrestaShop div.expand > div.inner > ul > li |
Examples of websites
Discover some of the best PrestaShop stores to inspire you… div.expand > div.inner > ul > li |
PrestaShop Marketplace
Explore the marketplace for all your modules and themes div.expand > div.inner > ul > li |
PrestaShop Experts
Hire a professional to help you with store creation, design,… div.expand > div.inner > ul > li |
Support plans
Get personalized help from our technical and support team div.expand > div.inner > ul > li |
Migration solutions
Explore our offers to migrate your ecommerce site to Presta… div.expand > div.inner > ul > li |
Hosting
Find the best hosting provider for your PrestaShop store div.expand > div.inner > ul > li |
Open source project
Learn more about the PrestaShop project and the open source… div.expand > div.inner > ul > li |
PrestaShop Community Slack
Ask questions, connect with contributors, and follow… div.expand > div.inner > ul > li |
Forum
Engage in discussions and ask questions to the community div.expand > div.inner > ul > li |
Events
Browse our calendar to find events near you or online div.expand > div.inner > ul > li |
PrestaShop Million Club
Join the club for merchants generating more than 1 mill… div.expand > div.inner > ul > li |
Care Center
Learn how to use PrestaShop and get answers to your questions div.expand > div.inner > ul > li |
Resource library
Guides, webinars, white papers, and best practices to grow you… div.expand > div.inner > ul > li |
Blog
Stay up to date with the latest PrestaShop news and read inspiring ecommer… div.expand > div.inner > ul > li |
Control div.col-md-6 > div.tabs > div.tablist > button#tab-0 |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.grid > div.col-lg-8 > div.card-article > a div.grid > div.col-lg-8 > div.card-article > a |
div.grid > aside.col-lg-4 > div.card-article > a div.grid > aside.col-lg-4 > div.card-article > a |
div.grid > aside.col-lg-4 > div.card-article > a div.grid > aside.col-lg-4 > div.card-article > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Sitemap div.col-lg-8 > ul.secondary > li > a |
Legal Notice div.col-lg-8 > ul.secondary > li > a |
PrestaShop Security Charter div.col-lg-8 > ul.secondary > li > a |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
I refuse div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss |
Fine for me div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
div.theHeader__container > div.actions > div > a.cta-conversion--pattern div.theHeader__container > div.actions > div > a.cta-conversion--pattern |
To appear in search results, crawlers need access to your app.
Send Feedback