Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

opss.org

Operation Supplement Safety | OPSS

Page Load Speed

2.1 sec in total

First Response

261 ms

Resources Loaded

1.4 sec

Page Rendered

415 ms

opss.org screenshot

About Website

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

Department of Defense dietary supplement resource for the military community, leaders, healthcare providers, and DoD civilians

Visit opss.org

Key Findings

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

Performance Metrics

opss.org performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

opss.org

261 ms

www.opss.org

18 ms

www.opss.org

113 ms

fbevents.js

130 ms

css_4VH3F3icjB7TRKSvb2sGNqzFwF7zqAEO6cAIR6s2emg.css

116 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Opss.org, 9% (3 requests) were made to Use.fontawesome.com and 6% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (589 ms) relates to the external source Gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.2 kB (69%)

Content Size

484.3 kB

After Optimization

148.1 kB

In fact, the total size of Opss.org main page is 484.3 kB. 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. CSS take 305.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 98.1 kB

  • Original 113.0 kB
  • After minification 106.5 kB
  • After compression 14.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 98.1 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 261 B

  • Original 44.4 kB
  • After minification 44.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. OPSS images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 101 B

  • Original 21.8 kB
  • After minification 21.8 kB
  • After compression 21.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-78%

Potential reduce by 237.7 kB

  • Original 305.0 kB
  • After minification 304.1 kB
  • After compression 67.4 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. Opss.org needs all CSS files to be minified and compressed as it can save up to 237.7 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (43%)

Requests Now

28

After Optimization

16

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

Accessibility Review

opss.org accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

ARIA IDs are not unique

Best Practices

opss.org best practices score

92

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

SEO Factors

opss.org SEO score

100

Search Engine Optimization Advices

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 Opss.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 Opss.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 OPSS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: