Tools & Wizards About Us
nava.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nava.org

Home - North American Vexillological Association

Page Load Speed

727 ms in total

First Response

76 ms

Resources Loaded

441 ms

Page Rendered

210 ms

nava.org screenshot

About Website

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

Promoting excellence in Vexillology and camaraderie among those interested in flags.

Visit nava.org

Key Findings

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

Performance Metrics

nava.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

nava.org

76 ms

nava.org

57 ms

js

69 ms

jquery-ui.min.css

6 ms

common_ui.css

20 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 51% of them (26 requests) were addressed to the original Nava.org, 16% (8 requests) were made to Fonts.gstatic.com and 12% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (118 ms) relates to the external source Images.clubexpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 429.7 kB (39%)

Content Size

1.1 MB

After Optimization

666.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 19.3 kB

  • Original 27.2 kB
  • After minification 26.6 kB
  • After compression 7.9 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 19.3 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 18.8 kB

  • Original 457.3 kB
  • After minification 438.5 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. Nava images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 376.3 kB

  • Original 561.6 kB
  • After minification 552.8 kB
  • After compression 185.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 376.3 kB or 67% of the original size.

CSS Optimization

-31%

Potential reduce by 15.3 kB

  • Original 50.0 kB
  • After minification 47.6 kB
  • After compression 34.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. Nava.org needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 31% of the original size.

Requests Breakdown

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

Requests Now

41

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nava.org

nava.org

76 ms

nava.org

nava.org

57 ms

js

js

69 ms

jquery-ui.min.css

jquery-ui.min.css

6 ms

common_ui.css

common_ui.css

20 ms

widget.css

widget.css

18 ms

jquery.js

jquery.js

25 ms

fonts.css

fonts.css

24 ms

layout.css

layout.css

23 ms

menu.css

menu.css

24 ms

design.css

design.css

25 ms

color.css

color.css

26 ms

layout_color.css

layout_color.css

26 ms

menu_color.css

menu_color.css

26 ms

club.css

club.css

31 ms

custom.css

custom.css

34 ms

WebResource.axd

WebResource.axd

26 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

43 ms

jquery-ui.min.js

jquery-ui.min.js

60 ms

widget.js

widget.js

26 ms

common.js

common.js

30 ms

page_tools.css

page_tools.css

30 ms

galleria.twelve.css

galleria.twelve.css

30 ms

user_panel.js

user_panel.js

30 ms

js

js

57 ms

css

css

35 ms

css

css

65 ms

icon

icon

65 ms

printable.css

printable.css

2 ms

css

css

18 ms

stylesheet.css

stylesheet.css

36 ms

css

css

18 ms

css

css

23 ms

user_panel.css

user_panel.css

5 ms

nava_220_2118976222.gif

nava_220_2118976222.gif

94 ms

header-new_2_1137306160.png

header-new_2_1137306160.png

71 ms

powered_by.png

powered_by.png

2 ms

print2_1233090706.png

print2_1233090706.png

106 ms

GoodFlagBadFlag_small_9495820.jpg

GoodFlagBadFlag_small_9495820.jpg

118 ms

NACFS_Logo__267246578.png

NACFS_Logo__267246578.png

113 ms

snippet.js

snippet.js

59 ms

cart.svg

cart.svg

30 ms

NAVA-header-comp_no-flag_4-9-21_1500x130px_522553173.png

NAVA-header-comp_no-flag_4-9-21_1500x130px_522553173.png

94 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

32 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

36 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

43 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

50 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

57 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

51 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

57 ms

Accessibility Review

nava.org accessibility score

86

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

nava.org best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nava.org SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Nava.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 Nava.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

nava.org

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