4.2 sec in total
930 ms
3 sec
297 ms
Visit dannydanon.com now to see the best up-to-date Dannydanon content and also check out these interesting facts you probably never knew about dannydanon.com
Visit dannydanon.comWe analyzed Dannydanon.com page load time and found that the first response time was 930 ms and then it took 3.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.
dannydanon.com performance score
930 ms
93 ms
183 ms
178 ms
186 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Dannydanon.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (930 ms) belongs to the original domain Dannydanon.com.
Page size can be reduced by 824.6 kB (43%)
1.9 MB
1.1 MB
In fact, the total size of Dannydanon.com main page is 1.9 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 29.0 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 4.1 kB, which is 11% 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 29.0 kB or 80% of the original size.
Potential reduce by 157.1 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. Obviously, Dannydanon needs image optimization as it can save up to 157.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 355.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 355.7 kB or 69% of the original size.
Potential reduce by 282.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. Dannydanon.com needs all CSS files to be minified and compressed as it can save up to 282.9 kB or 83% of the original size.
Number of requests can be reduced by 33 (56%)
59
26
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dannydanon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
930 ms
calendar.css
93 ms
front.css
183 ms
menu-234e75c119c025db5942611f41ee3da4.css
178 ms
grid-responsive.css
186 ms
grid-responsive.css
185 ms
bootstrap.css
269 ms
master-4734ed5125654d7920554a1cb701bbb6.css
279 ms
orstar.css
268 ms
mediaqueries.css
284 ms
stylesheet.css
287 ms
gantry-custom.css
285 ms
settings.css
364 ms
captions.css
366 ms
template.css
362 ms
mosaic.css
372 ms
mootools-core.js
463 ms
core.js
369 ms
caption.js
490 ms
script.js
489 ms
mootools-more.js
627 ms
browser-engines.js
490 ms
rokmediaqueries.js
490 ms
rokmediaqueries.js
559 ms
sidemenu.js
559 ms
script.js
552 ms
jquery.min.js
9 ms
jquery.themepunch.plugins.min.js
555 ms
jquery.themepunch.revolution.min.js
672 ms
mootools-mobile.js
675 ms
rokmediaqueries.js
675 ms
roksprocket.js
676 ms
moofx.js
675 ms
roksprocket.request.js
713 ms
mosaic.js
730 ms
ga.js
21 ms
bg.png
122 ms
searchButton.gif
124 ms
halikud-logo-new-header-en.png
123 ms
he.png
121 ms
enlang-active.png
123 ms
engslids.png
266 ms
kotelfix2en.jpg
616 ms
27-5-15-danon-website-eng.png
277 ms
enBanner2.jpg
442 ms
10986632_966050170083726_7456016401444193260_n.jpg
359 ms
11539678_924880237535215_7444916345261931113_n.jpg
453 ms
Document-page-001.jpg
613 ms
danidanon_action_en_26.png
368 ms
danidanon_action_en_30.png
453 ms
iphone-light.png
458 ms
android-light.png
532 ms
noise.png
524 ms
logoen.png
528 ms
divider.jpg
537 ms
__utm.gif
46 ms
divider-transparent.png
558 ms
socailicons.png
517 ms
loader.gif
517 ms
timer.png
524 ms
Alef-Regular.woff
582 ms
Alef-Bold.woff
593 ms
dannydanon.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dannydanon.com 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), while the claimed language is English. Our system also found out that Dannydanon.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.
dannydanon.com
Open Graph description is not detected on the main page of Dannydanon. 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: