Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nvf.org

National Veterans Foundation | The Lifeline for Vets

Page Load Speed

3.1 sec in total

First Response

94 ms

Resources Loaded

2.5 sec

Page Rendered

518 ms

About Website

Visit nvf.org now to see the best up-to-date Nvf content for United States and also check out these interesting facts you probably never knew about nvf.org

The National Veterans Foundation has been helping vets for over 30 years. Our hotline is vets serving vets and provides needed help to vets and families.

Visit nvf.org

Key Findings

We analyzed Nvf.org page load time and found that the first response time was 94 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

nvf.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value2,680 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

nvf.org

94 ms

nvf.org

171 ms

style.min.css

59 ms

mediaelementplayer-legacy.min.css

91 ms

wp-mediaelement.min.css

97 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 51% of them (66 requests) were addressed to the original Nvf.org, 9% (12 requests) were made to Fonts.gstatic.com and 7% (9 requests) were made to Us.commitchange.com. The less responsive or slowest element that took the longest time to load (848 ms) belongs to the original domain Nvf.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.2 kB (6%)

Content Size

2.1 MB

After Optimization

2.0 MB

In fact, the total size of Nvf.org main page is 2.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.9 kB

  • Original 109.0 kB
  • After minification 106.1 kB
  • After compression 21.1 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 87.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 685.8 kB
  • After minification 685.8 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. Nvf images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 4.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 23.0 kB

  • Original 265.8 kB
  • After minification 249.8 kB
  • After compression 242.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. Nvf.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 78 (76%)

Requests Now

102

After Optimization

24

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

Accessibility Review

nvf.org accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

nvf.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

nvf.org SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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