Tools & Wizards About Us
duralex.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

duralex.com

Duralex® Boutique

Page Load Speed

4.2 sec in total

First Response

538 ms

Resources Loaded

3.5 sec

Page Rendered

191 ms

duralex.com screenshot

About Website

Click here to check amazing Duralex content for Iran. Otherwise, check out these important facts you probably never knew about duralex.com

Découvrez tous nos produits Duralex® sur notre e-Boutique officielle ➤ Ultra résistance ✓ Livraison rapide ✓ Produit durable ✓ Made in France ✓

Visit duralex.com

Key Findings

We analyzed Duralex.com page load time and found that the first response time was 538 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

duralex.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value35.5 s

0/100

10%

TBT (Total Blocking Time)

Value42,240 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.446

20/100

15%

TTI (Time to Interactive)

Value56.9 s

0/100

10%

Network Requests Diagram

duralex.com

538 ms

css

26 ms

css

38 ms

css

47 ms

style.css

256 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 81% of them (46 requests) were addressed to the original Duralex.com, 7% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Duralex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.6 kB (15%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Duralex.com main page is 2.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.2 kB

  • Original 15.0 kB
  • After minification 13.2 kB
  • After compression 3.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 1.8 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.2 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 48.1 kB

  • Original 1.7 MB
  • After minification 1.6 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Duralex images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 147.4 kB

  • Original 208.3 kB
  • After minification 177.8 kB
  • After compression 61.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 147.4 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 89.0 kB

  • Original 109.7 kB
  • After minification 94.0 kB
  • After compression 20.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Duralex.com needs all CSS files to be minified and compressed as it can save up to 89.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (24%)

Requests Now

50

After Optimization

38

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duralex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

duralex.com

duralex.com

538 ms

css

css

26 ms

css

css

38 ms

css

css

47 ms

style.css

style.css

256 ms

isotope.css

isotope.css

178 ms

desktop.css

desktop.css

254 ms

font-awesome.min.css

font-awesome.min.css

7 ms

jquery.js

jquery.js

360 ms

colorbox.js

colorbox.js

306 ms

flexslider.js

flexslider.js

292 ms

global.js

global.js

397 ms

heightcol.js

heightcol.js

353 ms

ga.js

ga.js

48 ms

col_gauche_fixe_shw.png

col_gauche_fixe_shw.png

287 ms

desktop_sprite.jpg

desktop_sprite.jpg

424 ms

mainav.gif

mainav.gif

271 ms

search_input.gif

search_input.gif

438 ms

global_sprite.jpg

global_sprite.jpg

727 ms

slide-nouveautes-3_1902.jpg

slide-nouveautes-3_1902.jpg

1086 ms

generique_fr_1800.jpg

generique_fr_1800.jpg

970 ms

quotidien_fr_1575_1645.jpg

quotidien_fr_1575_1645.jpg

856 ms

resistant_fr_1577_1646.jpg

resistant_fr_1577_1646.jpg

993 ms

styles_fr_1576_1647.jpg

styles_fr_1576_1647.jpg

1117 ms

made_fr_1578_1648.jpg

made_fr_1578_1648.jpg

1547 ms

200_______pos_01_e_mail_signaturebrversion_c_enhtml_1814.jpg

200_______pos_01_e_mail_signaturebrversion_c_enhtml_1814.jpg

1160 ms

outerlink2.png

outerlink2.png

1252 ms

01.png

01.png

1291 ms

02.png

02.png

1379 ms

03.png

03.png

1403 ms

04.png

04.png

1447 ms

05.png

05.png

1555 ms

06.png

06.png

1574 ms

07.png

07.png

1670 ms

08.png

08.png

1690 ms

moma_1655.jpg

moma_1655.jpg

1806 ms

plus.gif

plus.gif

1833 ms

map_1332.jpg

map_1332.jpg

1854 ms

outerlink.png

outerlink.png

1868 ms

join_1333.jpg

join_1333.jpg

2167 ms

list_social.png

list_social.png

2016 ms

lang.png

lang.png

2096 ms

panier.png

panier.png

2094 ms

opacity_panier.png

opacity_panier.png

2151 ms

moncompte.png

moncompte.png

2134 ms

wZLYhRRxZWGToTRP78bqJQ.woff

wZLYhRRxZWGToTRP78bqJQ.woff

21 ms

UnXpojilM3XslYxUnWuVe_esZW2xOQ-xsNqO47m55DA.woff

UnXpojilM3XslYxUnWuVe_esZW2xOQ-xsNqO47m55DA.woff

22 ms

anMUvcNT0H1YN4FII8wprx7IBmrqA5IG9z8WNe77b9o.woff

anMUvcNT0H1YN4FII8wprx7IBmrqA5IG9z8WNe77b9o.woff

21 ms

7XUFZ5tgS-tD6QamInJTcdGU7DQ8I6RFMlK0vgclk7w.woff

7XUFZ5tgS-tD6QamInJTcdGU7DQ8I6RFMlK0vgclk7w.woff

22 ms

__utm.gif

__utm.gif

16 ms

__utm.gif

__utm.gif

44 ms

controls.png

controls.png

2076 ms

border.png

border.png

2118 ms

loading_background.png

loading_background.png

2035 ms

loading.gif

loading.gif

2101 ms

bg_control_nav.png

bg_control_nav.png

2218 ms

smartphone.css

smartphone.css

257 ms

Accessibility Review

duralex.com accessibility score

74

Accessibility Issues

ARIA

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.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

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.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

duralex.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

duralex.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duralex.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Duralex.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

duralex.com

Open Graph description is not detected on the main page of Duralex. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: