6.4 sec in total
1.4 sec
4.7 sec
227 ms
Welcome to dannywuenschel.com homepage info - get ready to check Danny Wuenschel best content right away, or after learning these important things about dannywuenschel.com
Visit dannywuenschel.comWe analyzed Dannywuenschel.com page load time and found that the first response time was 1.4 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dannywuenschel.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value6.4 s
9/100
25%
Value11.2 s
5/100
10%
Value260 ms
83/100
30%
Value1.38
0/100
15%
Value9.3 s
31/100
10%
1430 ms
104 ms
204 ms
367 ms
290 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Dannywuenschel.com, 3% (2 requests) were made to Netdna.bootstrapcdn.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Dannywuenschel.com.
Page size can be reduced by 160.4 kB (7%)
2.2 MB
2.0 MB
In fact, the total size of Dannywuenschel.com main page is 2.2 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 81.2 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 81.2 kB or 82% of the original size.
Potential reduce by 37.7 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. Danny Wuenschel images are well optimized though.
Potential reduce by 18.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 22.8 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. Dannywuenschel.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 17% of the original size.
Number of requests can be reduced by 26 (46%)
57
31
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danny Wuenschel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
dannywuenschel.com
1430 ms
sbi-styles.min.css
104 ms
cookieblocker.min.css
204 ms
style.css
367 ms
style.css
290 ms
fancybox.css
295 ms
font-awesome.min.css
292 ms
font-awesome.css
26 ms
dannywuenschel.com
1066 ms
page-banner.css
307 ms
js_composer.min.css
579 ms
mf_gig_calendar.css
395 ms
velocity.min.js
394 ms
jquery.min.js
500 ms
jquery-migrate.min.js
463 ms
iron_parallax.js
493 ms
utilities.js
597 ms
plugins.all.min.js
651 ms
jquery.tweet.min.js
597 ms
main.js
599 ms
index.js
675 ms
index.js
687 ms
jquery.parallax.js
691 ms
complianz.min.js
698 ms
js_composer_front.min.js
745 ms
sbi-scripts.min.js
776 ms
style.css
599 ms
all.js
96 ms
sbi-sprite.png
179 ms
dw-logo_2016_2.png
182 ms
11187439_1080996018594041_7630587247722904799_o_slide.jpg
746 ms
divider.gif
181 ms
placeholder.png
181 ms
footer.jpg
259 ms
cover_signifier-300x267.jpg
335 ms
apple-music-logo.png
251 ms
amazon-music-logo.png
268 ms
spotify-logo.png
271 ms
cover_lonesomeroad.jpg
443 ms
landesschau.png
451 ms
DRPP2017-singer.jpg
364 ms
countrynale2016.jpg
371 ms
about-me_bg.jpg
707 ms
IMG_1635_quad.jpg
632 ms
about-me_dw_bw.jpg
506 ms
F18_9557_bw.jpg
629 ms
about-me_bw.jpg
555 ms
fontawesome-webfont.woff
20 ms
fontawesome-webfont.woff
563 ms
all.js
55 ms
45 ms
420050362_10163154647021521_8191943786157122317_nfull.jpg
481 ms
421260711_10163153134021521_4953176316086717639_nfull.jpg
530 ms
421031182_10163151520146521_6506582561995103520_nfull.jpg
553 ms
420088676_10163148338906521_4547333334594429319_nfull.jpg
551 ms
420113328_10163146944866521_5473005265125598203_nfull.jpg
592 ms
420005424_10163145111516521_4549027818512769385_nfull.jpg
630 ms
419742318_10163143330791521_4024237921015322890_nfull.jpg
633 ms
419789000_10163141756181521_8647287026491733124_nfull.jpg
648 ms
419237193_10163139563046521_8591321946223083512_nfull.jpg
742 ms
dannywuenschel.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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dannywuenschel.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
dannywuenschel.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dannywuenschel.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Dannywuenschel.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.
dannywuenschel.com
Open Graph description is not detected on the main page of Danny Wuenschel. 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: