Tools & Wizards About Us
walkforpkd.kintera.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

walkforpkd.kintera.org

Home - Kintera.com

Page Load Speed

3.2 sec in total

First Response

151 ms

Resources Loaded

2.8 sec

Page Rendered

230 ms

walkforpkd.kintera.org screenshot

About Website

Welcome to walkforpkd.kintera.org homepage info - get ready to check Walkforpkd Kintera best content for United States right away, or after learning these important things about walkforpkd.kintera.org

The Walk for PKD is the PKD Foundation's signature fundraising event. Join us as we Unite to Fight PKD!

Visit walkforpkd.kintera.org

Key Findings

We analyzed Walkforpkd.kintera.org page load time and found that the first response time was 151 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

walkforpkd.kintera.org performance score

0

Network Requests Diagram

walkforpkd.kintera.org

151 ms

default.asp

199 ms

jquery-1.7.2.js

309 ms

plugins.js

277 ms

custom.js

209 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 21% of them (20 requests) were addressed to the original Walkforpkd.kintera.org, 26% (25 requests) were made to Static.xx.fbcdn.net and 9% (9 requests) were made to Pkdcure.org. The less responsive or slowest element that took the longest time to load (772 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (74%)

Content Size

1.8 MB

After Optimization

463.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Walkforpkd.kintera.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. 60% of websites need less resources to load. Javascripts take 998.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 38.8 kB

  • Original 50.6 kB
  • After minification 47.2 kB
  • After compression 11.8 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 38.8 kB or 77% of the original size.

Image Optimization

-52%

Potential reduce by 194.9 kB

  • Original 371.6 kB
  • After minification 176.7 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, Walkforpkd Kintera needs image optimization as it can save up to 194.9 kB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 781.6 kB

  • Original 998.8 kB
  • After minification 777.8 kB
  • After compression 217.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 781.6 kB or 78% of the original size.

CSS Optimization

-85%

Potential reduce by 326.7 kB

  • Original 384.5 kB
  • After minification 379.8 kB
  • After compression 57.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. Walkforpkd.kintera.org needs all CSS files to be minified and compressed as it can save up to 326.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Walkforpkd 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 34 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

walkforpkd.kintera.org

walkforpkd.kintera.org

151 ms

default.asp

default.asp

199 ms

jquery-1.7.2.js

jquery-1.7.2.js

309 ms

plugins.js

plugins.js

277 ms

custom.js

custom.js

209 ms

faf.css

faf.css

140 ms

EssentialStyles.css

EssentialStyles.css

209 ms

document.doc

document.doc

196 ms

INC_jsTools.js

INC_jsTools.js

141 ms

event.asp

event.asp

127 ms

walkheaderlogo.jpg

walkheaderlogo.jpg

181 ms

view.image

view.image

189 ms

walkheadertagline.jpg

walkheadertagline.jpg

242 ms

kcphoto.png

kcphoto.png

231 ms

help_Button.gif

help_Button.gif

71 ms

FriendsAskingFriends.png

FriendsAskingFriends.png

71 ms

kintera_149x36.gif

kintera_149x36.gif

72 ms

view.image

view.image

212 ms

view.image

view.image

221 ms

view.image

view.image

218 ms

view.image

view.image

224 ms

view.image

view.image

220 ms

view.image

view.image

219 ms

view.image

view.image

238 ms

pattern-4_whiteGradient.png

pattern-4_whiteGradient.png

83 ms

janrain.asp

janrain.asp

166 ms

loadingIcon2.gif

loadingIcon2.gif

45 ms

controls.png

controls.png

40 ms

all.js

all.js

159 ms

buttons.js

buttons.js

70 ms

engage.js

engage.js

7 ms

google_s.png

google_s.png

330 ms

yahoo_s.png

yahoo_s.png

215 ms

facebook_s.png

facebook_s.png

214 ms

twitter_s.png

twitter_s.png

215 ms

linkedin_s.png

linkedin_s.png

75 ms

login

login

10 ms

HOEtH029nhs

HOEtH029nhs

134 ms

providers.css

providers.css

16 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

80 ms

www-embed-player.js

www-embed-player.js

117 ms

160 ms

xd_arbiter.php

xd_arbiter.php

163 ms

xd_arbiter.php

xd_arbiter.php

287 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

48 ms

ad_status.js

ad_status.js

44 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

65 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

65 ms

getAllAppDefault.esi

getAllAppDefault.esi

105 ms

comments.php

comments.php

772 ms

getSegment.php

getSegment.php

172 ms

checkOAuth.esi

checkOAuth.esi

6 ms

t.dhj

t.dhj

6 ms

t.dhj

t.dhj

10 ms

cm

cm

22 ms

19 ms

s-3271.xgi

s-3271.xgi

6 ms

hbpix

hbpix

41 ms

8 ms

xrefid.xgi

xrefid.xgi

9 ms

pixel

pixel

21 ms

pixel

pixel

20 ms

2981

2981

31 ms

jTuqQ-OPDr6.css

jTuqQ-OPDr6.css

174 ms

n370yiaI2G6.css

n370yiaI2G6.css

216 ms

yShV8zgCmg4.css

yShV8zgCmg4.css

258 ms

cCIltMJutxu.css

cCIltMJutxu.css

331 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

384 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

384 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

295 ms

rFmE1g6Dkoz.js

rFmE1g6Dkoz.js

434 ms

7cm7D75Y0Sf.js

7cm7D75Y0Sf.js

347 ms

DKRU1bYTkTw.js

DKRU1bYTkTw.js

408 ms

LU4a_W5X-JG.js

LU4a_W5X-JG.js

425 ms

sj-JwAJi4AH.js

sj-JwAJi4AH.js

410 ms

AunibtBOmSk.js

AunibtBOmSk.js

428 ms

Nvkj5df-gdk.js

Nvkj5df-gdk.js

430 ms

336JejShbZp.js

336JejShbZp.js

429 ms

Q4A0UyjU8W2.js

Q4A0UyjU8W2.js

431 ms

TTCre3391I0.js

TTCre3391I0.js

469 ms

DnwTulctFaE.js

DnwTulctFaE.js

470 ms

index.2d85e55d89f85ae69e4f2ca5ab9438b7.html

index.2d85e55d89f85ae69e4f2ca5ab9438b7.html

17 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

16 ms

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

34 ms

st.1188278743c14064d5e8ae56c8ada29c.js

st.1188278743c14064d5e8ae56c8ada29c.js

38 ms

facebook_32.png

facebook_32.png

18 ms

twitter_32.png

twitter_32.png

20 ms

email_32.png

email_32.png

23 ms

sharethis_32.png

sharethis_32.png

21 ms

odA9sNLrE86.jpg

odA9sNLrE86.jpg

48 ms

fav.png

fav.png

23 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

40 ms

a-ZN6WoEOje.png

a-ZN6WoEOje.png

42 ms

W0OV23mIOyO.js

W0OV23mIOyO.js

41 ms

36TdwhIHusi.js

36TdwhIHusi.js

44 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

42 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

81 ms

SEO Factors

walkforpkd.kintera.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Walkforpkd.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 Walkforpkd.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.

Social Sharing Optimization

walkforpkd.kintera.org

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