Tools & Wizards About Us
opss.org screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

opss.org

Operation Supplement Safety | OPSS

Page Load Speed

616 ms in total

First Response

64 ms

Resources Loaded

552 ms

Page Rendered

0 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 64 ms and then it took 552 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

opss.org performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

opss.org

64 ms

www.opss.org

226 ms

css_QpFCMeoXMvX2htGc5bn8_b-rCDcmeBxgp1PfqXxDUXU.css

9 ms

css_QJZdnH1tD3njNf8PGYZ-083NVUqBS8tB3iq8Mclj4wA.css

32 ms

css_DI-NK9yAHfi1rgAWgF9FyoGavGBzDrIZoaKs0_CSdBw.css

27 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 88% of them (38 requests) were addressed to the original Opss.org, 2% (1 request) were made to Google.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (226 ms) belongs to the original domain Opss.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.4 kB (12%)

Content Size

559.3 kB

After Optimization

490.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Opss.org main page is 559.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. 50% of websites need less resources to load. Javascripts take 282.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 62.7 kB

  • Original 74.6 kB
  • After minification 66.6 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 8.0 kB, which is 11% 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 62.7 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 4.2 kB

  • Original 143.4 kB
  • After minification 139.2 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 1.0 kB

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

CSS Optimization

-1%

Potential reduce by 511 B

  • Original 59.1 kB
  • After minification 59.0 kB
  • After compression 58.6 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (42%)

Requests Now

33

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 33 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 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

opss.org

opss.org

64 ms

www.opss.org

www.opss.org

226 ms

css_QpFCMeoXMvX2htGc5bn8_b-rCDcmeBxgp1PfqXxDUXU.css

css_QpFCMeoXMvX2htGc5bn8_b-rCDcmeBxgp1PfqXxDUXU.css

9 ms

css_QJZdnH1tD3njNf8PGYZ-083NVUqBS8tB3iq8Mclj4wA.css

css_QJZdnH1tD3njNf8PGYZ-083NVUqBS8tB3iq8Mclj4wA.css

32 ms

css_DI-NK9yAHfi1rgAWgF9FyoGavGBzDrIZoaKs0_CSdBw.css

css_DI-NK9yAHfi1rgAWgF9FyoGavGBzDrIZoaKs0_CSdBw.css

27 ms

js_DiFzpnPcuE3LUOGvue4DcScZuuKt9Iycsl5iypFc8pA.js

js_DiFzpnPcuE3LUOGvue4DcScZuuKt9Iycsl5iypFc8pA.js

18 ms

api.js

api.js

46 ms

js_mii3KeXAXxlt6aWNV26GoHH3BS9dshMeg7E0hMCav54.js

js_mii3KeXAXxlt6aWNV26GoHH3BS9dshMeg7E0hMCav54.js

29 ms

css

css

36 ms

css_svAkiHWYCh7f9NO6McdSkZsYEI6bx3wbTAfmDtvTiHM.css

css_svAkiHWYCh7f9NO6McdSkZsYEI6bx3wbTAfmDtvTiHM.css

5 ms

recaptcha__en.js

recaptcha__en.js

63 ms

gtm.js

gtm.js

164 ms

banner-3.jpg

banner-3.jpg

33 ms

OPSS_home_300_200.png

OPSS_home_300_200.png

20 ms

USU-CHAMP-header-white.svg

USU-CHAMP-header-white.svg

33 ms

OPSS-LockUp-white.svg

OPSS-LockUp-white.svg

19 ms

facebook.svg

facebook.svg

22 ms

x-twitter.svg

x-twitter.svg

22 ms

instagram.svg

instagram.svg

30 ms

youtube.svg

youtube.svg

32 ms

search.svg

search.svg

31 ms

search.webp

search.webp

30 ms

caret-filled-down.webp

caret-filled-down.webp

30 ms

caret-filled-up.webp

caret-filled-up.webp

111 ms

facebook.webp

facebook.webp

112 ms

x-twitter.webp

x-twitter.webp

109 ms

instagram.webp

instagram.webp

110 ms

youtube.webp

youtube.webp

110 ms

OPSS-white.svg

OPSS-white.svg

112 ms

prohibited-list.svg

prohibited-list.svg

115 ms

PES-icon-purple.svg

PES-icon-purple.svg

117 ms

ingredient-lookup.svg

ingredient-lookup.svg

115 ms

medical-report.svg

medical-report.svg

121 ms

supplements.svg

supplements.svg

120 ms

ask-expert.svg

ask-expert.svg

118 ms

Semaglutide.jpg

Semaglutide.jpg

126 ms

Pills_Black_Background.jpeg

Pills_Black_Background.jpeg

123 ms

hemp_0.jpg

hemp_0.jpg

129 ms

memory_0.jpg

memory_0.jpg

123 ms

FDA-white.svg

FDA-white.svg

125 ms

envelope.svg

envelope.svg

124 ms

CHAMP-white.svg

CHAMP-white.svg

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

106 ms

Accessibility Review

opss.org accessibility score

92

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

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

opss.org

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: