PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 13, 2025, 6:00:27 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.3 s
Page LoadsGood (≤ 2.5 s)91%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)4%75th Percentile - 1.3 sCore Web Vital
Interaction to Next Paint (INP)
213 ms
Page LoadsGood (≤ 200 ms)72%Needs Improvement (200 ms - 500 ms)21%Poor (> 500 ms)6%75th Percentile - 213 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)90%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)8%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.2 s
Page LoadsGood (≤ 1.8 s)88%Needs Improvement (1.8 s - 3 s)8%Poor (> 3 s)5%75th Percentile - 1.2 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)88%Needs Improvement (0.8 s - 1.8 s)8%Poor (> 1.8 s)3%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.2 s
Page LoadsGood (≤ 2.5 s)94%Needs Improvement (2.5 s - 4 s)4%Poor (> 4 s)2%75th Percentile - 1.2 sCore Web Vital
Interaction to Next Paint (INP)
217 ms
Page LoadsGood (≤ 200 ms)72%Needs Improvement (200 ms - 500 ms)22%Poor (> 500 ms)6%75th Percentile - 217 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)93%Needs Improvement (0.1 - 0.25)3%Poor (> 0.25)5%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.1 s
Page LoadsGood (≤ 1.8 s)92%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)3%75th Percentile - 1.1 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)86%Needs Improvement (0.8 s - 1.8 s)12%Poor (> 1.8 s)2%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
43 FCP+4LCP+0TBT+14CLS+25SI+1 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
3.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
17.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.057
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
10.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 13, 2025, 6:00 PM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 387 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 131.0.6778.264 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Largest Contentful Paint element 17,290 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
Phase
% of LCP
Timing
TTFB
3%
600 ms
Load Delay
7%
1,280 ms
Load Time
14%
2,470 ms
Render Delay
75%
12,930 ms
Reduce JavaScript execution time 2.4 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
jysk.fr
1st party
1,807 ms
1,263 ms
96 ms
1,372 ms
1,161 ms
81 ms
173 ms
8 ms
4 ms
171 ms
23 ms
7 ms
91 ms
70 ms
4 ms
Google Tag Manager
tag-manager
779 ms
714 ms
28 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
518 ms
494 ms
12 ms
180 ms
145 ms
10 ms
/gtag/destination?id=…
(www.googletagmanager.com)
81 ms
75 ms
6 ms
Unattributable
289 ms
4 ms
0 ms
Unattributable
289 ms
4 ms
0 ms
Trusted Shops
utility
169 ms
140 ms
7 ms
/assets/fr-FR.5d928e0….chunk.js
(widgets.trustedshops.com)
112 ms
93 ms
0 ms
/assets/trustbadge.js
(widgets.trustedshops.com)
57 ms
47 ms
7 ms
Dynamic Yield
customer-success
166 ms
131 ms
15 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
101 ms
73 ms
12 ms
…2.47.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
65 ms
58 ms
3 ms
cookieinformation.com
72 ms
30 ms
2 ms
/uc.js
(policy.cookieinformation.com)
72 ms
30 ms
2 ms
Minimize main-thread work 3.5 s
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 workTBT
Category
Time Spent
Script Evaluation
2,422 ms
Style & Layout
335 ms
Other
242 ms
Garbage Collection
195 ms
Script Parsing & Compilation
179 ms
Parse HTML & CSS
88 ms
Rendering
35 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 440 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
373 KiB
432 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
147 KiB
276 ms
135 KiB
127 ms
/gtag/destination?id=…
(www.googletagmanager.com)
90 KiB
29 ms
2 KiB
0 ms
Trusted Shops
utility
72 KiB
7 ms
/assets/trustbadge.js
(widgets.trustedshops.com)
55 KiB
6 ms
/js/XC5CA20EC….js
(widgets.trustedshops.com)
2 KiB
1 ms
/assets/fr-FR.5d928e0….chunk.js
(widgets.trustedshops.com)
4 KiB
0 ms
…images/sprite.fa10bbb….svg
(widgets.trustedshops.com)
12 KiB
0 ms
Dynamic Yield
customer-success
160 KiB
0 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
116 KiB
0 ms
…2.47.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
33 KiB
0 ms
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
9 KiB
0 ms
/st?sec=…
(st-eu.dynamicyield.com)
3 KiB
0 ms
cookieinformation.com
250 KiB
0 ms
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
225 KiB
0 ms
/uc.js
(policy.cookieinformation.com)
16 KiB
0 ms
…jysk.fr/cabl.json
(policy.app.cookieinformation.com)
6 KiB
0 ms
/cookiesharingiframe.html
(policy.app.cookieinformation.com)
4 KiB
0 ms
JSDelivr CDN
cdn
2 KiB
0 ms
…dist/js.cookie.min.js
(cdn.jsdelivr.net)
2 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
Google/Doubleclick Ads
ad
1 KiB
0 ms
1 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
Eliminate render-blocking resources Potential savings of 2,220 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
DrupalConsider using a module to inline critical CSS and JavaScript, and use the defer attribute for non-critical CSS or JavaScript.
URL
Transfer Size
Potential Savings
Dynamic Yield
customer-success
124.6 KiB
2,000 ms
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
8.9 KiB
770 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
115.7 KiB
1,230 ms
jysk.fr
1st party
181.2 KiB
2,100 ms
70.7 KiB
900 ms
54.4 KiB
600 ms
53.5 KiB
450 ms
2.6 KiB
150 ms
JSDelivr CDN
cdn
1.6 KiB
750 ms
…dist/js.cookie.min.js
(cdn.jsdelivr.net)
1.6 KiB
750 ms
Reduce unused CSS Potential savings of 118 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.LCPFCP
DrupalConsider removing unused CSS rules and only attach the needed Drupal libraries to the relevant page or component in a page. See the Drupal documentation for details. To identify attached libraries that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/module responsible from the URL of the stylesheet when CSS aggregation is disabled in your Drupal site. Look out for themes/modules that have many stylesheets in the list which have a lot of red in code coverage. A theme/module should only attach a stylesheet library if it is actually used on the page.
URL
Transfer Size
Potential Savings
jysk.fr
1st party
124.1 KiB
117.6 KiB
70.2 KiB
65.3 KiB
53.9 KiB
52.3 KiB
Avoid an excessive DOM size 2,461 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
2,461
Maximum DOM Depth
div > div.brand-item > a.d-block > img.img-responsive
<img src="" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
21
Maximum Child Elements
div.col-12 > div.slick-slider > div.slick-list > div.slick-track
<div class="slick-track" style="width: 4416px; opacity: 1; transform: translate3d(-368px, 0px, 0px);">
24
Reduce unused JavaScript Potential savings of 890 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
DrupalConsider removing unused JavaScript assets and only attach the needed Drupal libraries to the relevant page or component in a page. See the Drupal documentation for details. To identify attached libraries that are adding extraneous JavaScript, try running code coverage in Chrome DevTools. You can identify the theme/module responsible from the URL of the script when JavaScript aggregation is disabled in your Drupal site. Look out for themes/modules that have many scripts in the list which have a lot of red in code coverage. A theme/module should only attach a script library if it is actually used on the page.
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
jysk.fr
1st party
983.3 KiB
662.9 KiB
814.5 KiB
523.6 KiB
100.7 KiB
81.5 KiB
46.9 KiB
36.9 KiB
21.3 KiB
20.9 KiB
Google Tag Manager
tag-manager
367.6 KiB
134.1 KiB
133.6 KiB
53.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
88.5 KiB
43.8 KiB
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
145.5 KiB
37.1 KiB
Dynamic Yield
customer-success
114.8 KiB
66.2 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
114.8 KiB
66.2 KiB
Trusted Shops
utility
54.3 KiB
26.4 KiB
/assets/trustbadge.js
(widgets.trustedshops.com)
54.3 KiB
26.4 KiB
Properly size images Potential savings of 753 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
DrupalEnsure that you are using the native Responsive Image Styles provided from Drupal. Use the Responsive Image Styles when rendering image fields through view modes, views, or images uploaded through the WYSIWYG editor.
URL
Resource Size
Potential Savings
jysk.fr
1st party
854.0 KiB
752.6 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
271.5 KiB
242.8 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/N…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
222.6 KiB
199.0 KiB
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
157.8 KiB
130.2 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
107.3 KiB
96.0 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
94.7 KiB
84.6 KiB
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
jysk.fr
1st party
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/N…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
DrupalEnsure you have enabled "Aggregate CSS files" in the "Administration » Configuration » Development" page.
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
URL
Transfer Size
Potential Savings
/**
  Template name: Overlay v2 - Google Consent Mode v2
  URI: https://cookieinformation.com
  Ver…
6.2 KiB
3.4 KiB
Serve images in next-gen formats Potential savings of 169 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
DrupalConsider configuring WebP image formats with a Convert image style on your site.
URL
Resource Size
Potential Savings
jysk.fr
1st party
291.3 KiB
168.5 KiB
Jardin
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Jardin">
50.3 KiB
27.1 KiB
Salle à manger
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle à manger">
37.7 KiB
22.2 KiB
Salle de bain
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle de bain">
42.9 KiB
21.9 KiB
Stores & rideaux
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Stores &amp; rideaux">
36.1 KiB
20.7 KiB
Rangement
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Rangement">
30.3 KiB
18.1 KiB
Bureau
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Bureau">
29.9 KiB
18.0 KiB
Salon
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salon">
26.6 KiB
16.0 KiB
Chambre et literie
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Chambre et literie">
25.7 KiB
15.5 KiB
div.company-details-text > p > a > img
<img data-entity-type="file" data-entity-uuid="fe863cb0-613e-435b-929c-644177292162" alt="" src="/sites/jysk.fr/files/wysiwyg/Bandeau_Fournisseur_Officiel_FFTRI_-_JYSK_1_2…" height="130" width="230">
11.8 KiB
9.0 KiB
Enable text compression Potential savings of 211 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
DrupalText-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Consider using a CDN that natively supports this, or configure the web server to perform this operation. Learn more.
URL
Transfer Size
Potential Savings
cookieinformation.com
229.6 KiB
210.7 KiB
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
224.7 KiB
206.6 KiB
…jysk.fr/cabl.json
(policy.app.cookieinformation.com)
4.9 KiB
4.1 KiB
Serve static assets with an efficient cache policy 30 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
DrupalSet the "Browser and proxy cache maximum age" in the "Administration » Configuration » Development" page. Read about Drupal cache and optimizing for performance.
URL
Cache TTL
Transfer Size
jysk.fr
1st party
1,568 KiB
None
272 KiB
None
223 KiB
None
158 KiB
None
101 KiB
None
95 KiB
None
71 KiB
None
55 KiB
None
55 KiB
None
54 KiB
None
54 KiB
None
54 KiB
None
47 KiB
None
19 KiB
None
12 KiB
None
3 KiB
None
1 KiB
30d
51 KiB
30d
43 KiB
30d
38 KiB
30d
36 KiB
30d
31 KiB
30d
30 KiB
30d
27 KiB
30d
26 KiB
30d
12 KiB
cookieinformation.com
225 KiB
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
None
225 KiB
Dynamic Yield
customer-success
125 KiB
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
30s
9 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
8h
116 KiB
Trusted Shops
utility
57 KiB
/assets/trustbadge.js
(widgets.trustedshops.com)
1h
55 KiB
/js/XC5CA20EC….js
(widgets.trustedshops.com)
1h
2 KiB
Defer offscreen images Potential savings of 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
DrupalConsider configuring lazy load images in Drupal. The field formatters for images support lazy or eager.
URL
Resource Size
Potential Savings
jysk.fr
1st party
11.8 KiB
11.8 KiB
div.company-details-text > p > a > img
<img data-entity-type="file" data-entity-uuid="fe863cb0-613e-435b-929c-644177292162" alt="" src="/sites/jysk.fr/files/wysiwyg/Bandeau_Fournisseur_Officiel_FFTRI_-_JYSK_1_2…" height="130" width="230">
11.8 KiB
11.8 KiB
Efficiently encode images Potential savings of 50 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
DrupalConsider using a module that automatically optimizes and reduces the size of images uploaded through the site while retaining quality. Also, ensure you are using the native Responsive Image Styles provided from Drupal for all images rendered on the site.
URL
Resource Size
Potential Savings
jysk.fr
1st party
291.3 KiB
50.2 KiB
Jardin
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Jardin">
50.3 KiB
7.7 KiB
Salle à manger
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle à manger">
37.7 KiB
7.1 KiB
div.company-details-text > p > a > img
<img data-entity-type="file" data-entity-uuid="fe863cb0-613e-435b-929c-644177292162" alt="" src="/sites/jysk.fr/files/wysiwyg/Bandeau_Fournisseur_Officiel_FFTRI_-_JYSK_1_2…" height="130" width="230">
11.8 KiB
5.7 KiB
Stores & rideaux
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Stores &amp; rideaux">
36.1 KiB
5.7 KiB
Rangement
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Rangement">
30.3 KiB
5.5 KiB
Bureau
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Bureau">
29.9 KiB
5.1 KiB
Salon
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salon">
26.6 KiB
4.8 KiB
Salle de bain
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle de bain">
42.9 KiB
4.5 KiB
Chambre et literie
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Chambre et literie">
25.7 KiB
4.2 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 15 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
jysk.fr
1st party
14.7 KiB
7.0 KiB
@babel/plugin-transform-classes
Object.entries
6.7 KiB
@babel/plugin-transform-classes
Array.isArray
Object.keys
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Trusted Shops
utility
0.0 KiB
/assets/trustbadge.js
(widgets.trustedshops.com)
0.0 KiB
/assets/trustbadge.js:2:158383
(widgets.trustedshops.com)
@babel/plugin-transform-classes
Avoid enormous network payloads Total size was 3,595 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
DrupalConsider using Responsive Image Styles to reduce the size of images loaded on your page. If you are using Views to show multiple content items on a page, consider implementing pagination to limit the number of content items shown on a given page.
URL
Transfer Size
jysk.fr
1st party
1,677.5 KiB
815.7 KiB
271.9 KiB
222.9 KiB
158.1 KiB
107.8 KiB
101.2 KiB
Google Tag Manager
tag-manager
281.2 KiB
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
146.5 KiB
134.7 KiB
cookieinformation.com
225.4 KiB
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
225.4 KiB
Dynamic Yield
customer-success
115.7 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
115.7 KiB
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
632 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
6,999 ms
220 ms
9,319 ms
177 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
18,833 ms
156 ms
/gtag/destination?id=…
(www.googletagmanager.com)
20,789 ms
79 ms
jysk.fr
1st party
514 ms
17,552 ms
514 ms
Unattributable
115 ms
Unattributable
1,128 ms
115 ms
Trusted Shops
utility
107 ms
/assets/trustbadge.js
(widgets.trustedshops.com)
20,046 ms
57 ms
/assets/fr-FR.5d928e0….chunk.js
(widgets.trustedshops.com)
20,350 ms
50 ms
Dynamic Yield
customer-success
85 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
13,202 ms
85 ms
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Chambre et literie Lits et matelas Salle de bain Bureau Salon Salle à manger Ra…
<div class="main-region-wrapper">
0.029
Chambre et literie Lits et matelas Salle de bain Bureau Salon Salle à manger Ra…
<div class="main-region-wrapper">
0.029
Initial server response time was short Root document took 150 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
DrupalOffload traffic with one or more Drupal caching modules such as Internal Page Cache, Internal Dynamic Page Cache, and BigPipe. Couple these with a CDN to further improve response time. Your hosting servers should make use of PHP OPcache. Consider using memory-caching such as Redis or Memcached to reduce database query times. Lastly use performant themes, modules, and faster servers to lower server response time.
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
jysk.fr
1st party
150 ms
150 ms
Avoid chaining critical requests 11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 1,285.897 ms
Initial Navigation
- 510.185 ms, 53.55 KiB
…dist/js.cookie.min.js
(cdn.jsdelivr.net)
- 20.57 ms, 1.59 KiB
- 158.464 ms, 2.59 KiB
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
- 561.183 ms, 8.88 KiB
- 364.036 ms, 47.39 KiB
- 117.764 ms, 1.90 KiB
- 445.117 ms, 101.18 KiB
- 155.129 ms, 11.81 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
- 66.303 ms, 115.70 KiB
- 305.769 ms, 70.73 KiB
- 225.159 ms, 18.58 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (14)
Show Hide
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
DrupalEnsure you have enabled "Aggregate JavaScript files" in the "Administration » Configuration » Development" page.
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://rcom-eu.dynamicyield.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://cdnjs.cloudflare.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
DrupalPreconnect or dns-prefetch resource hints can be added by installing and configuring a module that provides facilities for user agent resource hints.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
DrupalRedirects introduce additional delays before the page can be loaded. If the Redirect module is installed, review if unnecessary redirects can be removed. Learn more.
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
DrupalConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
DrupalIf the LCP element is dynamically added to the page, you should optimize the image in order to improve LCP. Learn more.
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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.
Names and labels
Buttons do not have an accessible name
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.
Failing Elements
div#coi-banner-wrapper > div#coiPage-1 > div.coi-banner__summary > button#coi-expand
<button id="coi-expand" tabindex="0">
w3-search
<button data-testid="submitbutton" type="submit" class="search-input-button btn-flat btn btn-primary">
w3-close
<button type="button" class="modal-close rounded-circle d-flex align-items-center justify-content-cente…">
w3-close
<button type="button" class="off-canvas-close rounded-circle d-flex align-items-center justify-content-…">
w3-close
<button type="button" class="off-canvas-close rounded-circle d-flex align-items-center justify-content-…">
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Failing Elements
form#jysk-teradata-subscribe-form > div.newsletter__fields > div.form-group > input.form-control
<input type="text" name="name" value="" maxlength="128" class="form-control">
form#jysk-teradata-subscribe-form > div.newsletter__fields > div.form-group > input#teradata-email
<input type="email" name="email" value="" maxlength="128" id="teradata-email" class="form-control">
Image elements have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Failing Elements
Chambre et literie
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Chambre et literie">
Salle de bain
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle de bain">
Bureau
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Bureau">
Salon
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salon">
Salle à manger
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle à manger">
Rangement
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Rangement">
Stores & rideaux
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Stores &amp; rideaux">
Jardin
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Jardin">
Déco/textile
<img src="" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Déco/textile">
Nos offres
<img src="" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Nos offres">
PETIT PRIX PERMANENT
<img src="" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="PETIT PRIX PERMANENT">
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.
Tables and lists
List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements.
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
Failing Elements
Fonctionnalité
<li>
Statistiques
<li>
Marketing
<li>
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
ARIA
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Failing Elements
TOUT REFUSER
<button tabindex="0" onclick="CookieInformation.declineAllCategories()" aria-label="Tout refuser" id="declineButton" class="coi-banner__decline" role="alert" aria-atomic="true" style="display: flex;">
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.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (22)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
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.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Not applicable (29)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
jysk.fr
1st party
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at https://jysk.fr/sites/jysk.fr/files/js/js_f-h4NWpO43Gy3U2wwNKEAft1BD9oKHCiLGP5aaEYfjk.js?scope=footer&delta=4&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:9:785
    at HTMLDocument.<anonymous> (https://jysk.fr/sites/jysk.fr/files/js/js_f-h4NWpO43Gy3U2wwNKEAft1BD9oKHCiLGP5aaEYfjk.js?scope=footer&delta=4&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:9:1764)
    at e (https://jysk.fr/sites/jysk.fr/files/js/js_LMjTxPaNhg7vE1AaMArLvjOpwbN42_dZ2VToUF8RT9o.js?scope=header&delta=0&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:3:27028)
    at t (https://jysk.fr/sites/jysk.fr/files/js/js_LMjTxPaNhg7vE1AaMArLvjOpwbN42_dZ2VToUF8RT9o.js?scope=header&delta=0&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:3:27330)
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.7.1
jQuery UI
1.13.2
React
Preact
10
Underscore
1.13.6
Knockout
3.5.0
core-js
core-js-global@3.18.1; core-js-global@3.37.1; core-js-pure@2.6.12
Drupal
Missing source maps for large first-party JavaScript
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.
URL
Map URL
jysk.fr
1st party
Large JavaScript file is missing a source map
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 99.62% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
jysk.fr
1st party
.jysk-ui-shim.jysk-ui-shim .w3-form.final-form.final-form .custom-form-input-label .error
0.27%
10px
.jysk-ui-shim.jysk-ui-shim .slick-arrow
0.11%
0px
Unattributable
Legible text
99.62%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
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.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
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
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.2 s
Page LoadsGood (≤ 2.5 s)92%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)3%75th Percentile - 1.2 sCore Web Vital
Interaction to Next Paint (INP)
126 ms
Page LoadsGood (≤ 200 ms)85%Needs Improvement (200 ms - 500 ms)10%Poor (> 500 ms)5%75th Percentile - 126 msCore Web Vital
Cumulative Layout Shift (CLS)
0.01
Page LoadsGood (≤ 0.1)92%Needs Improvement (0.1 - 0.25)6%Poor (> 0.25)1%75th Percentile - 0.01Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.1 s
Page LoadsGood (≤ 1.8 s)90%Needs Improvement (1.8 s - 3 s)7%Poor (> 3 s)4%75th Percentile - 1.1 s 
Time to First Byte (TTFB)
0.3 s
Page LoadsGood (≤ 0.8 s)93%Needs Improvement (0.8 s - 1.8 s)5%Poor (> 1.8 s)2%75th Percentile - 0.3 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.1 s
Page LoadsGood (≤ 2.5 s)95%Needs Improvement (2.5 s - 4 s)3%Poor (> 4 s)2%75th Percentile - 1.1 sCore Web Vital
Interaction to Next Paint (INP)
113 ms
Page LoadsGood (≤ 200 ms)88%Needs Improvement (200 ms - 500 ms)9%Poor (> 500 ms)3%75th Percentile - 113 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)89%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)5%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.9 s
Page LoadsGood (≤ 1.8 s)94%Needs Improvement (1.8 s - 3 s)5%Poor (> 3 s)2%75th Percentile - 0.9 s 
Time to First Byte (TTFB)
0.3 s
Page LoadsGood (≤ 0.8 s)90%Needs Improvement (0.8 s - 1.8 s)9%Poor (> 1.8 s)1%75th Percentile - 0.3 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
57 FCP+9LCP+17TBT+5CLS+25SI+2 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
670 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.035
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
3.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 13, 2025, 6:00 PM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 366 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 131.0.6778.264 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 2.3 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
jysk.fr
1st party
1,664 ms
1,141 ms
98 ms
1,259 ms
1,074 ms
90 ms
335 ms
6 ms
5 ms
69 ms
61 ms
3 ms
Google Tag Manager
tag-manager
750 ms
703 ms
36 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
544 ms
516 ms
17 ms
135 ms
123 ms
11 ms
/gtag/destination?id=…
(www.googletagmanager.com)
71 ms
64 ms
7 ms
Unattributable
244 ms
4 ms
0 ms
Unattributable
244 ms
4 ms
0 ms
Dynamic Yield
customer-success
235 ms
154 ms
12 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
140 ms
94 ms
9 ms
…2.47.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
95 ms
60 ms
3 ms
Trusted Shops
utility
88 ms
79 ms
0 ms
/assets/fr-FR.5d928e0….chunk.js
(widgets.trustedshops.com)
88 ms
79 ms
0 ms
cookieinformation.com
68 ms
24 ms
2 ms
/uc.js
(policy.cookieinformation.com)
68 ms
24 ms
2 ms
Minimize main-thread work 3.4 s
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 workTBT
Category
Time Spent
Script Evaluation
2,317 ms
Style & Layout
361 ms
Other
267 ms
Script Parsing & Compilation
193 ms
Parse HTML & CSS
85 ms
Garbage Collection
82 ms
Rendering
67 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 380 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
373 KiB
376 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
147 KiB
275 ms
135 KiB
82 ms
/gtag/destination?id=…
(www.googletagmanager.com)
89 KiB
19 ms
2 KiB
0 ms
Dynamic Yield
customer-success
160 KiB
5 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
116 KiB
5 ms
…2.47.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
33 KiB
0 ms
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
9 KiB
0 ms
/st?sec=…
(st-eu.dynamicyield.com)
3 KiB
0 ms
cookieinformation.com
250 KiB
3 ms
/uc.js
(policy.cookieinformation.com)
16 KiB
3 ms
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
225 KiB
0 ms
…jysk.fr/cabl.json
(policy.app.cookieinformation.com)
6 KiB
0 ms
/cookiesharingiframe.html
(policy.app.cookieinformation.com)
4 KiB
0 ms
Trusted Shops
utility
72 KiB
0 ms
/assets/trustbadge.js
(widgets.trustedshops.com)
55 KiB
0 ms
…images/sprite.fa10bbb….svg
(widgets.trustedshops.com)
12 KiB
0 ms
/assets/fr-FR.5d928e0….chunk.js
(widgets.trustedshops.com)
4 KiB
0 ms
/js/XC5CA20EC….js
(widgets.trustedshops.com)
2 KiB
0 ms
Google/Doubleclick Ads
ad
2 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
JSDelivr CDN
cdn
2 KiB
0 ms
…dist/js.cookie.min.js
(cdn.jsdelivr.net)
2 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
Properly size images Potential savings of 759 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
DrupalEnsure that you are using the native Responsive Image Styles provided from Drupal. Use the Responsive Image Styles when rendering image fields through view modes, views, or images uploaded through the WYSIWYG editor.
URL
Resource Size
Potential Savings
jysk.fr
1st party
1,005.0 KiB
759.0 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
271.5 KiB
253.0 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/N…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
222.6 KiB
207.4 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
107.3 KiB
100.0 KiB
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
94.7 KiB
88.2 KiB
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
126.5 KiB
62.3 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/Emma_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
27.2 KiB
17.0 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/royal_oak_123882-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
21.2 KiB
13.3 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/DODO_130477-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
13.0 KiB
8.1 KiB
Nous sommes là pour vous aider
<img src="https://jysk.fr/sites/jysk.fr/files/special_events_campaigns/2023-10/photo…" class="img-responsive lazyload" width="567" height="225" loading="lazy" decoding="async" alt="Nous sommes là pour vous aider">
113.6 KiB
4.9 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/Front-page-Merinos.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
7.4 KiB
4.6 KiB
Largest Contentful Paint element 1,900 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
Phase
% of LCP
Timing
TTFB
9%
160 ms
Load Delay
37%
710 ms
Load Time
34%
660 ms
Render Delay
20%
380 ms
Eliminate render-blocking resources Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
DrupalConsider using a module to inline critical CSS and JavaScript, and use the defer attribute for non-critical CSS or JavaScript.
URL
Transfer Size
Potential Savings
Dynamic Yield
customer-success
124.6 KiB
420 ms
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
8.9 KiB
210 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
115.7 KiB
210 ms
jysk.fr
1st party
178.6 KiB
440 ms
70.7 KiB
200 ms
54.4 KiB
120 ms
53.5 KiB
120 ms
JSDelivr CDN
cdn
1.6 KiB
230 ms
…dist/js.cookie.min.js
(cdn.jsdelivr.net)
1.6 KiB
230 ms
Reduce unused CSS Potential savings of 117 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.LCPFCP
DrupalConsider removing unused CSS rules and only attach the needed Drupal libraries to the relevant page or component in a page. See the Drupal documentation for details. To identify attached libraries that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/module responsible from the URL of the stylesheet when CSS aggregation is disabled in your Drupal site. Look out for themes/modules that have many stylesheets in the list which have a lot of red in code coverage. A theme/module should only attach a stylesheet library if it is actually used on the page.
URL
Transfer Size
Potential Savings
jysk.fr
1st party
124.1 KiB
116.7 KiB
70.2 KiB
64.7 KiB
53.9 KiB
52.0 KiB
Reduce unused JavaScript Potential savings of 889 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
DrupalConsider removing unused JavaScript assets and only attach the needed Drupal libraries to the relevant page or component in a page. See the Drupal documentation for details. To identify attached libraries that are adding extraneous JavaScript, try running code coverage in Chrome DevTools. You can identify the theme/module responsible from the URL of the script when JavaScript aggregation is disabled in your Drupal site. Look out for themes/modules that have many scripts in the list which have a lot of red in code coverage. A theme/module should only attach a script library if it is actually used on the page.
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
jysk.fr
1st party
983.3 KiB
662.7 KiB
814.5 KiB
523.6 KiB
100.7 KiB
81.5 KiB
46.9 KiB
36.9 KiB
21.3 KiB
20.7 KiB
Google Tag Manager
tag-manager
367.4 KiB
134.0 KiB
133.5 KiB
52.9 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
88.4 KiB
43.8 KiB
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
145.5 KiB
37.2 KiB
Dynamic Yield
customer-success
114.8 KiB
66.1 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
114.8 KiB
66.1 KiB
Trusted Shops
utility
54.3 KiB
26.4 KiB
/assets/trustbadge.js
(widgets.trustedshops.com)
54.3 KiB
26.4 KiB
Avoid an excessive DOM size 2,481 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
2,481
Maximum DOM Depth
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/royal_oak_123882-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
21
Maximum Child Elements
div.col-12 > div.slick-slider > div.slick-list > div.slick-track
<div class="slick-track" style="width: 5320px; opacity: 1; transform: translate3d(-1140px, 0px, 0px);">
28
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
jysk.fr
1st party
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/N…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
div.d-flex > a > picture > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive" loading="eager" alt="" fetchpriority="high">
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
DrupalEnsure you have enabled "Aggregate CSS files" in the "Administration » Configuration » Development" page.
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
URL
Transfer Size
Potential Savings
/**
  Template name: Overlay v2 - Google Consent Mode v2
  URI: https://cookieinformation.com
  Ver…
5.1 KiB
2.8 KiB
Serve images in next-gen formats Potential savings of 407 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
DrupalConsider configuring WebP image formats with a Convert image style on your site.
URL
Resource Size
Potential Savings
jysk.fr
1st party
609.3 KiB
406.5 KiB
Nous sommes là pour vous aider
<img src="https://jysk.fr/sites/jysk.fr/files/special_events_campaigns/2023-10/photo…" class="img-responsive lazyload" width="567" height="225" loading="lazy" decoding="async" alt="Nous sommes là pour vous aider">
113.6 KiB
96.7 KiB
JYSK POUR LES PROS - POUR TOUTES LES ENTREPRISES
<img src="https://jysk.fr/sites/jysk.fr/files/special_events_campaigns/2024-09/B2B_I…" class="img-responsive lazyload" width="567" height="225" loading="lazy" decoding="async" alt="JYSK POUR LES PROS - POUR TOUTES LES ENTREPRISES">
65.3 KiB
37.7 KiB
Jardin
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Jardin">
50.3 KiB
27.1 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/Emma_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
27.2 KiB
24.3 KiB
Salle à manger
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle à manger">
37.7 KiB
22.2 KiB
Salle de bain
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle de bain">
42.9 KiB
21.9 KiB
Stores & rideaux
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Stores &amp; rideaux">
36.1 KiB
20.7 KiB
Déco/textile
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Déco/textile">
36.0 KiB
20.3 KiB
PETIT PRIX PERMANENT
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2024-05/E…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="PETIT PRIX PERMANENT">
26.9 KiB
19.2 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/royal_oak_123882-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
21.2 KiB
18.9 KiB
Rangement
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Rangement">
30.3 KiB
18.1 KiB
Bureau
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Bureau">
29.9 KiB
18.0 KiB
Salon
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salon">
26.6 KiB
16.0 KiB
Chambre et literie
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Chambre et literie">
25.7 KiB
15.5 KiB
Nos offres
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-01/S…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Nos offres">
14.9 KiB
10.6 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/DODO_130477-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
13.0 KiB
10.4 KiB
div.company-details-text > p > a > img
<img data-entity-type="file" data-entity-uuid="fe863cb0-613e-435b-929c-644177292162" alt="" src="/sites/jysk.fr/files/wysiwyg/Bandeau_Fournisseur_Officiel_FFTRI_-_JYSK_1_2…" height="130" width="230">
11.8 KiB
9.0 KiB
Enable text compression Potential savings of 211 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
DrupalText-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Consider using a CDN that natively supports this, or configure the web server to perform this operation. Learn more.
URL
Transfer Size
Potential Savings
cookieinformation.com
229.6 KiB
210.7 KiB
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
224.7 KiB
206.6 KiB
…jysk.fr/cabl.json
(policy.app.cookieinformation.com)
4.9 KiB
4.1 KiB
Serve static assets with an efficient cache policy 44 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
DrupalSet the "Browser and proxy cache maximum age" in the "Administration » Configuration » Development" page. Read about Drupal cache and optimizing for performance.
URL
Cache TTL
Transfer Size
jysk.fr
1st party
1,408 KiB
None
127 KiB
None
101 KiB
None
95 KiB
None
71 KiB
None
55 KiB
None
55 KiB
None
54 KiB
None
54 KiB
None
54 KiB
None
47 KiB
None
19 KiB
None
12 KiB
None
3 KiB
None
1 KiB
30d
114 KiB
30d
66 KiB
30d
51 KiB
30d
43 KiB
30d
38 KiB
30d
36 KiB
30d
36 KiB
30d
31 KiB
30d
30 KiB
30d
28 KiB
30d
27 KiB
30d
27 KiB
30d
26 KiB
30d
22 KiB
30d
15 KiB
30d
13 KiB
30d
12 KiB
30d
8 KiB
30d
6 KiB
30d
6 KiB
30d
5 KiB
30d
5 KiB
30d
5 KiB
30d
5 KiB
30d
5 KiB
cookieinformation.com
225 KiB
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
None
225 KiB
Dynamic Yield
customer-success
125 KiB
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
30s
9 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
8h
116 KiB
Trusted Shops
utility
57 KiB
/assets/trustbadge.js
(widgets.trustedshops.com)
1h
55 KiB
/js/XC5CA20EC….js
(widgets.trustedshops.com)
1h
2 KiB
Defer offscreen images Potential savings of 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
DrupalConsider configuring lazy load images in Drupal. The field formatters for images support lazy or eager.
URL
Resource Size
Potential Savings
jysk.fr
1st party
11.8 KiB
11.8 KiB
div.company-details-text > p > a > img
<img data-entity-type="file" data-entity-uuid="fe863cb0-613e-435b-929c-644177292162" alt="" src="/sites/jysk.fr/files/wysiwyg/Bandeau_Fournisseur_Officiel_FFTRI_-_JYSK_1_2…" height="130" width="230">
11.8 KiB
11.8 KiB
Efficiently encode images Potential savings of 206 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
DrupalConsider using a module that automatically optimizes and reduces the size of images uploaded through the site while retaining quality. Also, ensure you are using the native Responsive Image Styles provided from Drupal for all images rendered on the site.
URL
Resource Size
Potential Savings
jysk.fr
1st party
616.7 KiB
206.4 KiB
Nous sommes là pour vous aider
<img src="https://jysk.fr/sites/jysk.fr/files/special_events_campaigns/2023-10/photo…" class="img-responsive lazyload" width="567" height="225" loading="lazy" decoding="async" alt="Nous sommes là pour vous aider">
113.6 KiB
77.5 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/Emma_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
27.2 KiB
20.6 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/royal_oak_123882-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
21.2 KiB
16.0 KiB
JYSK POUR LES PROS - POUR TOUTES LES ENTREPRISES
<img src="https://jysk.fr/sites/jysk.fr/files/special_events_campaigns/2024-09/B2B_I…" class="img-responsive lazyload" width="567" height="225" loading="lazy" decoding="async" alt="JYSK POUR LES PROS - POUR TOUTES LES ENTREPRISES">
65.3 KiB
11.4 KiB
PETIT PRIX PERMANENT
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2024-05/E…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="PETIT PRIX PERMANENT">
26.9 KiB
9.2 KiB
Jardin
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Jardin">
50.3 KiB
7.7 KiB
Salle à manger
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle à manger">
37.7 KiB
7.1 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/DODO_130477-n_235x80px.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
13.0 KiB
7.0 KiB
div.company-details-text > p > a > img
<img data-entity-type="file" data-entity-uuid="fe863cb0-613e-435b-929c-644177292162" alt="" src="/sites/jysk.fr/files/wysiwyg/Bandeau_Fournisseur_Officiel_FFTRI_-_JYSK_1_2…" height="130" width="230">
11.8 KiB
5.7 KiB
Stores & rideaux
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Stores &amp; rideaux">
36.1 KiB
5.7 KiB
Déco/textile
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Déco/textile">
36.0 KiB
5.6 KiB
Rangement
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Rangement">
30.3 KiB
5.5 KiB
Bureau
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Bureau">
29.9 KiB
5.1 KiB
Salon
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salon">
26.6 KiB
4.8 KiB
div > div.brand-item > a.d-block > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/brand/Front-page-Merinos.jpg" class="img-responsive lazyload image-contain" width="235" height="80" loading="lazy" decoding="async" alt="">
7.4 KiB
4.6 KiB
Salle de bain
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle de bain">
42.9 KiB
4.5 KiB
Chambre et literie
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Chambre et literie">
25.7 KiB
4.2 KiB
Nos offres
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-01/S…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Nos offres">
14.9 KiB
4.2 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 15 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
jysk.fr
1st party
14.7 KiB
7.0 KiB
@babel/plugin-transform-classes
Object.entries
6.7 KiB
@babel/plugin-transform-classes
Array.isArray
Object.keys
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Trusted Shops
utility
0.0 KiB
/assets/trustbadge.js
(widgets.trustedshops.com)
0.0 KiB
/assets/trustbadge.js:2:158383
(widgets.trustedshops.com)
@babel/plugin-transform-classes
Avoid enormous network payloads Total size was 3,931 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
DrupalConsider using Responsive Image Styles to reduce the size of images loaded on your page. If you are using Views to show multiple content items on a page, consider implementing pagination to limit the number of content items shown on a given page.
URL
Transfer Size
jysk.fr
1st party
1,659.2 KiB
815.7 KiB
272.0 KiB
223.0 KiB
126.8 KiB
114.0 KiB
107.8 KiB
Google Tag Manager
tag-manager
281.1 KiB
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
146.5 KiB
134.6 KiB
cookieinformation.com
225.4 KiB
…jysk.fr/fr.js
(policy.app.cookieinformation.com)
225.4 KiB
Dynamic Yield
customer-success
115.7 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
115.7 KiB
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
1,047 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
3,282 ms
473 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
1,708 ms
198 ms
/gtm.js?id=GTM-KM45937F
(www.googletagmanager.com)
4,075 ms
175 ms
2,146 ms
132 ms
/gtag/destination?id=…
(www.googletagmanager.com)
4,420 ms
69 ms
Dynamic Yield
customer-success
77 ms
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
879 ms
77 ms
cookieinformation.com
53 ms
/uc.js
(policy.cookieinformation.com)
3,853 ms
53 ms
Initial server response time was short Root document took 320 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
DrupalOffload traffic with one or more Drupal caching modules such as Internal Page Cache, Internal Dynamic Page Cache, and BigPipe. Couple these with a CDN to further improve response time. Your hosting servers should make use of PHP OPcache. Consider using memory-caching such as Redis or Memcached to reduce database query times. Lastly use performant themes, modules, and faster servers to lower server response time.
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
jysk.fr
1st party
320 ms
320 ms
Avoid large layout shifts 6 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Chambre et literie Lits et matelas Salle de bain Bureau Salon Salle à manger Ra…
<div class="main-region-wrapper">
0.018
Web font loaded
Web font loaded
A late network request adjusted the page layout
A late network request adjusted the page layout
A late network request adjusted the page layout
A late network request adjusted the page layout
A late network request adjusted the page layout
Chambre et literie Lits et matelas Salle de bain Bureau Salon Salle à manger Ra…
<div class="main-region-wrapper">
0.018
Web font loaded
Web font loaded
A late network request adjusted the page layout
A late network request adjusted the page layout
A late network request adjusted the page layout
A late network request adjusted the page layout
Inspiration Publicités Trouver mon magasin Service client PROS Carrière
<ul class="list-unstyled mb-0">
0.000
Jusqu'à -50% sur tous les meubles d'intérieur*
<span class="top-info-bar__text">
0.000
div.jysk-ui-shim > a#wishlist-link > span.header__action-icon > svg.svg-w3-wishlist
<svg class="svg-w3-wishlist v-3" role="img" aria-hidden="true" width="24" height="24" aria-label="">
0.000
div.col-md-5 > div.favorite-store-selector > button.btn-link > svg.svg-arrow-down
<svg class="svg-arrow-down v-3" role="img" aria-hidden="true" width="8" height="8" aria-label="">
0.000
Avoid chaining critical requests 11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 2,308.593 ms
Initial Navigation
- 220.007 ms, 53.55 KiB
…dist/js.cookie.min.js
(cdn.jsdelivr.net)
- 16.32 ms, 1.59 KiB
- 369.816 ms, 2.59 KiB
…9881222/api_dynamic.js
(cdn-eu.dynamicyield.com)
- 56.715 ms, 8.88 KiB
- 1,070.177 ms, 47.39 KiB
- 332.013 ms, 1.90 KiB
- 1,341.372 ms, 101.18 KiB
- 1,270.001 ms, 11.81 KiB
…9881222/api_static.js
(cdn-eu.dynamicyield.com)
- 23.836 ms, 115.70 KiB
- 257.055 ms, 70.73 KiB
- 235.519 ms, 18.58 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (14)
Show Hide
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
DrupalEnsure you have enabled "Aggregate JavaScript files" in the "Administration » Configuration » Development" page.
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://rcom-eu.dynamicyield.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://cdnjs.cloudflare.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
DrupalPreconnect or dns-prefetch resource hints can be added by installing and configuring a module that provides facilities for user agent resource hints.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
DrupalRedirects introduce additional delays before the page can be loaded. If the Redirect module is installed, review if unnecessary redirects can be removed. Learn more.
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
DrupalConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
DrupalIf the LCP element is dynamically added to the page, you should optimize the image in order to improve LCP. Learn more.
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
div.hero-banner--big-Image > a > picture.skip-autoscale > img.img-responsive
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-02/T…" class="img-responsive skip-autoscale" width="100%" height="" loading="eager" alt="" fetchpriority="high">
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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.
Names and labels
Buttons do not have an accessible name
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.
Failing Elements
w3-search
<button data-testid="submitbutton" type="submit" class="search-input-button btn-flat btn btn-primary">
w3-close
<button type="button" class="modal-close rounded-circle d-flex align-items-center justify-content-cente…">
w3-close
<button type="button" class="off-canvas-close rounded-circle d-flex align-items-center justify-content-…">
w3-close
<button type="button" class="off-canvas-close rounded-circle d-flex align-items-center justify-content-…">
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Failing Elements
form#jysk-teradata-subscribe-form > div.newsletter__fields > div.form-group > input.form-control
<input type="text" name="name" value="" maxlength="128" class="form-control">
form#jysk-teradata-subscribe-form > div.newsletter__fields > div.form-group > input#teradata-email
<input type="email" name="email" value="" maxlength="128" id="teradata-email" class="form-control">
Image elements have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Failing Elements
Chambre et literie
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Chambre et literie">
Salle de bain
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle de bain">
Bureau
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Bureau">
Salon
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salon">
Salle à manger
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Salle à manger">
Rangement
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Rangement">
Stores & rideaux
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Stores &amp; rideaux">
Jardin
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Jardin">
Déco/textile
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/catalog/l…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Déco/textile">
Nos offres
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2025-01/S…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="Nos offres">
PETIT PRIX PERMANENT
<img src="https://jysk.fr/sites/jysk.fr/files/styles/full_optimized/public/2024-05/E…" class="img-responsive lazyload" width="370" height="307" loading="lazy" decoding="async" alt="PETIT PRIX PERMANENT">
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.
Tables and lists
List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements.
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
Failing Elements
Fonctionnalité
<li>
Statistiques
<li>
Marketing
<li>
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Best practices
Touch targets do not have sufficient size or spacing.
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.
Failing Elements
Paramètres cookies
<a href="javascript:TogglePage(this, 'coiPage-3');" class="coi-banner__policy">
Politique de confidentialité de Google
<a class="coi-banner__google-privacy-policy" aria-label="" href="https://business.safety.google/privacy/" target="_blank" rel="noopener noreferrer">
Politique de confidentialité de Google
<a class="coi-banner__google-privacy-policy" aria-label="" href="https://business.safety.google/privacy/" target="_blank" rel="noopener noreferrer">
Paramètres cookies
<a href="javascript:TogglePage(this, 'coiPage-3');" class="coi-banner__policy">
These items highlight common accessibility best practices.
ARIA
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Failing Elements
TOUT REFUSER
<button tabindex="0" onclick="CookieInformation.declineAllCategories()" aria-label="Tout refuser" id="declineButton" class="coi-banner__decline" role="alert" aria-atomic="true" style="display: flex;">
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.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (21)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Not applicable (29)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
jysk.fr
1st party
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at https://jysk.fr/sites/jysk.fr/files/js/js_f-h4NWpO43Gy3U2wwNKEAft1BD9oKHCiLGP5aaEYfjk.js?scope=footer&delta=4&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:9:785
    at HTMLDocument.<anonymous> (https://jysk.fr/sites/jysk.fr/files/js/js_f-h4NWpO43Gy3U2wwNKEAft1BD9oKHCiLGP5aaEYfjk.js?scope=footer&delta=4&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:9:1764)
    at e (https://jysk.fr/sites/jysk.fr/files/js/js_LMjTxPaNhg7vE1AaMArLvjOpwbN42_dZ2VToUF8RT9o.js?scope=header&delta=0&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:3:27028)
    at t (https://jysk.fr/sites/jysk.fr/files/js/js_LMjTxPaNhg7vE1AaMArLvjOpwbN42_dZ2VToUF8RT9o.js?scope=header&delta=0&language=fr&theme=jysk_bootstrap&include=eJyFkt1yhCAMhV9IZabP0Yve9ZIJEF12kdAktrVPXyyu3f5NL9ST7xzEEB2RijIU467KFkYbc9TuQKZQoWfkG6JESWPp_AVDVGIL3hOHSNkcahiZsmIO3XmVizk_LcjrUBZODcwQc1N5yefFX6RVBSYcxphQBkgtaz93hkXJ01wSKvbiORaV7xmHGUFPf9pX9VcAXxU5Q_rq-xOoOdRwItHdiOGD91XshOgS0TrIGXn3PlDfUEsFUEiwXhNH2Yc1wxx9n6Jj4PWftCjo9_BENCW0tZssCRTNdMgWyKRxjL6urCObKcB-0IUpLF7Nrd-PDNOMeW-XEWoASpGb2orw50QrqzOqS0Lb4BfWJXhbzXbrCtT313M_iZ04htqP3_6Cn3AYiWfQOpzuBd1WmP05hAiJpu5FxLo7Z-rVhyielvrVGyywbh2YR5GHJh9ap_fgMMk7I280CQ:3:27330)
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.7.1
jQuery UI
1.13.2
React
Preact
10
Underscore
1.13.6
Knockout
3.5.0
core-js
core-js-global@3.18.1; core-js-global@3.37.1; core-js-pure@2.6.12
Drupal
Missing source maps for large first-party JavaScript
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.
URL
Map URL
jysk.fr
1st party
Large JavaScript file is missing a source map
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
SyntaxError: Unexpected token '<', "<HTML><HEA"... is not valid JSON
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (12)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
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.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
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
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.