11 sec in total
2.7 sec
6.7 sec
1.6 sec
Welcome to davidstaub.com homepage info - get ready to check David Staub best content right away, or after learning these important things about davidstaub.com
Welcome to David Staub\'s personal website
Visit davidstaub.comWe analyzed Davidstaub.com page load time and found that the first response time was 2.7 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
davidstaub.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value6.3 s
10/100
25%
Value10.6 s
7/100
10%
Value2,400 ms
5/100
30%
Value0.011
100/100
15%
Value17.4 s
4/100
10%
2700 ms
108 ms
64 ms
180 ms
207 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 19% of them (18 requests) were addressed to the original Davidstaub.com, 17% (16 requests) were made to Pixel.wp.com and 11% (10 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Davidstaub.com.
Page size can be reduced by 761.7 kB (20%)
3.8 MB
3.1 MB
In fact, the total size of Davidstaub.com main page is 3.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.3 kB or 82% of the original size.
Potential reduce by 143.0 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 Staub images are well optimized though.
Potential reduce by 245.8 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 245.8 kB or 64% of the original size.
Potential reduce by 328.7 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. Davidstaub.com needs all CSS files to be minified and compressed as it can save up to 328.7 kB or 80% of the original size.
Number of requests can be reduced by 53 (62%)
85
32
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of David Staub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.davidstaub.com
2700 ms
wp-emoji-release.min.js
108 ms
css
64 ms
style.css
180 ms
genericons.css
207 ms
jetpack.css
165 ms
jquery.js
251 ms
jquery-migrate.min.js
172 ms
widgets.js
79 ms
devicepx-jetpack.js
4 ms
gprofiles.js
57 ms
wpgroho.js
173 ms
navigation.js
228 ms
wp-embed.min.js
237 ms
sharing.js
242 ms
e-201611.js
4 ms
image-4122100-11457083
62 ms
250x250holidaycode-rev7.jpg
63 ms
ShowtheLove_Web.jpg
970 ms
2015-03-23-09.26.28-e1427125771185-624x741.jpg
608 ms
2015-03-23-09.35.21-1024x768.jpg
776 ms
wpid-20140408_222942.jpg
1645 ms
wrigley-field-opening-day-sign-2014-100-years-624x430.jpg
436 ms
loading.gif
328 ms
11457083-1417830915018
59 ms
lXbFu91a0t4
284 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
288 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
298 ms
xjAJXh38I15wypJXxuGMBtIh4imgI8P11RFo6YPCPC0.woff
358 ms
PRmiXeptR36kaC0GEAetxoUt79146ZFaIJxILcpzmhI.woff
358 ms
Genericons.svg
426 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
1 ms
cm
302 ms
hovercard.css
146 ms
services.css
158 ms
share
203 ms
g.gif
65 ms
count.json
139 ms
graph.facebook.com
200 ms
share
348 ms
count.json
137 ms
graph.facebook.com
460 ms
share
318 ms
count.json
134 ms
graph.facebook.com
458 ms
share
316 ms
count.json
132 ms
graph.facebook.com
455 ms
share
314 ms
count.json
130 ms
graph.facebook.com
467 ms
tweet.2c548e167cf5bdb0bd941e41896f257d.js
302 ms
g.gif
39 ms
g.gif
39 ms
g.gif
38 ms
g.gif
39 ms
g.gif
38 ms
g.gif
45 ms
g.gif
44 ms
g.gif
44 ms
g.gif
44 ms
g.gif
49 ms
g.gif
48 ms
g.gif
52 ms
g.gif
50 ms
g.gif
51 ms
g.gif
36 ms
www-embed-player-vflfNyN_r.css
157 ms
www-embed-player.js
239 ms
base.js
294 ms
kindle-device-assoc-b-300x250.jpg
82 ms
22 ms
syndication
204 ms
tweets.json
223 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
102 ms
ad_status.js
97 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
20 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
20 ms
proxy.jpg
79 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
57 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
NzaWFQ8l_normal.jpg
164 ms
BkZOuX0CEAAv1RM.jpg
250 ms
2Nc5TJm3_normal.jpg
266 ms
BkZcjadCQAEUVP5.jpg
351 ms
FB1GK_Y9_normal.jpeg
277 ms
C-thumbnail-copy_normal.jpg
278 ms
V_hKdipV_normal.jpg
279 ms
qEf3Ccl0_normal.jpg
275 ms
BkZ7PGPCMAAK7az.jpg
408 ms
PBJJCw64_normal.png
304 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
64 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
44 ms
proxy.jpg
51 ms
jot.html
32 ms
davidstaub.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
<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
davidstaub.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
davidstaub.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Davidstaub.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 Davidstaub.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.
davidstaub.com
Open Graph data is detected on the main page of David Staub. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: