3.5 sec in total
267 ms
2.6 sec
673 ms
Welcome to davidbrin.com homepage info - get ready to check David Brin best content for United States right away, or after learning these important things about davidbrin.com
The official website of best-selling science fiction writer and futurist DAVID BRIN
Visit davidbrin.comWe analyzed Davidbrin.com page load time and found that the first response time was 267 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
davidbrin.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value10.0 s
0/100
25%
Value24.8 s
0/100
10%
Value22,240 ms
0/100
30%
Value0.169
70/100
15%
Value38.6 s
0/100
10%
267 ms
24 ms
132 ms
521 ms
291 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 11% of them (20 requests) were addressed to the original Davidbrin.com, 14% (25 requests) were made to O.twimg.com and 11% (19 requests) were made to Files.bannersnack.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Keepandshare.com.
Page size can be reduced by 1.4 MB (28%)
5.1 MB
3.7 MB
In fact, the total size of Davidbrin.com main page is 5.1 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.3 MB which makes up the majority of the site volume.
Potential reduce by 35.4 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 35.4 kB or 76% of the original size.
Potential reduce by 88.8 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 Brin images are well optimized though.
Potential reduce by 814.2 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 814.2 kB or 71% of the original size.
Potential reduce by 490.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. Davidbrin.com needs all CSS files to be minified and compressed as it can save up to 490.9 kB or 84% of the original size.
Number of requests can be reduced by 66 (40%)
164
98
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of David Brin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
davidbrin.com
267 ms
css
24 ms
inland-wood.css
132 ms
jquery-1.7.1.min.js
521 ms
jquery.nivo.slider.js
291 ms
buttons.js
9 ms
slim-081711.css
13 ms
q
84 ms
widget.js
59 ms
r.js
286 ms
counter.js
23 ms
embed.html
51 ms
embed.html
48 ms
embed.html
16 ms
22358129265.3673.1675252951.png
276 ms
bodybg.jpg
375 ms
contentbg.jpg
374 ms
shadow.png
151 ms
loading.gif
153 ms
slider0.jpg
478 ms
slider1.jpg
532 ms
slider2.jpg
607 ms
slider3.jpg
740 ms
slider4.jpg
799 ms
collectedarticles.jpg
579 ms
aboutdb.jpg
611 ms
insistenceofvisioncover.jpg
798 ms
brin-intro.jpg
854 ms
publicspeaking.jpg
852 ms
iaamoac.jpg
881 ms
contactdb.jpg
976 ms
counter.asp
6 ms
analytics.js
5 ms
collect
22 ms
aFCvJBS-R58
107 ms
collect
14 ms
collect
13 ms
embed.html
16 ms
embed.html
13 ms
embed.html
24 ms
8001_5.js
13 ms
EmbedCanvas.gz.js
20 ms
popup.js
4 ms
nifty.js
54 ms
colors.js
53 ms
bzuloal5
61 ms
buks7sf5
26 ms
bum8vf53
54 ms
www-embed-player-vflfNyN_r.css
85 ms
www-embed-player.js
99 ms
widgets.js
27 ms
player_api
82 ms
buks7sf5_0
98 ms
wzr-DSDMkJM
103 ms
bzuloal5_0
99 ms
bum8vf53_0
84 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
46 ms
ad_status.js
38 ms
26 ms
24 ms
23 ms
www-widgetapi.js
21 ms
buks7sf5_1
78 ms
bum8vf53_1
149 ms
bzuloal5_1
80 ms
c.php
147 ms
f.php
221 ms
embed_calendar.php
552 ms
r.php
216 ms
meter.asp
8 ms
meter.asp
55 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
65 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
65 ms
getAllAppDefault.esi
107 ms
uxO37yTmqNw
85 ms
buks7sf5_2
69 ms
syndication
114 ms
696417626768019456
183 ms
buks7sf5_3
131 ms
bum8vf53_2
116 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
19 ms
getSegment.php
38 ms
checkOAuth.esi
34 ms
t.dhj
19 ms
pixel
27 ms
0.jpg
201 ms
t.dhj
15 ms
pixel
32 ms
cm
25 ms
x35248
171 ms
adxmapping.php
16 ms
s-3271.xgi
14 ms
hbpix
26 ms
14 ms
bum8vf53_3
25 ms
10 ms
episodes.js
313 ms
cache-1457363096-calendar.css
858 ms
cache-1458315200-calendar.js
1328 ms
xrefid.xgi
9 ms
pixel
13 ms
bum8vf53_4
34 ms
2981
28 ms
proxy.jpg
373 ms
proxy.jpg
390 ms
proxy.jpg
343 ms
proxy.jpg
296 ms
proxy.jpg
299 ms
proxy.jpg
283 ms
proxy.jpg
377 ms
proxy.jpg
322 ms
proxy.jpg
329 ms
proxy.jpg
476 ms
proxy.jpg
410 ms
proxy.jpg
447 ms
proxy.jpg
413 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
10 ms
bum8vf53_5
75 ms
w27AuOM2_normal.jpeg
176 ms
Mv4fgDci_normal.jpg
187 ms
Cd7fEqmVIAAFxPD.jpg:small
189 ms
Cd7RHmlVIAEQhbc.jpg:small
214 ms
Cd3s1lGVIAAxrN7.jpg:small
214 ms
Cd3kSKAVAAAm_pN.jpg:small
213 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
215 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
228 ms
t.php
125 ms
c.php
129 ms
proxy.jpg
231 ms
proxy.jpg
213 ms
proxy.jpg
207 ms
proxy.jpg
255 ms
proxy.jpg
300 ms
proxy.jpg
306 ms
proxy.jpg
240 ms
proxy.jpg
235 ms
proxy.jpg
388 ms
proxy.jpg
265 ms
proxy.jpg
252 ms
proxy.jpg
215 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
25 ms
buttons.ab966a004186897711de4a5ed256c924.css
10 ms
blogger_32.png
8 ms
wordpress_32.png
9 ms
facebook_32.png
7 ms
googleplus_32.png
8 ms
twitter_32.png
8 ms
reddit_32.png
9 ms
stumbleupon_32.png
8 ms
pinterest_32.png
9 ms
sharethis_32.png
10 ms
email_32.png
9 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
7 ms
st.1188278743c14064d5e8ae56c8ada29c.js
11 ms
jot.html
2 ms
please_wait.gif
74 ms
ga.js
11 ms
fns_asynch_api.php
326 ms
fontawesome-webfont.woff
207 ms
__utm.gif
12 ms
collect
57 ms
ir
18 ms
77 ms
widgets.css
13 ms
q
30 ms
51leMKwl7gL._SL75_.jpg
51 ms
amazon-logo-w_tpng.png
8 ms
gem-onyx-tli.gif
4 ms
gem-onyx-tmi.gif
7 ms
gem-onyx-tri.gif
5 ms
gem-onyx-lm.gif
7 ms
gem-onyx-rm.gif
10 ms
gem-onyx-blis.gif
11 ms
gem-onyx-bm.gif
10 ms
gem-onyx-bris.gif
11 ms
davidbrin.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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
davidbrin.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
Missing source maps for large first-party JavaScript
davidbrin.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Davidbrin.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Davidbrin.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.
davidbrin.com
Open Graph description is not detected on the main page of David Brin. 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: