Tools & Wizards About Us
oathealth.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

oathealth.com

Sur Nutrition – Plant-Based Supplements for Sports & Well-Being

Page Load Speed

951 ms in total

First Response

113 ms

Resources Loaded

759 ms

Page Rendered

79 ms

oathealth.com screenshot

About Website

Click here to check amazing Oathealth content for United States. Otherwise, check out these important facts you probably never knew about oathealth.com

Sur sources from nature to create clean, powerful, plant-based nutrition products for your work-outs and general well-being.

Visit oathealth.com

Key Findings

We analyzed Oathealth.com page load time and found that the first response time was 113 ms and then it took 838 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

oathealth.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

oathealth.com

113 ms

www.oathealth.com

120 ms

all.css

57 ms

lightbox.css

108 ms

main.js

107 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 71% of them (22 requests) were addressed to the original Oathealth.com, 13% (4 requests) were made to Google-analytics.com and 10% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (294 ms) relates to the external source Vimeo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.5 kB (9%)

Content Size

157.3 kB

After Optimization

143.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oathealth.com main page is 157.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. 30% of websites need less resources to load. Images take 75.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 12.0 kB

  • Original 15.9 kB
  • After minification 10.5 kB
  • After compression 3.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 5.4 kB, which is 34% 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 12.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 68 B

  • Original 75.7 kB
  • After minification 75.6 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. Oathealth images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 679 B

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

CSS Optimization

-10%

Potential reduce by 708 B

  • Original 7.4 kB
  • After minification 7.4 kB
  • After compression 6.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. Oathealth.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (67%)

Requests Now

27

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oathealth. 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 as a result speed up the page load time.

Network Requests Diagram

oathealth.com

oathealth.com

113 ms

www.oathealth.com

www.oathealth.com

120 ms

all.css

all.css

57 ms

lightbox.css

lightbox.css

108 ms

main.js

main.js

107 ms

swfobject.js

swfobject.js

109 ms

jquery.js

jquery.js

110 ms

videoBrowser.js

videoBrowser.js

109 ms

ScriptServlet

ScriptServlet

4 ms

gtm.js

gtm.js

104 ms

logo.gif

logo.gif

102 ms

embed

embed

294 ms

ga.js

ga.js

30 ms

phone-bg.gif

phone-bg.gif

98 ms

sep-orange.gif

sep-orange.gif

98 ms

bg-main-nav.gif

bg-main-nav.gif

97 ms

pointer.gif

pointer.gif

97 ms

nutrim.jpg

nutrim.jpg

148 ms

orange-menu-bg.gif

orange-menu-bg.gif

158 ms

vert-lines-1.gif

vert-lines-1.gif

158 ms

shadow-2.gif

shadow-2.gif

157 ms

vert-lines-2.gif

vert-lines-2.gif

156 ms

shadow-3.gif

shadow-3.gif

156 ms

sep-2.gif

sep-2.gif

198 ms

footer-logo-3.gif

footer-logo-3.gif

288 ms

footer-logo-4.gif

footer-logo-4.gif

289 ms

__utm.gif

__utm.gif

33 ms

js

js

63 ms

analytics.js

analytics.js

22 ms

collect

collect

98 ms

js

js

49 ms

Accessibility Review

oathealth.com accessibility score

48

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

oathealth.com best practices score

58

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

Browser errors were logged to the console

SEO Factors

oathealth.com SEO score

92

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

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oathealth.com 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 Oathealth.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

oathealth.com

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