Tools & Wizards About Us
saintsandheroes.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

saintsandheroes.com

Page Load Speed

10.5 sec in total

First Response

1.7 sec

Resources Loaded

8.4 sec

Page Rendered

450 ms

saintsandheroes.com screenshot

About Website

Click here to check amazing Saintsandheroes content. Otherwise, check out these important facts you probably never knew about saintsandheroes.com

Tributes to all our veterans and heroes, honoring veterans and our soldiers for all they do. With stories and poems about veterans tributes showing courageous people helping others. Nicely illustrated...

Visit saintsandheroes.com

Key Findings

We analyzed Saintsandheroes.com page load time and found that the first response time was 1.7 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

saintsandheroes.com performance score

0

Network Requests Diagram

saintsandheroes.com

1696 ms

all.js

122 ms

adsbygoogle.js

10 ms

saintsandheroes.gif

3174 ms

addthis_widget.js

69 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 12% of them (13 requests) were addressed to the original Saintsandheroes.com, 23% (26 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Reddit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 900.9 kB (65%)

Content Size

1.4 MB

After Optimization

489.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Saintsandheroes.com main page is 1.4 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 169.6 kB

  • Original 224.8 kB
  • After minification 222.7 kB
  • After compression 55.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. 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 169.6 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 2.1 kB

  • Original 72.6 kB
  • After minification 70.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. Saintsandheroes images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 729.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 363.5 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 729.2 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (56%)

Requests Now

108

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saintsandheroes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

saintsandheroes.com

saintsandheroes.com

1696 ms

all.js

all.js

122 ms

adsbygoogle.js

adsbygoogle.js

10 ms

saintsandheroes.gif

saintsandheroes.gif

3174 ms

addthis_widget.js

addthis_widget.js

69 ms

foldingFLAG.gif

foldingFLAG.gif

3212 ms

welrainbow.jpg

welrainbow.jpg

3179 ms

never.jpg

never.jpg

3199 ms

candles-004.gif

candles-004.gif

3186 ms

flag1.gif

flag1.gif

3183 ms

blstarsC.gif

blstarsC.gif

116 ms

ca-pub-1902572504242226.js

ca-pub-1902572504242226.js

32 ms

zrt_lookup.html

zrt_lookup.html

93 ms

show_ads_impl.js

show_ads_impl.js

127 ms

addthis_widget.js

addthis_widget.js

161 ms

brand

brand

15 ms

candleburningwht.gif

candleburningwht.gif

3178 ms

DDDEER80.gif

DDDEER80.gif

3187 ms

prod_411_20819.gif

prod_411_20819.gif

3194 ms

deerlake.gif

deerlake.gif

3194 ms

brand

brand

100 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

127 ms

225 ms

221 ms

ads

ads

332 ms

300lo.json

300lo.json

171 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

169 ms

widgets.js

widgets.js

118 ms

plusone.js

plusone.js

145 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

92 ms

xd_arbiter.php

xd_arbiter.php

164 ms

xd_arbiter.php

xd_arbiter.php

235 ms

osd.js

osd.js

115 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

75 ms

comments.php

comments.php

222 ms

ads

ads

214 ms

ads

ads

221 ms

ads

ads

199 ms

shares.json

shares.json

49 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

46 ms

like.php

like.php

101 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

46 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

45 ms

fastbutton

fastbutton

121 ms

xd_arbiter.php

xd_arbiter.php

68 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

12 ms

postmessageRelay

postmessageRelay

58 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

189 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

183 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

86 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

33 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

32 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

158 ms

VJx-L5qLy3d.css

VJx-L5qLy3d.css

151 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

154 ms

yBwS6rJyogl.css

yBwS6rJyogl.css

153 ms

ZeuPykSxSED.css

ZeuPykSxSED.css

179 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

210 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

223 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

170 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

240 ms

1FCa-btixu2.js

1FCa-btixu2.js

169 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

209 ms

FyxLoiww5bU.js

FyxLoiww5bU.js

235 ms

HaMjR2eXz4B.js

HaMjR2eXz4B.js

236 ms

WN2wSsLOuKy.js

WN2wSsLOuKy.js

236 ms

HgJbVwzBr8E.js

HgJbVwzBr8E.js

236 ms

Q4A0UyjU8W2.js

Q4A0UyjU8W2.js

237 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

237 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

94 ms

rpc:shindig_random.js

rpc:shindig_random.js

51 ms

m_js_controller.js

m_js_controller.js

68 ms

abg.js

abg.js

97 ms

0_z1Bt97DI.jpg

0_z1Bt97DI.jpg

212 ms

a.gif

a.gif

113 ms

bcs0

bcs0

116 ms

creative_add_on.js

creative_add_on.js

208 ms

jot

jot

152 ms

favicon

favicon

71 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

70 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

51 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

34 ms

s

s

29 ms

x_button_blue2.png

x_button_blue2.png

27 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

8 ms

surly.js

surly.js

205 ms

like.php

like.php

176 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

53 ms

comments.php

comments.php

177 ms

ba.html

ba.html

10 ms

4.gif

4.gif

28 ms

2532.js

2532.js

20 ms

box_19_top-right.png

box_19_top-right.png

119 ms

ci.png

ci.png

109 ms

odA9sNLrE86.jpg

odA9sNLrE86.jpg

27 ms

10403154_1015056621838694_5632653755201299640_n.jpg

10403154_1015056621838694_5632653755201299640_n.jpg

25 ms

fav.png

fav.png

7 ms

73931_106978206038129_7391961_n.jpg

73931_106978206038129_7391961_n.jpg

37 ms

12799088_1249009605127631_3291378588705548304_n.jpg

12799088_1249009605127631_3291378588705548304_n.jpg

54 ms

12742046_10209143073321107_2426916906226873968_n.jpg

12742046_10209143073321107_2426916906226873968_n.jpg

106 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

20 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

18 ms

OZFAYTv-ZUg.js

OZFAYTv-ZUg.js

19 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

24 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

23 ms

fql

fql

50 ms

count.json

count.json

31 ms

info.json

info.json

5272 ms

shares.json

shares.json

45 ms

views2.json

views2.json

138 ms

share

share

37 ms

candleburninghgclr.gif

candleburninghgclr.gif

40 ms

activeview

activeview

14 ms

SEO Factors

saintsandheroes.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saintsandheroes.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Saintsandheroes.com 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.

Social Sharing Optimization

saintsandheroes.com

Open Graph description is not detected on the main page of Saintsandheroes. 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: