5.9 sec in total
728 ms
4.8 sec
348 ms
Click here to check amazing Forced Green content. Otherwise, check out these important facts you probably never knew about forcedgreen.com
Living a natural life in an industrial world
Visit forcedgreen.comWe analyzed Forcedgreen.com page load time and found that the first response time was 728 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster. This domain responded with an error, which can significantly jeopardize Forcedgreen.com rating and web reputation
forcedgreen.com performance score
728 ms
117 ms
157 ms
159 ms
214 ms
Our browser made a total of 191 requests to load all elements on the main page. We found that 18% of them (34 requests) were addressed to the original Forcedgreen.com, 9% (17 requests) were made to Ce.lijit.com and 8% (16 requests) were made to Dsum.casalemedia.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Fuelmyblog.com.
Page size can be reduced by 1.1 MB (58%)
1.9 MB
803.9 kB
In fact, the total size of Forcedgreen.com main page is 1.9 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. 60% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 68.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 68.2 kB or 73% of the original size.
Potential reduce by 26.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. Forced Green images are well optimized though.
Potential reduce by 969.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 969.1 kB or 66% of the original size.
Potential reduce by 34.9 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. Forcedgreen.com needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 85% of the original size.
Number of requests can be reduced by 117 (72%)
163
46
The browser has sent 163 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forced Green. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.forcedgreen.com
728 ms
style.css
117 ms
script.js
157 ms
styles.css
159 ms
output.css
214 ms
styles.css
153 ms
pinterest-pin-it-button.css
158 ms
commentluv.css
216 ms
jquery.js
346 ms
commentluv.js
236 ms
gpo_plusone.css
231 ms
blog_wijits
82 ms
txwidget1.2.js
209 ms
srad.js
44 ms
signup_widget.min.js
10 ms
roadblock_widget.min.js
203 ms
28625X865768.skimlinks.js
113 ms
addthis_widget.js
13 ms
plusone.js
61 ms
jquery.form.min.js
255 ms
scripts.js
259 ms
pin-it-button-user-selects-image.js
261 ms
gpt.js
6 ms
pubads_impl_82.js
10 ms
container.html
29 ms
cs-gr-120x60.gif
130 ms
banner-31.gif
30 ms
BP_badge_125x140.jpg
104 ms
blogcatalog7.png
104 ms
20070628150946903_4511.png
3146 ms
PinExt.png
25 ms
btn_donate_LG.gif
74 ms
Page-BgTexture.png
166 ms
Page-BgGradient.png
167 ms
Page-BgGlare.png
227 ms
item-center.png
103 ms
nav.png
102 ms
Header.jpg
221 ms
BlockHeader.png
168 ms
environmentgreenguide-small.jpg
176 ms
Block-s.png
233 ms
Block-h.png
232 ms
Block-v.png
233 ms
happy.jpg
405 ms
xmas.jpg
303 ms
rssfeed-large.gif
294 ms
marijuanalobby.org.125x125.png
328 ms
pixel.gif
70 ms
uat_34503.js
289 ms
blogcatalog7.png
184 ms
0.png
130 ms
adserv_34503.js
298 ms
generic
7 ms
r.js
21 ms
technorati-tech_tag.js
23 ms
generic
5 ms
bounce
16 ms
search.js
36 ms
usermatch
24 ms
user_sync.html
23 ms
search.js
14 ms
usermatch
52 ms
showad.js
34 ms
lite.beacon.min.js
51 ms
ip.php
98 ms
PugMaster
37 ms
pixel
119 ms
usersync
26 ms
1
56 ms
VulRtsAoJVsAALKfcjQAAAE0%26632
108 ms
cm
39 ms
casale
13 ms
pixel
56 ms
crum
65 ms
42 ms
rum
70 ms
pm_match
56 ms
pixel
80 ms
Pug
83 ms
usersync.aspx
78 ms
tap.php
142 ms
pixel
51 ms
wijitTrack.gif
82 ms
rum
118 ms
Pug
58 ms
Pug
60 ms
Pug
61 ms
pixel
61 ms
crum
48 ms
pixel
63 ms
Pug
87 ms
5969
81 ms
crum
77 ms
ad
98 ms
Pug
67 ms
rum
60 ms
beacon
69 ms
101 ms
Pug
86 ms
364698.gif
49 ms
lj_match
33 ms
generic
47 ms
js
73 ms
pixel
45 ms
B5963203;sz=160x600;ord=2186788848
98 ms
5447
35 ms
merge
33 ms
merge
22 ms
400966.gif
25 ms
merge
28 ms
merge
27 ms
merge
52 ms
rand=28713
49 ms
merge
48 ms
merge
41 ms
sync
35 ms
usermatch
45 ms
usermatch
85 ms
user_sync.html
30 ms
user_sync.html
43 ms
getuuid
28 ms
merge
27 ms
img
73 ms
ad
81 ms
merge
47 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
94 ms
dfa7banner_flash_html_inpage_rendering_lib_200_103.js
124 ms
lidar.js
44 ms
gr
57 ms
blank.html
53 ms
merge
45 ms
merge
51 ms
merge
111 ms
merge
44 ms
merge
50 ms
merge
83 ms
rum
115 ms
usersync.aspx
94 ms
GenericUserSync.ashx
99 ms
140 ms
merge
76 ms
crum
89 ms
crum
80 ms
pixel
100 ms
rum
423 ms
crum
80 ms
pixel.htm
111 ms
cs
75 ms
iframe
82 ms
rum
81 ms
pm_match
49 ms
Sheet-s.png
371 ms
Sheet-h.png
383 ms
Sheet-v.png
369 ms
crum
63 ms
rum
64 ms
rum
65 ms
crum
343 ms
m
344 ms
img
125 ms
ad
309 ms
crum
66 ms
ddc.htm
96 ms
img
268 ms
crum
72 ms
rum
210 ms
px.gif
203 ms
195 ms
px.gif
194 ms
cb=gapi.loaded_0
170 ms
59 ms
boost
54 ms
300lo.json
123 ms
item-separator.png
110 ms
closeit.png
208 ms
merge
34 ms
crum
33 ms
crum
41 ms
sh.07f0d9bf220d07a763adad1e.html
80 ms
82 ms
jquery.min.js
165 ms
link
143 ms
67 ms
pixel
82 ms
p.skimresources.com
34 ms
track.php
61 ms
pixel
51 ms
img
39 ms
adc_ftp_stuntman_160x600.html
53 ms
activity;src=2276943;met=1;v=1;pid=72927228;aid=252208339;ko=0;cid=63967344;rid=63847444;rv=1;×tamp=1458131384567;eid1=871060;ecn1=1;etm1=0;
51 ms
runtime.js
101 ms
forcedgreen.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forcedgreen.com 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 Forcedgreen.com 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.
forcedgreen.com
Open Graph description is not detected on the main page of Forced Green. 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: