5.5 sec in total
52 ms
2.8 sec
2.7 sec
Welcome to discoveringreason.com homepage info - get ready to check Discovering Reason best content right away, or after learning these important things about discoveringreason.com
Discovering Reason promotes science and reason to a public that desperately needs it while fighting superstition and religious dogma.
Visit discoveringreason.comWe analyzed Discoveringreason.com page load time and found that the first response time was 52 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
discoveringreason.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value3.4 s
67/100
25%
Value3.0 s
94/100
10%
Value330 ms
75/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
52 ms
186 ms
60 ms
108 ms
96 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Discoveringreason.com, 19% (23 requests) were made to Apis.google.com and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (630 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 667.2 kB (30%)
2.3 MB
1.6 MB
In fact, the total size of Discoveringreason.com main page is 2.3 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 184.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 184.2 kB or 77% of the original size.
Potential reduce by 102.6 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. Discovering Reason images are well optimized though.
Potential reduce by 148.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 148.2 kB or 41% of the original size.
Potential reduce by 232.2 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. Discoveringreason.com needs all CSS files to be minified and compressed as it can save up to 232.2 kB or 80% of the original size.
Number of requests can be reduced by 64 (57%)
112
48
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovering Reason. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
discoveringreason.com
52 ms
www.discoveringreason.com
186 ms
3375562265-css_bundle_v2.css
60 ms
authorization.css
108 ms
plusone.js
96 ms
element.js
54 ms
show_ads.js
26 ms
3226477086-widgets.js
53 ms
image
119 ms
cb=gapi.loaded_0
32 ms
cb=gapi.loaded_1
33 ms
google_top_exp.js
29 ms
Discovering%2BReason%2Bblog%2Blogo.png
74 ms
blogger-powerby-blue.gif
73 ms
translateelement.css
108 ms
main.js
168 ms
icon18_edit_allbkg.gif
71 ms
dawkins%2Bletter.jpg
69 ms
its%2Bme%2Byou%2Bgod.jpg
74 ms
top%2B10%2Blist.png
61 ms
btn_donate_LG.gif
85 ms
pixel.gif
85 ms
arrow_dropdown.gif
87 ms
icon18_wrench_allbkg.png
54 ms
icon18_email.gif
61 ms
icon_feed12.png
86 ms
subscribe-netvibes.png
146 ms
subscribe-yahoo.png
147 ms
white%2Bhouse%2Bin%2Bgay%2Bcolors.jpg
59 ms
Discovering%2BReason%2Bcomment%2Bfrom%2BTaylor.png
67 ms
tough%2Bchristian%2Bquestion.jpg
60 ms
tough%2Bchristian%2Bquestion.jpg
58 ms
David%2BSmalley%2Bdogma%2Bdebate.png
65 ms
the%2Bchristian%2Bthing%2Bto%2Bdo%2Batheist%2Bmeme.png
84 ms
divine+plan.png
57 ms
David%2BSmalley%2Bdogma%2Bdebate.png
59 ms
Smart%2BApparel%2Blogo%2B4%2Binch%2Bwhite%2Bbackground.png
84 ms
blank.html
55 ms
navbar.g
104 ms
Exla3ttIKzo
113 ms
white80.png
62 ms
share_buttons_20_3.png
58 ms
all.js
349 ms
oEl9kVl6KPc
80 ms
icons_gray.png
30 ms
platform:gapi.iframes.style.common.js
43 ms
arrows-dark.png
30 ms
ca-pub-9549544274506507.js
241 ms
zrt_lookup.html
152 ms
show_ads_impl.js
113 ms
element_main.js
156 ms
www-embed-player-vflfNyN_r.css
276 ms
www-embed-player.js
376 ms
base.js
537 ms
black50.png
92 ms
cb=gapi.loaded_0
120 ms
cb=gapi.loaded_1
118 ms
fastbutton
250 ms
s_top.png
109 ms
s_bottom.png
180 ms
cb=gapi.loaded_2
184 ms
cb=gapi.loaded_3
225 ms
fastbutton
245 ms
fastbutton
301 ms
fastbutton
314 ms
fastbutton
272 ms
fastbutton
269 ms
fastbutton
284 ms
fastbutton
307 ms
fastbutton
326 ms
ads
502 ms
osd.js
129 ms
ads
495 ms
translate_24dp.png
311 ms
l
121 ms
cleardot.gif
612 ms
postmessageRelay
186 ms
ads
425 ms
cb=gapi.loaded_4
140 ms
cb=gapi.loaded_0
143 ms
cb=gapi.loaded_1
144 ms
grlryt2bdKIyfMSOhzd1eA.woff
200 ms
postmessageRelay
195 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
104 ms
311 ms
te_ctrl3.gif
49 ms
xd_arbiter.php
366 ms
xd_arbiter.php
630 ms
3193398744-postmessagerelay.js
119 ms
rpc:shindig_random.js
116 ms
cb=gapi.loaded_0
110 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
311 ms
ad_status.js
62 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
19 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
21 ms
m_js_controller.js
25 ms
abg.js
39 ms
favicon
69 ms
googlelogo_color_112x36dp.png
61 ms
nessie_icon_tiamat_white.png
61 ms
s
49 ms
x_button_blue2.png
36 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
3 ms
306752634-lightbox_bundle.css
33 ms
297602417-lbx.js
35 ms
like_box.php
68 ms
ui
161 ms
ebiMDO3r-8l.css
284 ms
jGc-59L_9lo.css
352 ms
q68gy-v_YMF.js
490 ms
FJmpeSpHpjS.js
619 ms
0wM5s1Khldu.js
504 ms
1bNoFZUdlYZ.js
485 ms
10858373_763583563695615_8657804195188942397_n.png
287 ms
wL6VQj7Ab77.png
79 ms
s7jcwEQH7Sx.png
77 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
135 ms
discoveringreason.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
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.
discoveringreason.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
discoveringreason.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Discoveringreason.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 Discoveringreason.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.
discoveringreason.com
Open Graph description is not detected on the main page of Discovering Reason. 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: