1.8 sec in total
77 ms
1.4 sec
302 ms
Click here to check amazing Aod content for United States. Otherwise, check out these important facts you probably never knew about aod.org
Sharing Christ in Southeast Michigan
Visit aod.orgWe analyzed Aod.org page load time and found that the first response time was 77 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
aod.org performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value7.6 s
4/100
25%
Value8.0 s
22/100
10%
Value1,570 ms
13/100
30%
Value0.807
5/100
15%
Value15.1 s
7/100
10%
77 ms
563 ms
7 ms
164 ms
85 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 79% of them (77 requests) were addressed to the original Aod.org, 8% (8 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (563 ms) belongs to the original domain Aod.org.
Page size can be reduced by 348.5 kB (22%)
1.6 MB
1.3 MB
In fact, the total size of Aod.org main page is 1.6 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 98.3 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 16.8 kB, which is 13% 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 98.3 kB or 79% of the original size.
Potential reduce by 34.9 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. Aod images are well optimized though.
Potential reduce by 81.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 81.4 kB or 64% of the original size.
Potential reduce by 133.8 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. Aod.org needs all CSS files to be minified and compressed as it can save up to 133.8 kB or 82% of the original size.
Number of requests can be reduced by 28 (44%)
64
36
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aod. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
aod.org
77 ms
www.aod.org
563 ms
font-awesome.min.css
7 ms
main.min.css
164 ms
Common.css
85 ms
Aod.css
87 ms
meganav.min.css
88 ms
style.min.css
67 ms
prototype.js
31 ms
jquery.min.js
43 ms
jquery.url.js
105 ms
functions.js
96 ms
jquery-ui.min.js
60 ms
jquery-jtemplates.js
370 ms
jquery-ui-1.10.4.custom.css
156 ms
GAUtil.min.js
100 ms
js
56 ms
main.min.js
156 ms
jsapi.js
183 ms
rssdisplayer.js
133 ms
jquery.capSlide.js
163 ms
corners.js
164 ms
fullcalendar.css
167 ms
script.js
168 ms
wowsliderdof.js
141 ms
BasicLinearDof.js
140 ms
LazyLoad.min.js
140 ms
css
56 ms
bg-html.png
31 ms
37 ms
default+en.css
4 ms
default+en.I.js
10 ms
bg-header.png
41 ms
sprites.png
40 ms
grey.png
81 ms
217D19BE9150405E900199A6AE59AB21.ashx
42 ms
941116551D4C4B0F908F7F80AD49CFAC.ashx
40 ms
8645D380BF9A4356BBD7212F4BC988C3.ashx
39 ms
02510683E259479DB21EB3B9085FEF87.ashx
80 ms
B259C8E895814B6FB7DA08BC27F12DFD.ashx
79 ms
5EB53003F2ED4BD385D254F51DC77E1D.ashx
78 ms
421E2D4CE4E444A98577DE82851D0025.ashx
79 ms
186A9711FC6842EF97F6BD97080F4D01.ashx
80 ms
9CE2B5AF296048789B109D945FBCA297.ashx
134 ms
BB9ADA6E44E34F1EA86B8EC48ABFD508.ashx
134 ms
D0267FF8D1DA4F7C8579CBF1E3122D14.ashx
133 ms
18BC8F31CF5341248DB54AA5A444C70D.ashx
134 ms
676BEF8DB4604225A3306BA8602BF85D.ashx
134 ms
BBBF7958B62A45C1B379695E020ED62D.ashx
134 ms
ga.js
35 ms
menu-dropdown-bg.gif
144 ms
121 ms
119 ms
159 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
98 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
118 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
131 ms
fontawesome-webfont.woff
36 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
139 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
138 ms
__utm.gif
61 ms
widget_header.ashx
117 ms
bg-footerBlue.png
126 ms
127 ms
126 ms
123 ms
142 ms
149 ms
W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf
95 ms
OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf
96 ms
t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf
88 ms
124 ms
100 ms
129 ms
arrows.png
103 ms
117 ms
124 ms
125 ms
155 ms
158 ms
133 ms
105 ms
217D19BE9150405E900199A6AE59AB21.ashx
30 ms
941116551D4C4B0F908F7F80AD49CFAC.ashx
28 ms
8645D380BF9A4356BBD7212F4BC988C3.ashx
28 ms
02510683E259479DB21EB3B9085FEF87.ashx
34 ms
B259C8E895814B6FB7DA08BC27F12DFD.ashx
33 ms
5EB53003F2ED4BD385D254F51DC77E1D.ashx
32 ms
421E2D4CE4E444A98577DE82851D0025.ashx
54 ms
186A9711FC6842EF97F6BD97080F4D01.ashx
56 ms
89 ms
61 ms
95 ms
68 ms
75 ms
49 ms
84 ms
61 ms
aod.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
aod.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
Browser errors were logged to the console
Page has valid source maps
aod.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Aod.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 Aod.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.
aod.org
Open Graph data is detected on the main page of Aod. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: