Tools & Wizards About Us
oth.io screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

oth.io

Virtual Care for Life - Healtcare for every person | OTH.io

Page Load Speed

3.2 sec in total

First Response

419 ms

Resources Loaded

2.5 sec

Page Rendered

212 ms

oth.io screenshot

About Website

Click here to check amazing OTH content. Otherwise, check out these important facts you probably never knew about oth.io

By aggregating virtual care actors, we enable access to healthcare for every person on the planet – anywhere, anytime!

Visit oth.io

Key Findings

We analyzed Oth.io page load time and found that the first response time was 419 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

oth.io performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value370 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.462

19/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

oth.io

419 ms

5281d59c1c15ad37594e7777fb7cc2bd.js

100 ms

330231efe61651c7c3a18db8f26f95f9.js

199 ms

jquery.min.js

37 ms

jquery-migrate.min.js

47 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 70% of them (30 requests) were addressed to the original Oth.io, 16% (7 requests) were made to C0.wp.com and 2% (1 request) were made to Js-eu1.hs-scripts.com. The less responsive or slowest element that took the longest time to load (594 ms) relates to the external source Js-eu1.hs-analytics.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.7 kB (26%)

Content Size

625.0 kB

After Optimization

460.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oth.io main page is 625.0 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. 40% of websites need less resources to load. Javascripts take 254.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 157.3 kB

  • Original 193.8 kB
  • After minification 191.3 kB
  • After compression 36.5 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 157.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 82 B

  • Original 135.7 kB
  • After minification 135.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. OTH images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.3 kB

  • Original 254.5 kB
  • After minification 254.5 kB
  • After compression 248.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

-3%

Potential reduce by 1.1 kB

  • Original 41.0 kB
  • After minification 41.0 kB
  • After compression 39.9 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. Oth.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (85%)

Requests Now

41

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oth.io

oth.io

419 ms

5281d59c1c15ad37594e7777fb7cc2bd.js

5281d59c1c15ad37594e7777fb7cc2bd.js

100 ms

330231efe61651c7c3a18db8f26f95f9.js

330231efe61651c7c3a18db8f26f95f9.js

199 ms

jquery.min.js

jquery.min.js

37 ms

jquery-migrate.min.js

jquery-migrate.min.js

47 ms

icons.min.js

icons.min.js

287 ms

agsdi-icons.min.js

agsdi-icons.min.js

290 ms

language-cookie.js

language-cookie.js

293 ms

imagelightbox.min.js

imagelightbox.min.js

293 ms

underscore.min.js

underscore.min.js

49 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

297 ms

front.js

front.js

297 ms

25903600.js

25903600.js

581 ms

js

js

85 ms

8503f0c79f4218520ab14c0ae52a2080.js

8503f0c79f4218520ab14c0ae52a2080.js

398 ms

photon.min.js

photon.min.js

48 ms

scripts.min.js

scripts.min.js

399 ms

jquery.fitvids.js

jquery.fitvids.js

396 ms

jquery.mobile.js

jquery.mobile.js

396 ms

intersection-observer.js

intersection-observer.js

396 ms

lazy-images.js

lazy-images.js

396 ms

common.js

common.js

497 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

2 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

2 ms

jetpack.css

jetpack.css

2 ms

Bildschirmfoto-2023-01-09-um-15.24.12.png

Bildschirmfoto-2023-01-09-um-15.24.12.png

90 ms

Logo-OTH-Menue.jpg

Logo-OTH-Menue.jpg

194 ms

en.png

en.png

187 ms

de.png

de.png

185 ms

et-divi-dynamic-tb-878-tb-945-238453-late.css

et-divi-dynamic-tb-878-tb-945-238453-late.css

137 ms

modules.woff

modules.woff

109 ms

animate.min.css

animate.min.css

99 ms

collectedforms.js

collectedforms.js

495 ms

25903600.js

25903600.js

594 ms

banner.js

banner.js

509 ms

icons.min.css

icons.min.css

103 ms

agsdi-icons.min.css

agsdi-icons.min.css

98 ms

styles.css

styles.css

101 ms

imagelightbox.min.css

imagelightbox.min.css

99 ms

style.min.css

style.min.css

98 ms

style.min.css

style.min.css

100 ms

cms-navigation-base.css

cms-navigation-base.css

99 ms

cms-navigation.css

cms-navigation.css

100 ms

Accessibility Review

oth.io accessibility score

73

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

Links do not have a discernible name

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

oth.io 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

High

Page has valid source maps

SEO Factors

oth.io SEO score

86

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

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 doesn't use 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 Oth.io 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 Oth.io 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

oth.io

Open Graph data is detected on the main page of OTH. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: