2 sec in total
59 ms
1.6 sec
332 ms
Welcome to 12step.org homepage info - get ready to check 12Step best content for United States right away, or after learning these important things about 12step.org
12Step.org has quality information and tools for a 12 step program of recovery
Visit 12step.orgWe analyzed 12step.org page load time and found that the first response time was 59 ms and then it took 1.9 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.
12step.org performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value10.8 s
0/100
25%
Value6.6 s
38/100
10%
Value1,120 ms
23/100
30%
Value0.352
31/100
15%
Value19.2 s
2/100
10%
59 ms
19 ms
20 ms
22 ms
24 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 75% of them (85 requests) were addressed to the original 12step.org, 4% (5 requests) were made to Pagead2.googlesyndication.com and 4% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (656 ms) belongs to the original domain 12step.org.
Page size can be reduced by 1.2 MB (57%)
2.2 MB
926.0 kB
In fact, the total size of 12step.org main page is 2.2 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. 75% 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 137.2 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 51.3 kB, which is 32% 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 137.2 kB or 85% of the original size.
Potential reduce by 24.4 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. 12Step images are well optimized though.
Potential reduce by 749.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 749.2 kB or 65% of the original size.
Potential reduce by 331.1 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. 12step.org needs all CSS files to be minified and compressed as it can save up to 331.1 kB or 83% of the original size.
Number of requests can be reduced by 58 (54%)
108
50
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 12Step. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
12step.org
59 ms
roksocialbuttons.css
19 ms
rokbox.css
20 ms
menu-3d55a85845b3362e4db5a0f5decbd1ba.css
22 ms
grid-responsive.css
24 ms
bootstrap.css
38 ms
master-b2b913a529709208a128d78a658e46be.css
47 ms
mediaqueries.css
656 ms
rtl.css
28 ms
thirdparty-k2.css
33 ms
tabs.css
30 ms
strips.css
44 ms
font-awesome.min.css
11 ms
jquery-1.7.1.min.js
13 ms
jquery.easing.min.js
14 ms
jquery-noconflict.js
43 ms
addthis_widget.js
14 ms
caption.js
43 ms
mootools-core.js
69 ms
core.js
55 ms
mootools-more.js
85 ms
rokbox.js
61 ms
gantry-totop.js
57 ms
browser-engines.js
55 ms
rokmediaqueries.js
58 ms
rokmediaqueries.js
64 ms
responsive.js
65 ms
mootools-mobile.js
69 ms
rokmediaqueries.js
73 ms
roksprocket.js
74 ms
tabs.js
74 ms
moofx.js
78 ms
roksprocket.request.js
85 ms
strips.js
84 ms
strips-speeds.js
83 ms
bootstrap.min.js
88 ms
jquery.js
102 ms
amazingcarousel.js
100 ms
initcarousel-1.css
90 ms
initcarousel-1.js
92 ms
adsbygoogle.js
12 ms
css
24 ms
none.png
79 ms
logo.png
52 ms
icon-monitor.png
53 ms
shield.png
51 ms
history_16.png
54 ms
speech_16.png
53 ms
book_open.png
55 ms
networking_16.png
55 ms
page_white_stack.png
55 ms
book.png
56 ms
Biblex16.png
56 ms
eswordx16b.png
57 ms
icon-docs.png
58 ms
icon-write.png
59 ms
homepage-step-1c.png
59 ms
homepage-step-2c.png
59 ms
homepage-step-3c.png
60 ms
homepage-step-4c.png
60 ms
homepage-step-5c.png
61 ms
homepage-step-6c.png
62 ms
homepage-step-7c.png
61 ms
homepage-step-8c.png
62 ms
homepage-step-9c.png
63 ms
homepage-step-10c.png
64 ms
homepage-step-11c.png
64 ms
homepage-step-12c.png
65 ms
homework_256.png
96 ms
book_newcomerx256.png
65 ms
frames_256.png
94 ms
fellowshipsb.png
91 ms
calendar_month_256.png
96 ms
Big_book_2nd_editionx256c.png
92 ms
help_256.png
98 ms
organigram_256.png
94 ms
img3.png
94 ms
jrlogox128-opt.png
98 ms
j1logox128-opt.png
55 ms
jflogox128-opt.png
56 ms
Ubuntu-L-webfont.woff.html
37 ms
fontawesome-webfont.woff
36 ms
fontawesome-webfont.woff_v=3.2.1.html
76 ms
Ubuntu-R-webfont.woff.html
37 ms
ca-pub-1769113891221306.js
97 ms
zrt_lookup.html
278 ms
show_ads_impl.js
91 ms
ads
228 ms
Ubuntu-M-webfont.woff.html
144 ms
osd.js
140 ms
ads
222 ms
analytics.js
128 ms
300lo.json
96 ms
12step.org
72 ms
lightbox-next.png
64 ms
lightbox-prev.png
62 ms
lightbox-close.png
63 ms
bottomshadow-110-100-5.png
62 ms
arrows-48-48-1.png
63 ms
bullet-16-16-2.png
75 ms
ads
164 ms
sh.7c7179124ea24ac6ba46caac.html
68 ms
collect
74 ms
m_js_controller.js
60 ms
abg.js
74 ms
favicon
123 ms
favicon
77 ms
googlelogo_color_112x36dp.png
102 ms
nessie_icon_thin_arrow_big_white.png
57 ms
s
48 ms
x_button_blue2.png
27 ms
favicon
120 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
9 ms
12step.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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
12step.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
12step.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 12step.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 12step.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.
12step.org
Open Graph description is not detected on the main page of 12Step. 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: