2.1 sec in total
154 ms
1.8 sec
146 ms
Visit danette.com.mx now to see the best up-to-date Danette content and also check out these interesting facts you probably never knew about danette.com.mx
Sitio Web de Danette®
Visit danette.com.mxWe analyzed Danette.com.mx page load time and found that the first response time was 154 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.
danette.com.mx performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value15.4 s
0/100
25%
Value3.3 s
90/100
10%
Value1,050 ms
25/100
30%
Value0.001
100/100
15%
Value12.7 s
14/100
10%
154 ms
584 ms
368 ms
514 ms
371 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 90% of them (36 requests) were addressed to the original Danette.com.mx, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Bs.serving-sys.com. The less responsive or slowest element that took the longest time to load (584 ms) belongs to the original domain Danette.com.mx.
Page size can be reduced by 272.8 kB (25%)
1.1 MB
813.5 kB
In fact, the total size of Danette.com.mx main page is 1.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. 40% of websites need less resources to load. Images take 730.0 kB which makes up the majority of the site volume.
Potential reduce by 58.4 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 9.9 kB, which is 13% 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 58.4 kB or 74% of the original size.
Potential reduce by 26.2 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. Danette images are well optimized though.
Potential reduce by 155.3 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 155.3 kB or 65% of the original size.
Potential reduce by 33.0 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. Danette.com.mx needs all CSS files to be minified and compressed as it can save up to 33.0 kB or 89% of the original size.
Number of requests can be reduced by 6 (18%)
34
28
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danette. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
danette.com.mx
154 ms
www.danette.com.mx
584 ms
estilos.css
368 ms
jquery-1.7.2.min.js
514 ms
functions.js
371 ms
TweenMax.min.js
441 ms
timer.js
146 ms
functions_game.js
369 ms
ga.js
14 ms
bg_bco.jpg
85 ms
load.gif
86 ms
logo_danette.png
192 ms
flecha.png
90 ms
linea_divisor.png
90 ms
btn_banner.png
79 ms
actualizar_btn.png
192 ms
tabla_nutrimental.png
261 ms
ActivityServer.bs
128 ms
__utm.gif
25 ms
ebAttribution.js
27 ms
reg.php
157 ms
bg_azul.jpg
77 ms
sprite_redes.png
81 ms
bg_buscador.png
78 ms
lupa.png
80 ms
bg-lb.png
84 ms
nexa_light-webfont.woff
145 ms
nexa_bold-webfont.woff
148 ms
nexa_light-webfont.ttf
95 ms
nexa_bold-webfont.ttf
157 ms
sprite_flechas.png
83 ms
bann_1.jpg
226 ms
bann_2.jpg
224 ms
bann_3.jpg
233 ms
sprite_dots.png
85 ms
bg_separador.png
91 ms
bnr_1.jpg
174 ms
bg_pleca.png
165 ms
bnr_2.jpg
314 ms
bnr_3.jpg
241 ms
danette.com.mx accessibility score
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
danette.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
danette.com.mx 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 doesn't use legible font sizes
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Danette.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 Danette.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.
danette.com.mx
Open Graph data is detected on the main page of Danette. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: