Tools & Wizards About Us
npef.org screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

npef.org

Northern Plains Eye Foundation | Rapid City, SD | Northern Plains Eye Foundation

Page Load Speed

1.4 sec in total

First Response

77 ms

Resources Loaded

1.1 sec

Page Rendered

187 ms

npef.org screenshot

About Website

Welcome to npef.org homepage info - get ready to check Npef best content right away, or after learning these important things about npef.org

Northern Plains Eye Foundation is a non-profit in Rapid City, SD, we preserve vision, restore sight, and develop research to promote eye health.

Visit npef.org

Key Findings

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

Performance Metrics

npef.org performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

npef.org

77 ms

www.npef.org

176 ms

gtm.js

52 ms

css

33 ms

global.css

43 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 88% of them (37 requests) were addressed to the original Npef.org, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (500 ms) belongs to the original domain Npef.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 375.0 kB (16%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Npef.org main page is 2.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. 25% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 9.4 kB

  • Original 14.0 kB
  • After minification 13.6 kB
  • After compression 4.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 9.4 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 23.2 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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. Npef images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 294.4 kB

  • Original 420.0 kB
  • After minification 412.3 kB
  • After compression 125.6 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 294.4 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 48.1 kB

  • Original 59.7 kB
  • After minification 54.8 kB
  • After compression 11.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. Npef.org needs all CSS files to be minified and compressed as it can save up to 48.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (39%)

Requests Now

38

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

npef.org

npef.org

77 ms

www.npef.org

www.npef.org

176 ms

gtm.js

gtm.js

52 ms

css

css

33 ms

global.css

global.css

43 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

80 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

193 ms

jquery-ui-1.9.2.custom.min.js

jquery-ui-1.9.2.custom.min.js

285 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

143 ms

jquery-ui-1.9.2.custom.min.css

jquery-ui-1.9.2.custom.min.css

156 ms

slides.min.jquery.js

slides.min.jquery.js

112 ms

slides.js.css

slides.js.css

113 ms

960-24col.css

960-24col.css

110 ms

analytics.js

analytics.js

58 ms

background.jpg

background.jpg

95 ms

logo.png

logo.png

40 ms

fb-f-logo--white-29.png

fb-f-logo--white-29.png

35 ms

tab-left.png

tab-left.png

35 ms

tab-right.png

tab-right.png

34 ms

nav-arrow-over.png

nav-arrow-over.png

37 ms

nav-arrow-down.png

nav-arrow-down.png

65 ms

nav-arrow.png

nav-arrow.png

68 ms

img-make-contribution.png

img-make-contribution.png

154 ms

local-eye-clinics-237x233.png

local-eye-clinics-237x233.png

165 ms

arrow-right.png

arrow-right.png

74 ms

2022-home-slider.png

2022-home-slider.png

379 ms

wsd-slider.png

wsd-slider.png

265 ms

protect-and-preserve-vision.png

protect-and-preserve-vision.png

262 ms

restore-sight.png

restore-sight.png

308 ms

support-eye-related-research.png

support-eye-related-research.png

390 ms

promote-eye-health.png

promote-eye-health.png

481 ms

pie-chart.png

pie-chart.png

309 ms

CVSI_150x118.png

CVSI_150x118.png

324 ms

christmas-gift-sight.jpg

christmas-gift-sight.jpg

373 ms

workplace-vision-wellness.png

workplace-vision-wellness.png

375 ms

memorial-scholarship.jpg

memorial-scholarship.jpg

364 ms

vision-for-a-lifetime-414x72.png

vision-for-a-lifetime-414x72.png

403 ms

2022-home-slider.png

2022-home-slider.png

500 ms

loading.png

loading.png

421 ms

none

none

442 ms

QdVUSTchPBm7nuUeVf70viFj.woff

QdVUSTchPBm7nuUeVf70viFj.woff

23 ms

collect

collect

14 ms

Accessibility Review

npef.org accessibility score

81

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

npef.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

npef.org SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Npef.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 Npef.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

npef.org

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