3.2 sec in total
846 ms
1.9 sec
409 ms
Welcome to lavin.com.mx homepage info - get ready to check Lavin best content right away, or after learning these important things about lavin.com.mx
Nuvel, Notré, Mineral Care, Vita-derm, Man Hood, Beautyberry, Etam
Visit lavin.com.mxWe analyzed Lavin.com.mx page load time and found that the first response time was 846 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
lavin.com.mx performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value15.6 s
0/100
25%
Value13.4 s
2/100
10%
Value100 ms
98/100
30%
Value0.075
95/100
15%
Value13.8 s
10/100
10%
846 ms
157 ms
156 ms
164 ms
162 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 83% of them (44 requests) were addressed to the original Lavin.com.mx, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Cdn-images.mailchimp.com. The less responsive or slowest element that took the longest time to load (873 ms) belongs to the original domain Lavin.com.mx.
Page size can be reduced by 1.2 MB (17%)
7.1 MB
5.9 MB
In fact, the total size of Lavin.com.mx main page is 7.1 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. 55% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 53.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 26.5 kB, which is 44% 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 53.8 kB or 89% of the original size.
Potential reduce by 1.1 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. Obviously, Lavin needs image optimization as it can save up to 1.1 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 56.8 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 56.8 kB or 25% of the original size.
Potential reduce by 19.2 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. Lavin.com.mx needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 28% of the original size.
Number of requests can be reduced by 26 (54%)
48
22
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lavin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
lavin.com.mx
846 ms
bootstrap.min.css
157 ms
owl.carousel.min.css
156 ms
font-awesome.min.css
164 ms
flaticon.css
162 ms
jquery-ui.css
165 ms
metisMenu.min.css
163 ms
swiper.min.css
235 ms
styles.css
237 ms
styleindex.css
234 ms
responsive.css
235 ms
css
29 ms
horizontal-slim-10_7.css
11 ms
jquery-2.2.4.min.js
309 ms
bootstrap.min.js
242 ms
owl.carousel.min.js
388 ms
mouse_scroll.js
332 ms
scrollup.js
331 ms
isotope.pkgd.min.js
333 ms
imagesloaded.pkgd.min.js
332 ms
jquery.zoom.min.js
384 ms
swiper.min.js
465 ms
metisMenu.min.js
396 ms
mailchimp.js
397 ms
jquery-ui.min.js
483 ms
scripts.js
464 ms
esp.png
463 ms
eng.png
471 ms
logo.png
476 ms
t.png
541 ms
772-Bannerwebcapilares1111pxlavin.jpg
765 ms
395-PostsuncarewebCV550-515(2).jpg
691 ms
214-ImagenProductoDestacadoKitAmazon.jpg
873 ms
productodes1.jpg
779 ms
307-Banner2LAVIN-logo800x600.jpg
778 ms
439-ImagenNoticiaNuvelSunCare.jpg
691 ms
672-ImagenNoticaManhood.jpg
770 ms
Newsletter.png
769 ms
horizontal-slim-10_7.css
17 ms
css
34 ms
406-BannerWebRepelente1920copia.jpg
711 ms
119-BannerWebRepelente1920.jpg
786 ms
508-bannerpaginawebamazonporoductos.jpg
720 ms
700-41-inicio.jpg
577 ms
66-Banner2LAVIN-logonuevo.jpg
658 ms
151-GRAND.jpg
730 ms
373-banner34a%C3%B1osLAVIN.jpg
745 ms
font
22 ms
fontawesome-webfont.woff
706 ms
font
84 ms
sdk.js
12 ms
sdk.js
7 ms
51 ms
lavin.com.mx 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
lavin.com.mx 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
lavin.com.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
ES
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lavin.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lavin.com.mx 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.
lavin.com.mx
Open Graph data is detected on the main page of Lavin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: