4.9 sec in total
274 ms
4.5 sec
179 ms
Visit lery.com now to see the best up-to-date LERY content and also check out these interesting facts you probably never knew about lery.com
Visit lery.comWe analyzed Lery.com page load time and found that the first response time was 274 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lery.com performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value17.4 s
0/100
25%
Value12.8 s
2/100
10%
Value720 ms
41/100
30%
Value0.191
64/100
15%
Value16.4 s
5/100
10%
274 ms
1104 ms
128 ms
214 ms
258 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 70% of them (76 requests) were addressed to the original Lery.com, 9% (10 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lery.com.
Page size can be reduced by 220.9 kB (19%)
1.2 MB
933.4 kB
In fact, the total size of Lery.com main page is 1.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 393.3 kB which makes up the majority of the site volume.
Potential reduce by 155.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 155.9 kB or 82% of the original size.
Potential reduce by 21.4 kB
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. LERY images are well optimized though.
Potential reduce by 24.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 19.1 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. Lery.com has all CSS files already compressed.
Number of requests can be reduced by 65 (76%)
85
20
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LERY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
lery.com
274 ms
1104 ms
wp-emoji-release.min.js
128 ms
style.min.css
214 ms
styles.css
258 ms
supersized.css
315 ms
supersized.shutter.css
339 ms
popup-contact-form.css
92 ms
style.css
344 ms
font-awesome.css
346 ms
owl.carousel.css
361 ms
owl.theme.css
370 ms
swatches-and-photos.css
399 ms
settings.css
423 ms
css
34 ms
css
37 ms
css
42 ms
js_composer_front_custom.css
609 ms
font-awesome.min.css
430 ms
bootstrap.min.css
541 ms
style.css
655 ms
css
42 ms
css
42 ms
custom.css
479 ms
Defaults.css
505 ms
anything-popup.js
180 ms
jquery.min.js
602 ms
jquery-migrate.min.js
563 ms
jquery.easing.min.js
588 ms
supersized.3.2.7.min.js
630 ms
supersized.shutter.min.js
647 ms
popup-contact-form.js
172 ms
popup-contact-popup.js
175 ms
owl.carousel.js
685 ms
lightbox.js
687 ms
jquery.themepunch.plugins.min.js
694 ms
jquery.themepunch.essential.min.js
810 ms
modernizr.js
730 ms
head.js
745 ms
css
13 ms
rs6.css
726 ms
regenerator-runtime.min.js
740 ms
wp-polyfill.min.js
748 ms
index.js
778 ms
popup-contact-form.css
757 ms
qppr_frontend_script.min.js
734 ms
popup-contact-form.js
691 ms
popup-contact-popup.js
695 ms
anything-popup.js
725 ms
rbtools.min.js
848 ms
rs6.min.js
851 ms
swatches-and-photos.js
689 ms
jquery.blockUI.min.js
669 ms
woocommerce.min.js
663 ms
jquery.cookie.min.js
716 ms
cart-fragments.min.js
746 ms
gtm4wp-contact-form-7-tracker.js
737 ms
gtm4wp-form-move-tracker.js
706 ms
plugins.js
926 ms
hoverIntent.min.js
729 ms
underscore.min.js
760 ms
wp-util.min.js
733 ms
add-to-cart-variation.min.js
692 ms
etheme.js
676 ms
js_composer_front.min.js
799 ms
gtm.js
145 ms
lery-paris-joaillerie-logo-final-.png
163 ms
ecrin.png
351 ms
dummy.png
394 ms
PinExt.png
105 ms
Histoire-de-la-Maison-LerY-Paris.jpg
629 ms
bague-entourage-marguerite-diamants-or-blanc-saphir-ovale-2-800x450.jpg
453 ms
solo-sienna-bleu-blanc-rouge-2-800x450.jpg
634 ms
Savoir-Faire-Lery-Paris-e1418118880242-740x930.jpg
839 ms
Logo-Maison-Lery-Paris-Dor%C3%A9.png
106 ms
place
593 ms
like.php
192 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
186 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
257 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf
385 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
383 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf
386 ms
fontawesome-webfont.woff
567 ms
fontawesome-webfont.woff
643 ms
KFOlCnqEu92Fr1MmEU9fCRc9AMP6lQ.ttf
385 ms
KFOmCnqEu92Fr1Mu72xPKTU1Kg.ttf
565 ms
KFOlCnqEu92Fr1MmSU5fCRc9AMP6lQ.ttf
385 ms
KFOlCnqEu92Fr1MmWUlfCRc9AMP6lQ.ttf
691 ms
widgets.js
544 ms
Logo-Maison-Lery-Paris-Dor%C3%A9.png
527 ms
bod-i.ttf
604 ms
bod-r.ttf
600 ms
lery-paris-joaillerie-logo-final-.png
554 ms
medium-cross.png
551 ms
analytics.js
240 ms
Ja7UzhsCO0c.js
391 ms
FEppCFCt76d.png
388 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
168 ms
pinit.js
49 ms
collect
85 ms
Lery_Paris_ico.ico
131 ms
js
120 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
82 ms
collect
145 ms
pinit_main.js
71 ms
Lery_Paris_ico.ico
102 ms
count.json
46 ms
ga-audiences
15 ms
lery.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lery.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
lery.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lery.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lery.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.
lery.com
Open Graph description is not detected on the main page of LERY. 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: