7.1 sec in total
127 ms
5.7 sec
1.3 sec
Welcome to od.org homepage info - get ready to check Od best content right away, or after learning these important things about od.org
Open Doors serves persecuted Christians around the world by providing vital support, delivering resources, and providing training.
Visit od.orgWe analyzed Od.org page load time and found that the first response time was 127 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
od.org performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value22.9 s
0/100
25%
Value26.1 s
0/100
10%
Value17,940 ms
0/100
30%
Value0.006
100/100
15%
Value28.6 s
0/100
10%
127 ms
573 ms
110 ms
288 ms
391 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Od.org, 58% (31 requests) were made to Opendoors.org and 11% (6 requests) were made to Content.powerapps.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Api.geoapify.com.
Page size can be reduced by 191.7 kB (21%)
927.1 kB
735.4 kB
In fact, the total size of Od.org main page is 927.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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 584.8 kB which makes up the majority of the site volume.
Potential reduce by 45.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. This page needs HTML code to be minified as it can gain 10.7 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.4 kB or 81% of the original size.
Potential reduce by 52.5 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. Od images are well optimized though.
Potential reduce by 21.9 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 21.9 kB or 30% of the original size.
Potential reduce by 71.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. Od.org needs all CSS files to be minified and compressed as it can save up to 71.9 kB or 33% of the original size.
Number of requests can be reduced by 32 (73%)
44
12
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Od. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
od.org
127 ms
573 ms
getresourcemanager
110 ms
bootstrap.min.css
288 ms
glyphicons-font-awesome-migrate.min.css
391 ms
preform.bundle-240556d2d6.css
207 ms
tiny-slider.css
461 ms
index.css
694 ms
templatedefaults.css
616 ms
index.css
766 ms
templatedefaults.css
540 ms
all.min.css
277 ms
jquery.min.js
195 ms
popper.min.js
339 ms
bootstrap.min.js
259 ms
jquery.timeago.js
564 ms
jquery.cookie.js
584 ms
tiny-slider.js
972 ms
index.js
653 ms
js
324 ms
offlinenotification.css
653 ms
preform.bundle-238a2fff81.js
304 ms
prop-types.js
980 ms
fela.js
979 ms
fela-dom.js
980 ms
pcf.bundle-bb82d8b481.js
318 ms
react-fela.js
1101 ms
fluentui-react.js
1395 ms
player.js
313 ms
loadPcfControls.js
1100 ms
postpreform.bundle-f4f91a6eb4.js
300 ms
app.bundle-f7eaf3ce8e.js
299 ms
default-1033.bundle-eda4e638fd.js
275 ms
header-logo
157 ms
wwl22-map.jpg
414 ms
footer-logo
158 ms
popup-header
414 ms
fa-solid-900.woff
712 ms
fa-regular-400.woff
846 ms
proximanova-medium-webfont.woff
1118 ms
proximanova-regular-webfont.woff
1116 ms
BrotherAndrewPortrait-extended-scaled2.jpg
255 ms
667359332
143 ms
ftn85-webfont.woff
791 ms
impact-banner.jpg
269 ms
1351264873-0239a24cf24b4cc1947d7212f21965cbd03c56764c978e4c07f4a214d3f51b4b-d.jpg
205 ms
player.js
726 ms
player.css
656 ms
vuid.min.js
650 ms
proximanova-extrabold-webfont.woff
716 ms
ftn65-webfont.woff
715 ms
ipinfo
1450 ms
1351264873-0239a24cf24b4cc1947d7212f21965cbd03c56764c978e4c07f4a214d3f51b4b-d
402 ms
od.org accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
od.org 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
Missing source maps for large first-party JavaScript
od.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Od.org 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 Od.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.
od.org
Open Graph data is detected on the main page of Od. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: