5 sec in total
158 ms
4.5 sec
339 ms
Welcome to runwithart.kintera.org homepage info - get ready to check Runwithart Kintera best content for United States right away, or after learning these important things about runwithart.kintera.org
Visit runwithart.kintera.orgWe analyzed Runwithart.kintera.org page load time and found that the first response time was 158 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
runwithart.kintera.org performance score
158 ms
411 ms
346 ms
282 ms
282 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 24% of them (20 requests) were addressed to the original Runwithart.kintera.org, 27% (22 requests) were made to Static.xx.fbcdn.net and 9% (7 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Facebook.com.
Page size can be reduced by 1.0 MB (79%)
1.3 MB
273.7 kB
In fact, the total size of Runwithart.kintera.org main page is 1.3 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. 55% of websites need less resources to load. Javascripts take 813.2 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.3 kB or 77% of the original size.
Potential reduce by 191.3 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, Runwithart Kintera needs image optimization as it can save up to 191.3 kB or 70% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 649.0 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 649.0 kB or 80% of the original size.
Potential reduce by 124.6 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. Runwithart.kintera.org needs all CSS files to be minified and compressed as it can save up to 124.6 kB or 88% of the original size.
Number of requests can be reduced by 43 (58%)
74
31
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runwithart Kintera. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
runwithart.kintera.org
158 ms
default.asp
411 ms
jquery-1.7.2.js
346 ms
plugins.js
282 ms
custom.js
282 ms
faf.css
140 ms
EssentialStyles.css
209 ms
INC_jsTools.js
143 ms
event.asp
171 ms
ga.js
109 ms
1383066_534307099980684_1902800781_n.jpg
250 ms
5k_logo_for_website_reduced.jpg
250 ms
kath_picture_we_can_use_-_copy.jpg
248 ms
healthsouth_logo_-_copy.jpg
256 ms
help_Button.gif
161 ms
emailFriend.gif
145 ms
FriendsAskingFriends.png
145 ms
kintera_149x36.gif
145 ms
pattern-2_texturedGradient.png
218 ms
janrain.asp
217 ms
loadingIcon2.gif
118 ms
controls.png
110 ms
__utm.gif
69 ms
all.js
283 ms
buttons.js
325 ms
engage.js
15 ms
google_s.png
289 ms
yahoo_s.png
233 ms
facebook_s.png
232 ms
twitter_s.png
233 ms
linkedin_s.png
75 ms
login
11 ms
providers.css
18 ms
40 ms
xd_arbiter.php
235 ms
xd_arbiter.php
440 ms
getAllAppDefault.esi
239 ms
comments.php
1727 ms
getSegment.php
162 ms
checkOAuth.esi
62 ms
t.dhj
60 ms
t.dhj
36 ms
cm
26 ms
s-3271.xgi
13 ms
hbpix
30 ms
10 ms
xrefid.xgi
9 ms
11 ms
pixel
43 ms
pixel
21 ms
2981
26 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
18 ms
buttons.ab966a004186897711de4a5ed256c924.css
18 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
11 ms
st.1188278743c14064d5e8ae56c8ada29c.js
14 ms
facebook_32.png
19 ms
twitter_32.png
20 ms
email_32.png
21 ms
sharethis_32.png
19 ms
hDvwL1_H7g-.css
286 ms
56WNbrUYLbL.css
360 ms
K4L53ZPHpV7.css
430 ms
xxJgcoj8mOR.css
559 ms
q68gy-v_YMF.js
558 ms
FJmpeSpHpjS.js
623 ms
0wM5s1Khldu.js
490 ms
LTv6ZK-5zxz.js
730 ms
1FCa-btixu2.js
607 ms
Oagsvfb4VWi.js
642 ms
FyxLoiww5bU.js
645 ms
HaMjR2eXz4B.js
691 ms
WN2wSsLOuKy.js
695 ms
HgJbVwzBr8E.js
689 ms
Q4A0UyjU8W2.js
694 ms
1bNoFZUdlYZ.js
696 ms
odA9sNLrE86.jpg
69 ms
fav.png
16 ms
wL6VQj7Ab77.png
88 ms
K00K-UgnsKu.png
87 ms
OZFAYTv-ZUg.js
74 ms
I6-MnjEovm5.js
73 ms
pQrUxxo5oQp.js
73 ms
runwithart.kintera.org SEO score
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runwithart.kintera.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 Runwithart.kintera.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.
runwithart.kintera.org
Open Graph description is not detected on the main page of Runwithart Kintera. 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: