7.7 sec in total
660 ms
6.1 sec
891 ms
Click here to check amazing Danihoy content for United States. Otherwise, check out these important facts you probably never knew about danihoy.com
Home page of danihoy.com, an americana artist from Key West, FL. Singer/songwriter and performer and entertainer
Visit danihoy.comWe analyzed Danihoy.com page load time and found that the first response time was 660 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
danihoy.com performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value11.9 s
0/100
25%
Value7.4 s
28/100
10%
Value2,040 ms
7/100
30%
Value0.002
100/100
15%
Value12.3 s
15/100
10%
660 ms
667 ms
172 ms
300 ms
299 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 51% of them (57 requests) were addressed to the original Danihoy.com, 26% (29 requests) were made to Fonts.googleapis.com and 4% (4 requests) were made to Static.kickstarter.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Danihoy.com.
Page size can be reduced by 1.2 MB (31%)
3.9 MB
2.7 MB
In fact, the total size of Danihoy.com main page is 3.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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 27.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 27.5 kB or 74% of the original size.
Potential reduce by 269.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. Danihoy images are well optimized though.
Potential reduce by 610.4 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 610.4 kB or 67% of the original size.
Potential reduce by 290.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. Danihoy.com needs all CSS files to be minified and compressed as it can save up to 290.9 kB or 84% of the original size.
Number of requests can be reduced by 66 (62%)
107
41
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danihoy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
danihoy.com
660 ms
foundation.min.css
667 ms
theme_foundation_overrides.css
172 ms
owl.carousel.css
300 ms
owl.theme.css
299 ms
owl.transitions.css
363 ms
theme_base.css
278 ms
theme_base_responsive.css
265 ms
style.css
686 ms
jquery-ui-1.8.2.custom.css
386 ms
audio
536 ms
jquery.min.js
21 ms
swfobject.js
450 ms
jquery-ui-1.8.9.min.js
825 ms
jquery.easing.1.3.min.js
490 ms
jquery.mousewheel.min.js
544 ms
jquery.ui.scrollbar.min.js
606 ms
jquery.jplayer.min.js
720 ms
jplayer.playlist.js
720 ms
jQuery.cookie.js
719 ms
theme.js
741 ms
foundation.js
764 ms
tinynav.min.js
775 ms
google_fonts
1006 ms
jquery-ui.min.js
1049 ms
owl.carousel.min.js
869 ms
jquery.fitvids.js
819 ms
app.js
826 ms
lb2_signup.js
852 ms
css
54 ms
css
71 ms
css
70 ms
css
73 ms
css
70 ms
css
70 ms
css
69 ms
css
76 ms
css
85 ms
css
84 ms
css
80 ms
css
79 ms
css
80 ms
css
85 ms
css
86 ms
css
95 ms
css
94 ms
css
93 ms
css
95 ms
css
105 ms
css
104 ms
css
104 ms
css
103 ms
css
102 ms
css
104 ms
css
116 ms
css
115 ms
css
111 ms
css
110 ms
ga.js
96 ms
10404181_10206370166508435_157669026156723474_n.jpg
632 ms
danihoy2_small.jpg
366 ms
danihoy_small.jpg
365 ms
facebook_logo.png
152 ms
itunes-logo.jpg
166 ms
amazonmp3.png
165 ms
Keyboard_ad.jpg
356 ms
ABitofParadise-LOGO_full.jpg
354 ms
534238_10151420213935508_1008328548_n.jpg
191 ms
stick2.png
824 ms
islanddreamz.jpg
359 ms
PVR_L365_resized.jpg
351 ms
318264_454987311241467_911733458_n.jpg
680 ms
islandtime2.gif
358 ms
9-wW4zu3WNoD5Fjka35JmybsRidxnYrfzLNRqJkHfFo.ttf
105 ms
__utm.gif
32 ms
gradient_footer.png
386 ms
none
381 ms
gradient_header.png
385 ms
speaker.png
387 ms
gradient_player.png
447 ms
play.png
465 ms
pause.png
516 ms
play_sm.png
1284 ms
linkmkr_btn5grey_buycd.png
194 ms
all.js
167 ms
widgets.js
145 ms
Me_BlueHeaven.jpg
4111 ms
4_12_15-106.jpg
688 ms
Dani_Hoy-214-2_banner_1.jpg
1203 ms
11164569_10205914989534469_2263357527498343218_n.jpg
780 ms
BlueHeaven.jpg
1623 ms
video.html
106 ms
nav_soundwave.svg
835 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
847 ms
volume_knob.png
925 ms
widget-09ce031e2f25c1bdcefe8e2259c017329d55ee0cf30d48a56bf813304e8a9c53.css
243 ms
en.js
148 ms
video_player-0f8a3062e17f40621c61345b6eafbaadeae8c8c984a7a1c06324654326209ecf.js
292 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
357 ms
293 ms
xd_arbiter.php
249 ms
xd_arbiter.php
295 ms
photo-original.jpg
332 ms
k-logo-6e89a1dfb0acef06bf4313d05fdb86b6f5809542ce1517764a7bee4afcb419e1.png
166 ms
analytics.js
202 ms
ksr-icons-8a72398a16f375ecaca738ae23ef67764a761eaf10392b580b2206dc56a4e8b7.woff
31 ms
follow_button.64a917b4a230f163048902c783e1530f.en.html
57 ms
nr-892.min.js
83 ms
b04b883ad2
124 ms
jot
126 ms
css
719 ms
danihoy.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role] values are not valid
[aria-*] attributes do not have valid values
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
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
danihoy.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
Page has valid source maps
danihoy.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Danihoy.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Danihoy.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.
danihoy.com
Open Graph description is not detected on the main page of Danihoy. 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: