Tools & Wizards About Us
hjf.org screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

hjf.org

Homepage | HJF

Page Load Speed

1.1 sec in total

First Response

19 ms

Resources Loaded

894 ms

Page Rendered

166 ms

hjf.org screenshot

About Website

Click here to check amazing HJF content for United States. Otherwise, check out these important facts you probably never knew about hjf.org

Our Mission is to Advance Military Medicine. We are a nonprofit linking the military medical community and millions of American service families and civilians.

Visit hjf.org

Key Findings

We analyzed Hjf.org page load time and found that the first response time was 19 ms and then it took 1.1 sec 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

hjf.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

hjf.org

19 ms

www.hjf.org

292 ms

golden.css

40 ms

hjf.css

31 ms

hjf-int-Home.css

47 ms

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

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-78%

Potential reduce by 22.2 kB

  • Original 28.6 kB
  • After minification 23.1 kB
  • After compression 6.4 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 5.6 kB, which is 19% 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 22.2 kB or 78% of the original size.

Image Optimization

-15%

Potential reduce by 187.9 kB

  • Original 1.2 MB
  • After minification 1.0 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. Obviously, HJF needs image optimization as it can save up to 187.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 625.2 kB

  • Original 907.7 kB
  • After minification 860.2 kB
  • After compression 282.5 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 625.2 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (54%)

Requests Now

35

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hjf.org

hjf.org

19 ms

www.hjf.org

www.hjf.org

292 ms

golden.css

golden.css

40 ms

hjf.css

hjf.css

31 ms

hjf-int-Home.css

hjf-int-Home.css

47 ms

nivo-slider.css

nivo-slider.css

38 ms

jquery.min.js

jquery.min.js

35 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

63 ms

reset-cachekey-05a78aad81de33b9bebb75ba314a7b5a.css

reset-cachekey-05a78aad81de33b9bebb75ba314a7b5a.css

74 ms

base-cachekey-b24a0a11d78b8b1eafb4d4096acf5f40.css

base-cachekey-b24a0a11d78b8b1eafb4d4096acf5f40.css

66 ms

resourceplone.app.jquerytools.overlays-cachekey-c090f625b135233e83fb1f9fdd3a33f6.css

resourceplone.app.jquerytools.overlays-cachekey-c090f625b135233e83fb1f9fdd3a33f6.css

74 ms

resourceplone.app.widgets-cachekey-c9225b00e246058d6b5546560142a3be.css

resourceplone.app.widgets-cachekey-c9225b00e246058d6b5546560142a3be.css

148 ms

ploneCustom-cachekey-8347d7a0e5e892ed60e0a732504ee8b1.css

ploneCustom-cachekey-8347d7a0e5e892ed60e0a732504ee8b1.css

74 ms

resourceplone.app.jquery-cachekey-0504cd97f4a25223f55fa86f93e2424f.js

resourceplone.app.jquery-cachekey-0504cd97f4a25223f55fa86f93e2424f.js

94 ms

++resource++plone.app.widgets.js

++resource++plone.app.widgets.js

183 ms

resourceplone.app.jquerytools-cachekey-fdb47bbd067b07caac155d07f4827c41.js

resourceplone.app.jquerytools-cachekey-fdb47bbd067b07caac155d07f4827c41.js

138 ms

hjf_donations-cachekey-2a9e2f391a4748ad3f88eb85ba3824e0.js

hjf_donations-cachekey-2a9e2f391a4748ad3f88eb85ba3824e0.js

257 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

135 ms

jquery.cycle2.caption2.min.js

jquery.cycle2.caption2.min.js

94 ms

cycle2_defaults.css

cycle2_defaults.css

178 ms

resourcedrop_down-cachekey-b368fe4deffcaba30a1fccae53d6f2cf.css

resourcedrop_down-cachekey-b368fe4deffcaba30a1fccae53d6f2cf.css

111 ms

++resource++collective.portletpage.css

++resource++collective.portletpage.css

16 ms

analytics.js

analytics.js

59 ms

HJF-Website-Banner1.jpg

HJF-Website-Banner1.jpg

50 ms

HJFlogo-150.png

HJFlogo-150.png

52 ms

HJF_title_block.png

HJF_title_block.png

50 ms

test-arrow1.png

test-arrow1.png

50 ms

carbon_chains.png

carbon_chains.png

275 ms

whitefadetop.png

whitefadetop.png

51 ms

60alphawhite.png

60alphawhite.png

49 ms

whitefadebottom.png

whitefadebottom.png

81 ms

CDHAM-resize.png

CDHAM-resize.png

217 ms

MilMedTimeLine.png

MilMedTimeLine.png

252 ms

military-spouses.jpg

military-spouses.jpg

250 ms

sprites.png

sprites.png

81 ms

spinner.gif

spinner.gif

98 ms

collect

collect

12 ms

Accessibility Review

hjf.org accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

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

SEO Factors

hjf.org SEO score

84

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

High

Tap targets are not sized appropriately

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

hjf.org

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