4.7 sec in total
721 ms
1.8 sec
2.1 sec
Click here to check amazing Aaf content for United States. Otherwise, check out these important facts you probably never knew about aaf.org
Visit aaf.orgWe analyzed Aaf.org page load time and found that the first response time was 721 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
aaf.org performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value51.3 s
0/100
25%
Value10.7 s
7/100
10%
Value1,780 ms
10/100
30%
Value0.002
100/100
15%
Value33.1 s
0/100
10%
721 ms
66 ms
75 ms
77 ms
95 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 99% of them (84 requests) were addressed to the original Aaf.org, 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (721 ms) belongs to the original domain Aaf.org.
Page size can be reduced by 424.8 kB (21%)
2.0 MB
1.6 MB
In fact, the total size of Aaf.org main page is 2.0 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 21.7 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 3.3 kB, which is 12% 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 21.7 kB or 78% of the original size.
Potential reduce by 45.1 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. Aaf images are well optimized though.
Potential reduce by 229.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 229.2 kB or 73% of the original size.
Potential reduce by 128.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. Aaf.org needs all CSS files to be minified and compressed as it can save up to 128.8 kB or 82% of the original size.
Number of requests can be reduced by 58 (70%)
83
25
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
aaf.org
721 ms
node.css
66 ms
defaults.css
75 ms
system.css
77 ms
system-menus.css
95 ms
content-module.css
95 ms
ckeditor.css
100 ms
ctools.css
98 ms
date.css
120 ms
jquery-ui.css
122 ms
datepicker.1.7.css
132 ms
jquery.timeentry.css
134 ms
filefield.css
136 ms
video.css
134 ms
video_filter.css
136 ms
calendarsearch.css
154 ms
pantheonCustomDropDown.css
154 ms
hero-area.css
154 ms
hero-area-anon.css
132 ms
panthdocumentsearch.css
132 ms
pantheonLeftMenu.css
161 ms
panthwebcastsearch.css
161 ms
user.css
163 ms
forum.css
163 ms
views.css
195 ms
general.css
172 ms
jquery.ui.all.css
173 ms
jquery-ui-1.8.custom.css
201 ms
style.css
195 ms
jquery.js
202 ms
drupal.js
202 ms
video.js
243 ms
calendarsearch.js
215 ms
pantheonCustomDropDown.js
214 ms
jquery.cycle.all.min.js
227 ms
hero_area.js
174 ms
hero_area_anon.js
172 ms
panthdocumentsearch.js
213 ms
jquery.form.js
196 ms
ui.core.min.js
195 ms
ui.datepicker.min.js
193 ms
pantheonLeftMenu.js
191 ms
panthwebcastsearch.js
192 ms
popup.js
199 ms
jquery.validate.js
197 ms
jquery.form.js
187 ms
webform.district.js
187 ms
aaf.utility.js
186 ms
events.district.js
186 ms
googleanalytics.js
200 ms
jquery.ui.base.css
137 ms
jquery.ui.theme.css
136 ms
jquery.ui.core.css
41 ms
jquery.ui.datepicker.css
21 ms
analytics.js
401 ms
bg.png
179 ms
blank.gif
78 ms
aaf_logo.png
76 ms
heroAreaBg.png
73 ms
slideShowImg.gif
73 ms
0315_AAF_Maintenance_Member_Website_979x277_0.jpg
98 ms
979x277_AAF-web-banner.jpg
92 ms
TLEE_Chicago_MemberSite_Hero.png
93 ms
4015_AHOA_Event_Member_Website_Slide2.png
87 ms
heroAreaBgActionBg.gif
61 ms
btnPrev.gif
83 ms
btnNext.gif
80 ms
btnHeroReadmore.gif
80 ms
contentMiddleRepeat.gif
102 ms
contentMiddleFixed.gif
79 ms
leftNavMenuBdr.gif
102 ms
icon_rss.gif
78 ms
icon_twitter.gif
104 ms
icon_facebook.gif
105 ms
rightPanelBg.gif
103 ms
loginFieldBg.gif
104 ms
btnSignin.png
103 ms
blank.gif
105 ms
btnJoin.png
104 ms
footer.png
125 ms
popupBg.gif
141 ms
blank.gif
106 ms
ajax-loader.gif
106 ms
btnSelected.gif
107 ms
btnDeSelected.gif
106 ms
aaf.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.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
aaf.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
aaf.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Aaf.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 Aaf.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.
aaf.org
Open Graph description is not detected on the main page of Aaf. 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: