1.4 sec in total
86 ms
1.2 sec
160 ms
Click here to check amazing Aa content for United States. Otherwise, check out these important facts you probably never knew about aa.org
Have a problem with alcohol? There is a solution. A.A. has a simple program that works. It’s based on one alcoholic helping another.
Visit aa.orgWe analyzed Aa.org page load time and found that the first response time was 86 ms and then it took 1.3 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.
aa.org performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value9.7 s
0/100
25%
Value7.1 s
31/100
10%
Value810 ms
36/100
30%
Value0.115
86/100
15%
Value11.1 s
20/100
10%
86 ms
134 ms
28 ms
71 ms
111 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 86% of them (55 requests) were addressed to the original Aa.org, 8% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (370 ms) belongs to the original domain Aa.org.
Page size can be reduced by 583.0 kB (67%)
864.3 kB
281.2 kB
In fact, the total size of Aa.org main page is 864.3 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. 35% of websites need less resources to load. Javascripts take 391.8 kB which makes up the majority of the site volume.
Potential reduce by 32.0 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.9 kB, which is 29% 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 32.0 kB or 86% of the original size.
Potential reduce by 93.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. Obviously, Aa needs image optimization as it can save up to 93.9 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 338.1 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 338.1 kB or 86% of the original size.
Potential reduce by 119.0 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. Aa.org needs all CSS files to be minified and compressed as it can save up to 119.0 kB or 86% of the original size.
Number of requests can be reduced by 27 (47%)
57
30
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
aa.org
86 ms
www.aa.org
134 ms
css
28 ms
jqmaps.css
71 ms
video-js.css
111 ms
jsDatePick_ltr.css
73 ms
jquery-ui.css
21 ms
tree.css
75 ms
icon.css
77 ms
jquery.fancybox.css
77 ms
main.css
179 ms
styles
124 ms
jquery.min.js
35 ms
jquery-ui.min.js
57 ms
jquery.jcarousel.js
223 ms
easyloader.js
110 ms
jquery.fancybox.js
225 ms
jquery.flyout.1.1.js
144 ms
video.dev.js
370 ms
readmore.js
157 ms
jsDatePick.jquery.full.1.3.js
228 ms
main.js
338 ms
fontsize
229 ms
angelfish.js
227 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
39 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
60 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
65 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
67 ms
4cKlrioa77J2iqTqBgkRWg.ttf
71 ms
jquery.parser.js
50 ms
aa_background_mountain.jpg
189 ms
header-bar-bk.png
38 ms
logo-en_US.png
40 ms
settings-btn2.png
42 ms
back.jpg
79 ms
night-background.jpg
78 ms
en_web_banners_small.jpg
74 ms
printer.png
77 ms
cart.png
80 ms
contributions-self-support-icon.png
111 ms
people.png
152 ms
search-box-bk.png
116 ms
plus-icon.gif
118 ms
find-aa-icon.gif
118 ms
go-btn.gif
150 ms
dropdown-btn.gif
155 ms
info-icon.gif
159 ms
home-box-link-icon.png
153 ms
home-carousel-prev.gif
188 ms
home-carousel-next.gif
189 ms
ebooks-icon.png
190 ms
aa-twelve-steps-big-book.png
192 ms
aa-75th-anniversary.png
193 ms
literature-icon.png
221 ms
cart.png
224 ms
grapevine-icon.png
225 ms
contributions-self-support-icon.png
225 ms
archives-icon.png
227 ms
press-media-icon.png
230 ms
videos-audios-icon.png
256 ms
calendar.png
260 ms
newsletters.png
258 ms
footer-bar-bk.png
261 ms
printer.css
39 ms
aa.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.
aa.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
aa.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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aa.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 Aa.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.
aa.org
Open Graph description is not detected on the main page of Aa. 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: