2.4 sec in total
180 ms
1.8 sec
467 ms
Visit odb.org now to see the best up-to-date Odb content for United States and also check out these interesting facts you probably never knew about odb.org
Daily Devotionals
Visit odb.orgWe analyzed Odb.org page load time and found that the first response time was 180 ms and then it took 2.3 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.
odb.org performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value13.1 s
0/100
25%
Value6.1 s
44/100
10%
Value1,560 ms
13/100
30%
Value0.057
98/100
15%
Value15.8 s
6/100
10%
180 ms
62 ms
51 ms
25 ms
57 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 55% of them (51 requests) were addressed to the original Odb.org, 3% (3 requests) were made to S.gravatar.com and 3% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 982.5 kB (56%)
1.7 MB
766.3 kB
In fact, the total size of Odb.org main page is 1.7 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. 65% of websites need less resources to load. Javascripts take 637.4 kB which makes up the majority of the site volume.
Potential reduce by 118.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 118.2 kB or 80% of the original size.
Potential reduce by 41.4 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. Odb images are well optimized though.
Potential reduce by 432.4 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 432.4 kB or 68% of the original size.
Potential reduce by 390.5 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. Odb.org needs all CSS files to be minified and compressed as it can save up to 390.5 kB or 79% of the original size.
Number of requests can be reduced by 69 (81%)
85
16
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
odb.org
180 ms
css
62 ms
default.css
51 ms
bootstrap.min.css
25 ms
bootstrap-xxs.min.css
57 ms
font-awesome.min.css
84 ms
kp-menus.min.css
57 ms
subscriptions.css
85 ms
sharing.css
87 ms
css
35 ms
rbc-profiles.css
87 ms
default.css
88 ms
rbc-profiles-responsive.css
89 ms
rbc-profiles-datepicker.css
100 ms
dashicons.min.css
129 ms
thickbox.css
104 ms
grid.css
111 ms
note.css
109 ms
components.css
117 ms
jquery.js
173 ms
jquery-migrate.min.js
133 ms
bootstrap.min.js
15 ms
kp.min.js
134 ms
kickpress.js
133 ms
jquery.validate.min.js
142 ms
sharing.js
153 ms
jquery.fitvids.js
148 ms
script.min.js
163 ms
rbc-profiles-datepicker.js
192 ms
rbc-profiles-fitvids.js
168 ms
ajax.js
190 ms
mono_space_light.css
182 ms
cforms.js
183 ms
swfobject.js
190 ms
style.css
193 ms
all.js
276 ms
wp-emoji-release.min.js
154 ms
core.min.js
134 ms
datepicker.min.js
136 ms
mediaelement-and-player.min.js
163 ms
jquery.infinitescroll.min.js
141 ms
comment-reply.min.js
147 ms
thickbox.js
163 ms
jquery.form.min.js
161 ms
scripts.js
163 ms
devicepx-jetpack.js
59 ms
gprofiles.js
53 ms
wpgroho.js
166 ms
wp-embed.min.js
171 ms
mep-feature-googleanalytics.js
187 ms
rbc-profiles-custom.js
188 ms
e-201609.js
6 ms
analytics.js
25 ms
collect
62 ms
calendar.css
77 ms
collect
66 ms
style.css
55 ms
29-770x425.jpg
40 ms
share-odb-2016-02-29.jpg
68 ms
3e63a0549b31cf4ceb2ba9c0308eb3fb
70 ms
b4079d2717faf63f0c948062952f4b33
68 ms
1297f6cb52235615eb2ef9019943b5e9
70 ms
odbm_horz_logo_gray.png
43 ms
6cc07adc849039e2eb1bca30f0db459e
105 ms
f62c312f74b34ae8483885649ec0240c
136 ms
odb_logo.svg
40 ms
donate-img.svg
36 ms
odb_phone.png
161 ms
loading.gif
38 ms
walkinginhisstrength.jpg
42 ms
newlifepbanner.jpg
62 ms
d644e1a4cbcd42cf3b5d38c8ccfbb09e
102 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
115 ms
fontawesome-webfont.woff
91 ms
glyphicons-halflings-regular.woff
20 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
68 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
68 ms
349 ms
like.php
352 ms
xd_arbiter.php
358 ms
xd_arbiter.php
561 ms
g.gif
295 ms
jquery.lazyload.min.js
97 ms
loadingAnimation.gif
66 ms
hovercard.css
59 ms
services.css
85 ms
fql.query
179 ms
vpc6VNjRPXV.js
494 ms
LVx-xkvaJ0b.png
560 ms
vpc6VNjRPXV.js
202 ms
nr-852.min.js
18 ms
899937db96
52 ms
odb.org 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.
odb.org 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
odb.org 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odb.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Odb.org 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.
odb.org
Open Graph data is detected on the main page of Odb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: