Tools & Wizards About Us
ndnqi.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ndnqi.org

NDNQI - National Database of Nursing Quality Indicators

Page Load Speed

976 ms in total

First Response

19 ms

Resources Loaded

713 ms

Page Rendered

244 ms

ndnqi.org screenshot

About Website

Visit ndnqi.org now to see the best up-to-date NDNQI content and also check out these interesting facts you probably never knew about ndnqi.org

National Database of Nursing Quality Indicators (NDNQI) provides robust analytics to support the importance of nurse sensitive measures.

Visit ndnqi.org

Key Findings

We analyzed Ndnqi.org page load time and found that the first response time was 19 ms and then it took 957 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

ndnqi.org performance score

0

Network Requests Diagram

ndnqi.org

19 ms

nursingquality

66 ms

nursing-quality

248 ms

css

25 ms

font-awesome.min.css

10 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ndnqi.org, 72% (39 requests) were made to Pressganey.com and 15% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (248 ms) relates to the external source Pressganey.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 816.7 kB (73%)

Content Size

1.1 MB

After Optimization

301.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ndnqi.org main page is 1.1 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. CSS take 630.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.9 kB

  • Original 26.4 kB
  • After minification 20.2 kB
  • After compression 6.5 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. This page needs HTML code to be minified as it can gain 6.2 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.9 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 2.4 kB

  • Original 75.6 kB
  • After minification 73.1 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. NDNQI images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 263.4 kB

  • Original 385.7 kB
  • After minification 368.0 kB
  • After compression 122.3 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 263.4 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 530.9 kB

  • Original 630.6 kB
  • After minification 591.7 kB
  • After compression 99.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. Ndnqi.org needs all CSS files to be minified and compressed as it can save up to 530.9 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ndnqi.org

ndnqi.org

19 ms

nursingquality

nursingquality

66 ms

nursing-quality

nursing-quality

248 ms

css

css

25 ms

font-awesome.min.css

font-awesome.min.css

10 ms

html5shiv.min.js

html5shiv.min.js

43 ms

respond.min.js

respond.min.js

77 ms

modernizr.js

modernizr.js

83 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

145 ms

kendo.common.min.css

kendo.common.min.css

122 ms

kendo.flat.min.css

kendo.flat.min.css

94 ms

kendo.dataviz.min.css

kendo.dataviz.min.css

92 ms

kendo.dataviz.flat.min.css

kendo.dataviz.flat.min.css

91 ms

bootstrap.min.css

bootstrap.min.css

99 ms

flexslider.css

flexslider.css

99 ms

style.css

style.css

110 ms

tablet.css

tablet.css

118 ms

mobile.css

mobile.css

139 ms

override.css

override.css

136 ms

WebResource.axd

WebResource.axd

141 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

167 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

185 ms

bootstrap.min.js

bootstrap.min.js

151 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

152 ms

jquery.paging.min.js

jquery.paging.min.js

152 ms

global.js

global.js

154 ms

script.js

script.js

154 ms

analytics.js

analytics.js

19 ms

collect

collect

50 ms

logo.png

logo.png

144 ms

footer-logo.png

footer-logo.png

144 ms

update.min.js

update.min.js

13 ms

header-social.png

header-social.png

41 ms

search-icon.png

search-icon.png

40 ms

dropdown-bg.png

dropdown-bg.png

42 ms

title-page-shadow.png

title-page-shadow.png

39 ms

detail-top-bg.jpg

detail-top-bg.jpg

73 ms

half-circle.png

half-circle.png

58 ms

detail-top-shadow.png

detail-top-shadow.png

57 ms

triangle-white.png

triangle-white.png

58 ms

featured-resources-after.png

featured-resources-after.png

70 ms

icon-note-big.png

icon-note-big.png

72 ms

icon-comment-big.png

icon-comment-big.png

71 ms

icon-book-big.png

icon-book-big.png

88 ms

footer-social.png

footer-social.png

88 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

36 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

50 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

53 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

54 ms

PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff

PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff

53 ms

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

54 ms

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

53 ms

PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff

PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff

62 ms

c.png

c.png

5 ms

SEO Factors

ndnqi.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ndnqi.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ndnqi.org main page’s claimed encoding is . 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

ndnqi.org

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