2.1 sec in total
36 ms
1.6 sec
437 ms
Visit johnbender.us now to see the best up-to-date Johnbender content and also check out these interesting facts you probably never knew about johnbender.us
Writings on computer stuff.
Visit johnbender.usWe analyzed Johnbender.us page load time and found that the first response time was 36 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
johnbender.us performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value2.6 s
87/100
25%
Value2.6 s
97/100
10%
Value2,900 ms
3/100
30%
Value0
100/100
15%
Value11.1 s
20/100
10%
36 ms
77 ms
62 ms
64 ms
64 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original Johnbender.us, 51% (40 requests) were made to Speakerd.s3.amazonaws.com and 8% (6 requests) were made to D2dfho4r6t7asi.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Speakerdeck.com.
Page size can be reduced by 364.5 kB (26%)
1.4 MB
1.0 MB
In fact, the total size of Johnbender.us main page is 1.4 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. 45% of websites need less resources to load. Images take 834.3 kB which makes up the majority of the site volume.
Potential reduce by 9.8 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 9.8 kB or 67% of the original size.
Potential reduce by 0 B
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. Johnbender images are well optimized though.
Potential reduce by 262.0 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 262.0 kB or 63% of the original size.
Potential reduce by 92.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. Johnbender.us needs all CSS files to be minified and compressed as it can save up to 92.7 kB or 81% of the original size.
Number of requests can be reduced by 19 (27%)
70
51
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnbender. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
johnbender.us
36 ms
bootstrap.min.css
77 ms
style.css
62 ms
cv.css
64 ms
font-awesome.min.css
64 ms
embed.js
85 ms
style.css
63 ms
cv.css
64 ms
bootstrap.min.css
57 ms
style.css
14 ms
font-awesome.min.css
17 ms
cv.css
14 ms
bootstrap.min.css
18 ms
ga.js
27 ms
fontawesome-webfont.woff
19 ms
af35e490a0b00131f6cb2abc05ca10ad
1139 ms
__utm.gif
11 ms
04706730a1090131ed084e04b85186c1
84 ms
player-131ee76e68102edd2d7959c929af06d1.css
33 ms
player-67e207486452a6edc528fc9bbb3a0e02.js
43 ms
slide_0.jpg
115 ms
ga.js
64 ms
linen-20977254ed0ba0794911c98be5e3e456.png
47 ms
embed_logo-7bd0769d19ac8220ab94eaee49f490c8.png
16 ms
share-bird-2f494451db023d0928249af611b3e226.png
28 ms
close-01577296b1552db3535d995dcc9288d6.png
37 ms
thumb_slide_0.jpg
84 ms
thumb_slide_1.jpg
89 ms
thumb_slide_2.jpg
87 ms
thumb_slide_3.jpg
99 ms
thumb_slide_4.jpg
82 ms
preview_slide_0.jpg
116 ms
preview_slide_1.jpg
119 ms
preview_slide_2.jpg
109 ms
preview_slide_3.jpg
114 ms
preview_slide_4.jpg
154 ms
tweet_button.html
150 ms
like.php
165 ms
__utm.gif
18 ms
__utm.gif
18 ms
jot
89 ms
Dt46LmMjzaB.js
293 ms
LVx-xkvaJ0b.png
332 ms
nr-885.min.js
43 ms
2f94e4d8c2
107 ms
slide_0.jpg
76 ms
thumb_slide_0.jpg
26 ms
thumb_slide_1.jpg
27 ms
thumb_slide_2.jpg
44 ms
thumb_slide_3.jpg
74 ms
thumb_slide_4.jpg
39 ms
thumb_slide_5.jpg
57 ms
thumb_slide_6.jpg
57 ms
thumb_slide_7.jpg
114 ms
thumb_slide_8.jpg
84 ms
thumb_slide_9.jpg
82 ms
thumb_slide_10.jpg
93 ms
thumb_slide_11.jpg
81 ms
thumb_slide_12.jpg
112 ms
thumb_slide_13.jpg
185 ms
thumb_slide_14.jpg
108 ms
thumb_slide_15.jpg
103 ms
thumb_slide_16.jpg
141 ms
thumb_slide_17.jpg
130 ms
preview_slide_0.jpg
161 ms
preview_slide_1.jpg
131 ms
preview_slide_2.jpg
187 ms
preview_slide_3.jpg
163 ms
preview_slide_4.jpg
161 ms
preview_slide_5.jpg
165 ms
preview_slide_6.jpg
189 ms
preview_slide_7.jpg
199 ms
preview_slide_8.jpg
187 ms
preview_slide_9.jpg
194 ms
__utm.gif
6 ms
tweet_button.html
38 ms
like.php
75 ms
__utm.gif
3 ms
jot
24 ms
johnbender.us 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
johnbender.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
johnbender.us 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
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 Johnbender.us 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 Johnbender.us 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.
johnbender.us
Open Graph description is not detected on the main page of Johnbender. 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: