4.6 sec in total
662 ms
1.4 sec
2.5 sec
Click here to check amazing David Hauser content for United States. Otherwise, check out these important facts you probably never knew about davidhauser.com
David Hauser
Visit davidhauser.comWe analyzed Davidhauser.com page load time and found that the first response time was 662 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
davidhauser.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value10.5 s
0/100
25%
Value5.6 s
53/100
10%
Value360 ms
72/100
30%
Value0.016
100/100
15%
Value7.8 s
45/100
10%
662 ms
12 ms
25 ms
224 ms
15 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Davidhauser.com, 21% (15 requests) were made to 38.media.tumblr.com and 18% (13 requests) were made to 33.media.tumblr.com. The less responsive or slowest element that took the longest time to load (662 ms) belongs to the original domain Davidhauser.com.
Page size can be reduced by 1.0 MB (48%)
2.2 MB
1.1 MB
In fact, the total size of Davidhauser.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. 70% of websites need less resources to load. Images take 814.3 kB which makes up the majority of the site volume.
Potential reduce by 347.3 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 347.3 kB or 84% of the original size.
Potential reduce by 44.3 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. David Hauser images are well optimized though.
Potential reduce by 424.1 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 424.1 kB or 63% of the original size.
Potential reduce by 223.4 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. Davidhauser.com needs all CSS files to be minified and compressed as it can save up to 223.4 kB or 80% of the original size.
Number of requests can be reduced by 17 (27%)
63
46
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of David Hauser. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
davidhauser.com
662 ms
pre_tumblelog.js
12 ms
css
25 ms
css
224 ms
normalize-2.1.3.min.css
15 ms
theme.css
20 ms
tumblelog_post_message_queue.js
18 ms
stylesheet.css
20 ms
jquery-1.10.2.min.js
5 ms
theme.min.js
4 ms
index.js
13 ms
avatar_cf284cdfa4cf_128.png
261 ms
tumblr_inline_nzj4jtkeZY1qdqvze_500.png
346 ms
like_iframe.html
194 ms
tumblr_inline_mvlowiHMEo1qdqvze.jpg
195 ms
tumblr_md12j3PDma1qdqvze.png
179 ms
jPhZlFHiyil7T5bicpSvkX1xGWpbk4W9VXDv6-cN5ba0iwd58WrQzGz9umEEzHnDmHc4PpyKEKC_gmYqBRe1mo7m3ZdDy2JUflmtJlZOiibqkcKxPXg
317 ms
uSxgxz_xeTbeROQltCx_LggUaa_ScxQceTuBhEdpecTlDZ3kQ79U4tSBxnECKYFU6BAqqHJs7F6JBGGLH9RH88wSlYmcy1SFifF1Ru5GVUPK4ExgaVM
316 ms
ga.js
184 ms
impixu
344 ms
tumblr_md1cehlFRE1qdqvze.jpg
80 ms
tumblr_inline_mhdgi4dDke1qz4rgp.jpg
173 ms
tumblr_md11xdlMZJ1qdqvze.jpg
170 ms
tumblr_md121frcIG1qdqvze.jpg
169 ms
tumblr_md125u6Rb81qdqvze.png
169 ms
tumblr_md127kKmh41qdqvze.png
170 ms
tumblr_md12fepftT1qdqvze.png
168 ms
tumblr_md12kyYapK1qdqvze.jpg
237 ms
tumblr_md1dqvYWQb1qdqvze.jpg
236 ms
tumblr_md12tmoalg1qdqvze.png
235 ms
tumblr_md12ybBahS1qdqvze.jpg
235 ms
tumblr_md1ccfLPZG1qdqvze.jpg
235 ms
tumblr_md1chf5llc1qdqvze.jpg
236 ms
tumblr_md1dcpWucP1qdqvze.jpg
267 ms
tumblr_md1djvC8Az1qdqvze.png
265 ms
tumblr_inline_mhdgkovUGK1qz4rgp.jpg
82 ms
tumblr_inline_mhdgok8yv81qz4rgp.png
81 ms
tumblr_md1238Dnmt1qdqvze.jpg
82 ms
tumblr_md1c27O1y51qdqvze.png
150 ms
tumblr_md12aepg1X1qdqvze.jpg
149 ms
tumblr_md12c6qZb71qdqvze.png
149 ms
tumblr_md12djB5bc1qdqvze.jpg
167 ms
tumblr_md1cijvDA21qdqvze.jpg
165 ms
tumblr_md1cpmfaLa1qdqvze.jpg
168 ms
tumblr_md1d4pVSMN1qdqvze.jpg
174 ms
tumblr_md3w0uHsVf1qdqvze.jpg
173 ms
impixu
262 ms
PMERKYCXslE4ZquoIeqFWVs5KN8sWpeelvogpRXezTQtipxMU07w8qDpfWV_nfcTos9vfBIScxBeLnVJrd6FtBN4flSXW6V0JkU0O0Dl8PDFlXgLrtU
262 ms
analytics.html
235 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
172 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
217 ms
Dtju0JkUlDlFXz0X0fsVeiR6XERUAAABLuADIUlixAQGOWbkIAAgAYyCwASNEsAMjcLIEKAlFUkSyCgIHKrEGAUSxJAGIUViwQIhYsQYDRLEmAYhRWLgEAIhYsQYBRFlZWVm4Af+FsASNsQUARAAA
20 ms
login_check.html
79 ms
9EzNll1U2N8
246 ms
__utm.gif
94 ms
_fCSSBA0dGg
220 ms
avatar_cf284cdfa4cf_40.png
78 ms
iframe_logo.png
123 ms
rapid-3.36.js
48 ms
rapidworker-1.2.js
52 ms
www-embed-player-vflfNyN_r.css
59 ms
www-embed-player.js
93 ms
base.js
150 ms
ga.js
102 ms
analytics.js
93 ms
cs.js
111 ms
__utm.gif
121 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
72 ms
ad_status.js
73 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
37 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
davidhauser.com accessibility score
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
davidhauser.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
Page has valid source maps
davidhauser.com SEO score
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 Davidhauser.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 Davidhauser.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.
davidhauser.com
Open Graph data is detected on the main page of David Hauser. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: