Tools & Wizards About Us
righttofightexhibit.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

righttofightexhibit.org

Fighting for the Right to Fight: African American Experiences in World War II | The National WWII Museum in New Orleans

Page Load Speed

1.3 sec in total

First Response

8 ms

Resources Loaded

850 ms

Page Rendered

453 ms

righttofightexhibit.org screenshot

About Website

Click here to check amazing Right To Fight Exhibit content. Otherwise, check out these important facts you probably never knew about righttofightexhibit.org

The National WWII Museum presents a Special Exhibit about African American Experiences in World War II. July 4, 2015 - May 30, 2016 in New Orleans

Visit righttofightexhibit.org

Key Findings

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

righttofightexhibit.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.083

93/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

8 ms

style.css

4 ms

normalize.css

9 ms

font-awesome.min.css

14 ms

lightgallery.css

8 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 43% of them (21 requests) were addressed to the original Righttofightexhibit.org, 8% (4 requests) were made to Connect.facebook.net and 6% (3 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (273 ms) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.1 kB (19%)

Content Size

1.2 MB

After Optimization

938.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Righttofightexhibit.org main page is 1.2 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. 75% 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. Images take 874.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 21.2 kB

  • Original 29.8 kB
  • After minification 28.2 kB
  • After compression 8.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 21.2 kB or 71% of the original size.

Image Optimization

-8%

Potential reduce by 73.3 kB

  • Original 874.4 kB
  • After minification 801.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. Right To Fight Exhibit images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 52.8 kB

  • Original 170.4 kB
  • After minification 169.3 kB
  • After compression 117.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 52.8 kB or 31% of the original size.

CSS Optimization

-86%

Potential reduce by 65.8 kB

  • Original 76.6 kB
  • After minification 54.6 kB
  • After compression 10.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. Righttofightexhibit.org needs all CSS files to be minified and compressed as it can save up to 65.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (53%)

Requests Now

43

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

8 ms

style.css

style.css

4 ms

normalize.css

normalize.css

9 ms

font-awesome.min.css

font-awesome.min.css

14 ms

lightgallery.css

lightgallery.css

8 ms

6ef90d7a-1797-47b9-958a-7e8dc5427011.css

6ef90d7a-1797-47b9-958a-7e8dc5427011.css

89 ms

css

css

20 ms

jquery.min.js

jquery.min.js

14 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

5 ms

uikit.min.js

uikit.min.js

8 ms

selectivizr.min.js

selectivizr.min.js

8 ms

waypoints.min.js

waypoints.min.js

9 ms

plugins.js

plugins.js

9 ms

main.js

main.js

8 ms

share.js

share.js

9 ms

share.js

share.js

14 ms

widgets.js

widgets.js

144 ms

gtm.js

gtm.js

161 ms

all.js

all.js

134 ms

nww2m-logo_wht.png

nww2m-logo_wht.png

140 ms

rtf-mobile-logo.jpg

rtf-mobile-logo.jpg

106 ms

share_1T.png

share_1T.png

103 ms

real_cf.png

real_cf.png

37 ms

soldiers.jpg

soldiers.jpg

46 ms

blk-bg.png

blk-bg.png

36 ms

rtf-logo-horiz.jpg

rtf-logo-horiz.jpg

35 ms

before-cutout.png

before-cutout.png

44 ms

during-cutout.png

during-cutout.png

37 ms

after-cutout.png

after-cutout.png

44 ms

entergy-logo.png

entergy-logo.png

37 ms

IHeartMedia-white.png

IHeartMedia-white.png

39 ms

Advocate_White.png

Advocate_White.png

39 ms

fb754dec-aa8f-444c-be48-868464c47ab0.woff

fb754dec-aa8f-444c-be48-868464c47ab0.woff

90 ms

2c9e64ce-9ea3-446e-a7e9-7e6a9cd2ba17.woff

2c9e64ce-9ea3-446e-a7e9-7e6a9cd2ba17.woff

138 ms

4iCj6KZ0a9NXjG8dWC4.ttf

4iCj6KZ0a9NXjG8dWC4.ttf

39 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

41 ms

widget_iframe.7dae38096d06923d683a2a807172322a.html

widget_iframe.7dae38096d06923d683a2a807172322a.html

273 ms

all.js

all.js

84 ms

bat.js

bat.js

216 ms

fbevents.js

fbevents.js

57 ms

ebOneTag.js

ebOneTag.js

213 ms

activity;xsp=4637842;ord=7756694585550.576

activity;xsp=4637842;ord=7756694585550.576

211 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

90 ms

js

js

89 ms

activity;xsp=4908331;ord=5668210820294917

activity;xsp=4908331;ord=5668210820294917

208 ms

analytics.js

analytics.js

166 ms

1646928738961854

1646928738961854

120 ms

collect

collect

83 ms

collect

collect

60 ms

Accessibility Review

righttofightexhibit.org accessibility score

71

Accessibility Issues

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

Image elements do not have [alt] attributes

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

Best Practices

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

High

Page has valid source maps

SEO Factors

righttofightexhibit.org SEO score

83

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

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

    N/A

  • Encoding

    UTF-8

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

righttofightexhibit.org

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