3.8 sec in total
744 ms
2.7 sec
332 ms
Welcome to danol.com homepage info - get ready to check Danol best content right away, or after learning these important things about danol.com
Tienda para comprar lámparas antiguas de mesa de aceite de parafina y quinqués. Para decorar restaurantes y decoraciones rústicas. De cristal y metal.
Visit danol.comWe analyzed Danol.com page load time and found that the first response time was 744 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
danol.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value9.3 s
1/100
25%
Value12.4 s
3/100
10%
Value540 ms
54/100
30%
Value1.418
0/100
15%
Value16.3 s
5/100
10%
744 ms
100 ms
298 ms
23 ms
196 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 91% of them (52 requests) were addressed to the original Danol.com, 7% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Danol.com.
Page size can be reduced by 494.7 kB (24%)
2.1 MB
1.6 MB
In fact, the total size of Danol.com main page is 2.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. 35% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 15.5 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 15.5 kB or 76% of the original size.
Potential reduce by 111.6 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. Danol images are well optimized though.
Potential reduce by 209.7 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 209.7 kB or 74% of the original size.
Potential reduce by 157.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. Danol.com needs all CSS files to be minified and compressed as it can save up to 157.9 kB or 85% of the original size.
Number of requests can be reduced by 25 (48%)
52
27
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danol. 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 12 to 1 for CSS and as a result speed up the page load time.
danol.com
744 ms
wp-emoji-release.min.js
100 ms
style.css
298 ms
css
23 ms
prettyPhoto.css
196 ms
superfish.css
198 ms
uniform.default.css
202 ms
supersized.css
201 ms
supersized.shutter.css
203 ms
jplayer.dark.css
292 ms
style_dark.css
293 ms
responsive.css
302 ms
dynamic_css.php
528 ms
custom.css
304 ms
jquery.js
494 ms
jquery-migrate.min.js
388 ms
supersized.3.2.7.js
392 ms
supersized.shutter.js
395 ms
jquery.easing.min.js
405 ms
jquery.backstretch.min.js
485 ms
superfish.js
490 ms
jquery.tipsy.js
492 ms
jquery.prettyPhoto.js
507 ms
jquery.tweet.js
583 ms
jquery.uniform.min.js
586 ms
page-elements.js
591 ms
common.js
593 ms
jquery.jplayer.min.js
609 ms
13.png
299 ms
logo.png
133 ms
menu_toggle-black.png
136 ms
button-tray-up.png
139 ms
pause.png
140 ms
arrow_left.png
156 ms
arrow_right.png
221 ms
thumb-back.png
248 ms
thumb-forward.png
255 ms
stripes_fine_white.png
229 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
13 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
23 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
20 ms
4cKlrioa77J2iqTqBgkRWg.ttf
23 ms
nav-dot.png
169 ms
Danol-47-63x63.jpg
229 ms
Danol-41-63x63.jpg
243 ms
Danol-50-63x63.jpg
264 ms
Danol-46-63x63.jpg
264 ms
Danol-48-63x63.jpg
270 ms
m-4200-m-4500az-63x63.jpg
300 ms
Danol-11-63x63.jpg
326 ms
m-300-t-63x63.jpg
338 ms
m-300-t.jpg
1043 ms
Danol-41.jpg
1067 ms
Danol-47.jpg
1305 ms
big_dots.png
498 ms
fullscreen_loader.png
424 ms
arrow_right.png
464 ms
danol.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
danol.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
danol.com 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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Danol.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Danol.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.
danol.com
Open Graph description is not detected on the main page of Danol. 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: