6.6 sec in total
444 ms
5.9 sec
214 ms
Welcome to realityandtruth.com homepage info - get ready to check Realityandtruth best content right away, or after learning these important things about realityandtruth.com
Home
Visit realityandtruth.comWe analyzed Realityandtruth.com page load time and found that the first response time was 444 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
realityandtruth.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value6.4 s
9/100
25%
Value6.3 s
42/100
10%
Value800 ms
37/100
30%
Value0.057
98/100
15%
Value10.4 s
24/100
10%
444 ms
28 ms
15 ms
21 ms
35 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Realityandtruth.com, 17% (18 requests) were made to Pbs.twimg.com and 13% (14 requests) were made to Dynamic.websimages.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Realityandtruth.com.
Page size can be reduced by 579.1 kB (41%)
1.4 MB
838.4 kB
In fact, the total size of Realityandtruth.com 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. 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 616.4 kB which makes up the majority of the site volume.
Potential reduce by 84.1 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 84.1 kB or 74% of the original size.
Potential reduce by 13.7 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. Realityandtruth images are well optimized though.
Potential reduce by 342.7 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 342.7 kB or 65% of the original size.
Potential reduce by 138.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. Realityandtruth.com needs all CSS files to be minified and compressed as it can save up to 138.7 kB or 87% of the original size.
Number of requests can be reduced by 53 (58%)
91
38
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Realityandtruth. 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.
www.realityandtruth.com
444 ms
css
28 ms
modernizr-old.js
15 ms
require.js
21 ms
jquery.min.js
35 ms
bootstrap.js
18 ms
.theme.css
3709 ms
sitebase.css
11 ms
view.app.js
21 ms
collector.js
4 ms
bg_body.png
59 ms
Logo%20101009.jpg
272 ms
btn_donateCC_LG.gif
49 ms
bg_top_gradient.png
25 ms
new%20building%20purchased%201.jpg
383 ms
1233532_10101029758483098_118608644_n.jpg
190 ms
660x390photo_1338129207772-1-0%20levinsky%20park.jpg
247 ms
tutwiler%20picture.jpg
189 ms
prayer-on-my-knees4.jpg
1476 ms
Tennis%20Logo.jpg
494 ms
pixel.gif
47 ms
ModuleClassLoader.js
9 ms
tooltip.css
9 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
18 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
24 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
22 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
30 ms
creativeCommons.js
14 ms
translate.js
6 ms
localize.js
5 ms
locale.js
9 ms
3 ms
ga.js
10 ms
header_editor_view.js
47 ms
image_view.js
17 ms
text_image_view.js
16 ms
twitter-feed_view.js
17 ms
share_button_view.js
17 ms
email_list_view.js
17 ms
donate_view.js
17 ms
__utm.gif
32 ms
text_view.js
6 ms
addthis_widget.js
31 ms
widgets.js
102 ms
button_view.js
23 ms
title_view.js
23 ms
66 ms
300lo.json
56 ms
all.js&version=v2.0
67 ms
widgets.js
49 ms
plusone.js
87 ms
counter.5524cceca805eb4b9b2b.js
13 ms
sh.8e5f85691f9aaa082472a194.html
40 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
24 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
27 ms
shares.json
33 ms
syndication
123 ms
345639413285539841
240 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
37 ms
138 ms
cb=gapi.loaded_0
61 ms
cb=gapi.loaded_1
75 ms
fastbutton
113 ms
xd_arbiter.php
46 ms
xd_arbiter.php
76 ms
postmessageRelay
46 ms
pixel
33 ms
cb=gapi.loaded_0
14 ms
cb=gapi.loaded_1
13 ms
grlryt2bdKIyfMSOhzd1eA.woff
39 ms
pixel
15 ms
3193398744-postmessagerelay.js
40 ms
rpc:shindig_random.js
42 ms
jot
36 ms
cb=gapi.loaded_0
2 ms
1f496.png
50 ms
proxy.jpg
81 ms
1f60a.png
84 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
20 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
24 ms
cd0a96457b3c1127751f3a2e7850966f_normal.jpeg
73 ms
bd71a6078115de7ffa614d24ec5d8328_normal.jpeg
68 ms
corrie-ten-boom_normal.jpg
70 ms
atZvKz5W_normal.jpeg
76 ms
klwfICwe_normal.jpg
84 ms
PUhPp2c5_normal.jpg
75 ms
QC7xVbUn_normal.jpg
75 ms
8YpVZ15m_normal.jpg
110 ms
AReyDh6i_normal.jpeg
99 ms
yzkICzI2_normal.png
101 ms
a5ec63d2b90af5104d0ecf8d3a431f68_normal.jpeg
100 ms
n6Hw4c8o_normal.jpg
99 ms
Cd6vLFkWoAAPvB3.jpg:small
274 ms
Cd2l6zeWoAMvZzA.jpg:small
122 ms
CdzXWqdWIAAoHq0.jpg:small
114 ms
CdouX--WoAAvqSd.jpg:small
117 ms
CdeayKlUYAAVe3E.jpg:small
120 ms
CdXSXPnWIAEcvXm.jpg:small
151 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
71 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
92 ms
proxy.jpg
63 ms
jot.html
2 ms
ping
44 ms
like.php
132 ms
LVx-xkvaJ0b.png
22 ms
realityandtruth.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
Image elements do not have [alt] attributes
realityandtruth.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
realityandtruth.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 doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Realityandtruth.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 Realityandtruth.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.
realityandtruth.com
Open Graph description is not detected on the main page of Realityandtruth. 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: