2.5 sec in total
118 ms
2 sec
327 ms
Welcome to smartrecoveryforum.org homepage info - get ready to check Smartrecoveryforum best content right away, or after learning these important things about smartrecoveryforum.org
SMART Recovery discussion forum
Visit smartrecoveryforum.orgWe analyzed Smartrecoveryforum.org page load time and found that the first response time was 118 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
smartrecoveryforum.org performance score
118 ms
194 ms
336 ms
25 ms
137 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Smartrecoveryforum.org, 78% (65 requests) were made to Smartrecovery.org and 5% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Smartrecovery.org.
Page size can be reduced by 935.2 kB (53%)
1.8 MB
828.0 kB
In fact, the total size of Smartrecoveryforum.org main page is 1.8 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. Javascripts take 775.2 kB which makes up the majority of the site volume.
Potential reduce by 76.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 13.9 kB, which is 15% 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 76.0 kB or 84% of the original size.
Potential reduce by 3.5 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. Smartrecoveryforum images are well optimized though.
Potential reduce by 475.9 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 475.9 kB or 61% of the original size.
Potential reduce by 379.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. Smartrecoveryforum.org needs all CSS files to be minified and compressed as it can save up to 379.8 kB or 82% of the original size.
Number of requests can be reduced by 57 (73%)
78
21
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smartrecoveryforum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
smartrecoveryforum.org
118 ms
194 ms
336 ms
yuiloader-dom-event.js
25 ms
vbulletin-core.js
137 ms
main-rollup.css
165 ms
detect.js
87 ms
vbulletin_read_marker.js
89 ms
forumhome-rollup.css
88 ms
additional.css
106 ms
spcjs.php
127 ms
jquery.min.js
28 ms
jquery.modal.js
120 ms
jquery-ui.js
35 ms
vbulletin_md5.js
120 ms
connection-min.js
4 ms
forumhome-rollup.css
65 ms
sidebar.css
78 ms
widgets.css
78 ms
tagcloud.css
83 ms
animation-min.js
4 ms
vbulletin-sidebar.js
97 ms
spc.php
59 ms
fl.js
32 ms
ga.js
49 ms
header-bg.png
51 ms
logo.png
90 ms
navbar.png
56 ms
arrow.png
54 ms
search.png
54 ms
smart-reg-image.png
87 ms
navbit-home.png
47 ms
newbtn_middle.png
64 ms
fourpoints.png
63 ms
collapse_40b.png
64 ms
forum_new-48.png
70 ms
grey-up.png
85 ms
icon1.png
85 ms
lastpost-right.png
88 ms
subforum_old-48.png
93 ms
gradient-greytowhite.png
97 ms
forum_stats.png
107 ms
legend.png
116 ms
forum_new-16.png
116 ms
forum_old-16.png
118 ms
category-16.png
123 ms
forum_link-16.png
126 ms
smart-recovery-become-a-volunteer.jpg
118 ms
lg.php
152 ms
tab-collapsed.png
126 ms
widget-comment.png
142 ms
image.php
281 ms
image.php
1165 ms
006.gif
279 ms
unknown.gif
279 ms
__utm.gif
20 ms
16-12-20-YearEndDonationButton-MB.png
260 ms
lg.php
261 ms
smart-recovery-facilitator-training.png
258 ms
lg.php
259 ms
89cIz3aAN0I
88 ms
top-highlight.png
243 ms
gradient-black-down.png
244 ms
bottom-shadow.png
245 ms
16-12-27-checkup-choices.png
236 ms
lg.php
237 ms
Ft-Lauderdale-community-forum-ad.png
236 ms
lg.php
237 ms
bookstore-graphic-280.png
236 ms
lg.php
258 ms
volunteer-thin.png
257 ms
lg.php
259 ms
tools-thin.png
256 ms
lg.php
250 ms
www-player-vflMqr8uC.css
5 ms
www-embed-player.js
18 ms
base.js
27 ms
id
106 ms
T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js
107 ms
ad_status.js
105 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
82 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
86 ms
logo_ringo-vflOpz8ZI.png
82 ms
smartrecoveryforum.org SEO score
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smartrecoveryforum.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Smartrecoveryforum.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
smartrecoveryforum.org
Open Graph description is not detected on the main page of Smartrecoveryforum. 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: