Tools & Wizards About Us
nph.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nph.org

NPH Nuestros Pequeños Hermanos Serves Vulnerable Children

Page Load Speed

2.7 sec in total

First Response

72 ms

Resources Loaded

2.1 sec

Page Rendered

541 ms

nph.org screenshot

About Website

Click here to check amazing NPH content for Nicaragua. Otherwise, check out these important facts you probably never knew about nph.org

NPH Nuestros Pequeños Hermanos empowers vulnerable children to build resilient communities. Learn how we support the whole child.

Visit nph.org

Key Findings

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

Performance Metrics

nph.org performance score

0

Network Requests Diagram

nph.org

72 ms

www.nph.org

1359 ms

content.css

60 ms

cookies.js

88 ms

functions.js

98 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 72% of them (46 requests) were addressed to the original Nph.org, 3% (2 requests) were made to Apis.google.com and 3% (2 requests) were made to Seal.godaddy.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nph.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 601.8 kB (58%)

Content Size

1.0 MB

After Optimization

432.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nph.org main page is 1.0 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. 50% of websites need less resources to load. Javascripts take 354.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 136.8 kB

  • Original 152.4 kB
  • After minification 147.2 kB
  • After compression 15.6 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 136.8 kB or 90% of the original size.

Image Optimization

-8%

Potential reduce by 20.5 kB

  • Original 261.5 kB
  • After minification 241.0 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. NPH images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 222.0 kB

  • Original 354.6 kB
  • After minification 350.3 kB
  • After compression 132.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 222.0 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 222.5 kB

  • Original 266.1 kB
  • After minification 259.3 kB
  • After compression 43.7 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. Nph.org needs all CSS files to be minified and compressed as it can save up to 222.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (43%)

Requests Now

60

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nph.org

nph.org

72 ms

www.nph.org

www.nph.org

1359 ms

content.css

content.css

60 ms

cookies.js

cookies.js

88 ms

functions.js

functions.js

98 ms

helptips.js

helptips.js

119 ms

jquery.js

jquery.js

172 ms

plusone.js

plusone.js

56 ms

helptipstyle.js

helptipstyle.js

100 ms

getSeal

getSeal

477 ms

menu_var-all.js

menu_var-all.js

75 ms

menu132_compact.js

menu132_compact.js

118 ms

brand

brand

24 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

ga.js

ga.js

72 ms

sdk.js

sdk.js

100 ms

tUXAov3wa64

tUXAov3wa64

131 ms

1O6IVWZV94c

1O6IVWZV94c

194 ms

back.gif

back.gif

49 ms

back-middle.png

back-middle.png

48 ms

back-top.png

back-top.png

47 ms

space.gif

space.gif

48 ms

feed-16.png

feed-16.png

76 ms

facebook-16.png

facebook-16.png

76 ms

twitter-16.png

twitter-16.png

102 ms

youtube-16.png

youtube-16.png

102 ms

picasa-16.png

picasa-16.png

100 ms

linkedin-16.png

linkedin-16.png

102 ms

googleplus-16.png

googleplus-16.png

102 ms

big.jpg

big.jpg

191 ms

int-en-white.png

int-en-white.png

114 ms

pe-en.png

pe-en.png

127 ms

home-mo.jpg

home-mo.jpg

115 ms

home.jpg

home.jpg

114 ms

cardiac.jpg

cardiac.jpg

186 ms

GoingtotheSource.jpg

GoingtotheSource.jpg

155 ms

valentines2016.jpg

valentines2016.jpg

180 ms

Cholerachildstory.jpg

Cholerachildstory.jpg

188 ms

maxwater.jpg

maxwater.jpg

186 ms

YoanandJaime.jpg

YoanandJaime.jpg

251 ms

006.jpg

006.jpg

249 ms

013.jpg

013.jpg

252 ms

023.jpg

023.jpg

272 ms

listwhite.gif

listwhite.gif

252 ms

list.gif

list.gif

250 ms

feed-48.png

feed-48.png

254 ms

facebook-48.png

facebook-48.png

254 ms

picasa-48.png

picasa-48.png

253 ms

twitter-48.png

twitter-48.png

269 ms

youtube-48.png

youtube-48.png

267 ms

email-48.png

email-48.png

306 ms

website-48.png

website-48.png

306 ms

wikipedia-48.png

wikipedia-48.png

306 ms

back-bottom.png

back-bottom.png

382 ms

__utm.gif

__utm.gif

32 ms

147 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

45 ms

www-embed-player.js

www-embed-player.js

79 ms

xd_arbiter.php

xd_arbiter.php

43 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

31 ms

ad_status.js

ad_status.js

49 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

130 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

131 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

125 ms

SEO Factors

nph.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 Nph.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 Nph.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

nph.org

Open Graph data is detected on the main page of NPH. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: