2.3 sec in total
330 ms
1.8 sec
116 ms
Click here to check amazing Lasser content for Spain. Otherwise, check out these important facts you probably never knew about lasser.es
Mamparas de ducha y baño de cristal templado de seguridad fabricadas a mediada en acero inoxidable y aluminio por Lasser, de diseño y calidad.
Visit lasser.esWe analyzed Lasser.es page load time and found that the first response time was 330 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
lasser.es performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value10.5 s
0/100
25%
Value10.0 s
9/100
10%
Value670 ms
45/100
30%
Value0.045
99/100
15%
Value14.0 s
10/100
10%
330 ms
321 ms
211 ms
314 ms
336 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 94% of them (31 requests) were addressed to the original Lasser.es, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (833 ms) belongs to the original domain Lasser.es.
Page size can be reduced by 300.9 kB (30%)
993.6 kB
692.7 kB
In fact, the total size of Lasser.es main page is 993.6 kB. 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 656.5 kB which makes up the majority of the site volume.
Potential reduce by 20.6 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 20.6 kB or 81% of the original size.
Potential reduce by 35.0 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. Lasser images are well optimized though.
Potential reduce by 224.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 224.5 kB or 78% of the original size.
Potential reduce by 20.9 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. Lasser.es needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 86% of the original size.
Number of requests can be reduced by 12 (38%)
32
20
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lasser. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lasser.es
330 ms
prototype.js
321 ms
scriptaculous.js
211 ms
lightbox.js
314 ms
global.js
336 ms
mampara.js
214 ms
alignUtilities.js
218 ms
cookiebanner.js
314 ms
lightbox.css
336 ms
general.css
336 ms
menu.css
418 ms
mampara.css
418 ms
effects.js
108 ms
builder.js
108 ms
logocolores.png
107 ms
topo_nuevo_es.png
108 ms
topo_pdf_livian.png
109 ms
topo_config_es.png
110 ms
socialnetwork.png
211 ms
ga.js
4 ms
__utm.gif
11 ms
loading.gif
106 ms
closelabel.gif
109 ms
topo_intro_es.png
110 ms
imatge_cataleg_01.jpg
583 ms
imatge_cataleg_02.jpg
419 ms
imatge_cataleg_03.jpg
559 ms
imatge_cataleg_04.jpg
521 ms
imatge_cataleg_05.jpg
570 ms
imatge_cataleg_06.jpg
537 ms
imatge_cataleg_07.jpg
632 ms
imatge_cataleg_08.jpg
833 ms
menu.php
645 ms
lasser.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
lasser.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lasser.es SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lasser.es can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lasser.es 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.
lasser.es
Open Graph description is not detected on the main page of Lasser. 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: