1.7 sec in total
366 ms
949 ms
410 ms
Click here to check amazing Aai content for Philippines. Otherwise, check out these important facts you probably never knew about aai.org
Visit aai.orgWe analyzed Aai.org page load time and found that the first response time was 366 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
aai.org performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value19.3 s
0/100
25%
Value10.6 s
7/100
10%
Value570 ms
52/100
30%
Value0.029
100/100
15%
Value11.3 s
19/100
10%
366 ms
173 ms
171 ms
302 ms
180 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 79% of them (33 requests) were addressed to the original Aai.org, 14% (6 requests) were made to Google.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (500 ms) belongs to the original domain Aai.org.
Page size can be reduced by 169.2 kB (22%)
780.1 kB
610.9 kB
In fact, the total size of Aai.org main page is 780.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. 45% of websites need less resources to load. Images take 595.4 kB which makes up the majority of the site volume.
Potential reduce by 68.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 47.6 kB, which is 63% 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 68.3 kB or 90% of the original size.
Potential reduce by 67.2 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. Obviously, Aai needs image optimization as it can save up to 67.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 18.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 18.4 kB or 20% of the original size.
Potential reduce by 15.3 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. Aai.org needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 85% of the original size.
Number of requests can be reduced by 8 (20%)
41
33
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
aai.org
366 ms
AAI_main.css
173 ms
minimalist.css
171 ms
SpryMenuBar.js
302 ms
banner_menu.css
180 ms
jsapi
18 ms
ga.js
35 ms
JI_Ribbon.jpg
205 ms
AAI_Background_color.jpg
200 ms
AAI_banner.jpg
305 ms
current.gif
200 ms
AAI-NL_current.jpg
240 ms
Advertise_redux.jpg
203 ms
faseb_new_logo.jpg
200 ms
IUIS_Logo.gif
200 ms
TheJIMobile.gif
200 ms
social-media---twitter-AAI.png
239 ms
social-media---twiiter-JI.png
246 ms
social-media---facebook.png
248 ms
social-media---linkedin.png
254 ms
Littman_D_2015_sh.jpg
279 ms
2016_Awardees_HP_button_cap.jpg
343 ms
IMM_2016_site_banner_news_board_350x59.jpg
305 ms
ici2016-top.jpg
308 ms
AAI-News-Burgandy.gif
311 ms
Glimcher_75x94@72_sh.png
320 ms
CAB_banner_340x41_sh.jpg
360 ms
In_Memoriam_graphic_cropped_sh_sm.jpg
365 ms
Member-Services-Burgandy.gif
368 ms
CIIF_TfT_2015_HP_banner_sh.jpg
368 ms
AAI-100_banner.jpg
432 ms
CalendarIcon.gif
398 ms
Members-News.jpg
500 ms
59 ms
__utm.gif
61 ms
default+en.css
5 ms
default+en.I.js
9 ms
SpryMenuBarRightHover.gif
367 ms
async-ads.js
58 ms
small-logo.png
27 ms
clear.gif
13 ms
SpryMenuBarDownHover.gif
194 ms
aai.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
aai.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
aai.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aai.org 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 Aai.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.
aai.org
Open Graph description is not detected on the main page of Aai. 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: