Tools & Wizards About Us
onhealth.de screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

onhealth.de

IT-Provider für das Gesundheitswesen | Telekom Healthcare Solutions

Page Load Speed

3.7 sec in total

First Response

528 ms

Resources Loaded

2.7 sec

Page Rendered

476 ms

onhealth.de screenshot

About Website

Welcome to onhealth.de homepage info - get ready to check Onhealth best content right away, or after learning these important things about onhealth.de

Als IT-Provider für ein modernes Gesundheitswesen entwickeln wir innovative digitale Lösungen in Klinik-IT, Cloud & Sicherheit und E-Health.

Visit onhealth.de

Key Findings

We analyzed Onhealth.de page load time and found that the first response time was 528 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

onhealth.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value280 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.368

29/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

www.telekom-healthcare.com

528 ms

loader-1d454fb1128c03f76d093c66272be074.css

210 ms

merged-4f8464576dabaa1b7deec66c386f359d-33069a1b620e8e960e132214492f7d79.css

293 ms

merged-f3bea4b270c94006c48dd94e86d1bfdc-0c3334eb54d9a047baa2a7cd0091f44b.js

604 ms

myscript2.js

305 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that all of those requests were addressed to Onhealth.de and no external sources were called. The less responsive or slowest element that took the longest time to load (945 ms) relates to the external source Telekom-healthcare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.7 kB (15%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images

In fact, the total size of Onhealth.de main page is 1.5 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 47.7 kB

  • Original 61.3 kB
  • After minification 54.6 kB
  • After compression 13.6 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 6.7 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 47.7 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 176.0 kB

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

Requests Breakdown

We found no issues to fix!

Requests Now

41

After Optimization

41

  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onhealth. According to our analytics all requests are already optimized.

Network Requests Diagram

www.telekom-healthcare.com

www.telekom-healthcare.com

528 ms

loader-1d454fb1128c03f76d093c66272be074.css

loader-1d454fb1128c03f76d093c66272be074.css

210 ms

merged-4f8464576dabaa1b7deec66c386f359d-33069a1b620e8e960e132214492f7d79.css

merged-4f8464576dabaa1b7deec66c386f359d-33069a1b620e8e960e132214492f7d79.css

293 ms

merged-f3bea4b270c94006c48dd94e86d1bfdc-0c3334eb54d9a047baa2a7cd0091f44b.js

merged-f3bea4b270c94006c48dd94e86d1bfdc-0c3334eb54d9a047baa2a7cd0091f44b.js

604 ms

myscript2.js

myscript2.js

305 ms

DT_healtcare_solutions_rgb_p.svg

DT_healtcare_solutions_rgb_p.svg

173 ms

m1-m2.png

m1-m2.png

210 ms

m2-m1.png

m2-m1.png

388 ms

m2.png

m2.png

215 ms

csm_Kooperation_GoogleCloud_Universitaetsklinik_Telekom_8bab0b0fd2.jpg

csm_Kooperation_GoogleCloud_Universitaetsklinik_Telekom_8bab0b0fd2.jpg

419 ms

m3.png

m3.png

293 ms

csm_bi-230912-symbolfoto-digital-identity-barmer_5b699bb4e6.jpg

csm_bi-230912-symbolfoto-digital-identity-barmer_5b699bb4e6.jpg

499 ms

m5.png

m5.png

317 ms

csm_MSU_8074_a8ec8fca15.jpg

csm_MSU_8074_a8ec8fca15.jpg

423 ms

csm_VAMED_TELEKOM_d676ba72c4.jpg

csm_VAMED_TELEKOM_d676ba72c4.jpg

585 ms

csm_Potrait_Gottfried_Ludewig_090322_a5db605546.jpg

csm_Potrait_Gottfried_Ludewig_090322_a5db605546.jpg

424 ms

m1.png

m1.png

489 ms

csm_1280x720_LinkedIn_A__rzte_WhatsApp_20230426_EEM_20c24fa7aa.jpg

csm_1280x720_LinkedIn_A__rzte_WhatsApp_20230426_EEM_20c24fa7aa.jpg

527 ms

csm_TelekomKnappschaftRecare3866x2579-TelekomCom_2874938702.jpg

csm_TelekomKnappschaftRecare3866x2579-TelekomCom_2874938702.jpg

533 ms

csm_telekom_com_THS_Blutbahnen_RGB_4520e2059d.jpg

csm_telekom_com_THS_Blutbahnen_RGB_4520e2059d.jpg

534 ms

csm_Telekom_Patientenabrechnung_88ddca9903.jpg

csm_Telekom_Patientenabrechnung_88ddca9903.jpg

594 ms

csm_TelekomRecare_A_neu_120123_c15c9276b3.jpg

csm_TelekomRecare_A_neu_120123_c15c9276b3.jpg

605 ms

csm_THC_Karriere_462e80aad8.jpg

csm_THC_Karriere_462e80aad8.jpg

633 ms

heart.svg

heart.svg

641 ms

pulse.svg

pulse.svg

639 ms

cloud.svg

cloud.svg

687 ms

THC_E-Health_Icon.svg

THC_E-Health_Icon.svg

697 ms

THC_Klinik-IT_Icon_Telematikinfrastruktur.svg

THC_Klinik-IT_Icon_Telematikinfrastruktur.svg

714 ms

csm_THC_Erfolgsgeschichte_Teaser-BG_46ee0c2a5c.jpg

csm_THC_Erfolgsgeschichte_Teaser-BG_46ee0c2a5c.jpg

840 ms

csm_Gemeinsam_360digital__IT-Profis_aus_Kliniken_treiben_Digitalisierung_im_Gesundheitswesen_voran_85eb86b97c.jpg

csm_Gemeinsam_360digital__IT-Profis_aus_Kliniken_treiben_Digitalisierung_im_Gesundheitswesen_voran_85eb86b97c.jpg

747 ms

csm_BG_Esslingen_f41ad3a4b0.jpg

csm_BG_Esslingen_f41ad3a4b0.jpg

749 ms

csm_BG_UKE_Hamburg_7858a586f2.jpg

csm_BG_UKE_Hamburg_7858a586f2.jpg

791 ms

csm_BG_Bonn_6ca39d08b6.jpg

csm_BG_Bonn_6ca39d08b6.jpg

800 ms

csm_BG_Knappschaft_042a29075e.jpg

csm_BG_Knappschaft_042a29075e.jpg

820 ms

csm_THC_Refersh-IT_Teaser-BG_73a31c8dfe.jpg

csm_THC_Refersh-IT_Teaser-BG_73a31c8dfe.jpg

857 ms

csm_THC_Download-Teaser_600x300px-31_6b5c1306c4.jpg

csm_THC_Download-Teaser_600x300px-31_6b5c1306c4.jpg

857 ms

csm_THC_Download-Teaser_600x300px-42_280988dbae.jpg

csm_THC_Download-Teaser_600x300px-42_280988dbae.jpg

893 ms

csm_THC_Download-Teaser_600x300px-21_1d03012a4b.jpg

csm_THC_Download-Teaser_600x300px-21_1d03012a4b.jpg

902 ms

kunde2.svg

kunde2.svg

926 ms

starw.svg

starw.svg

945 ms

DT_healtcare_solutions_rgb_n.svg

DT_healtcare_solutions_rgb_n.svg

907 ms

telegrotesknext-regular.woff

telegrotesknext-regular.woff

898 ms

telegrotesknext-thin.woff

telegrotesknext-thin.woff

893 ms

telegrotesknext-ultra.woff

telegrotesknext-ultra.woff

793 ms

icomoon.ttf

icomoon.ttf

743 ms

slick.woff

slick.woff

738 ms

ajax-loader.gif

ajax-loader.gif

689 ms

Accessibility Review

onhealth.de accessibility score

93

Accessibility Issues

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

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

onhealth.de best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

onhealth.de SEO score

92

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onhealth.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Onhealth.de 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

onhealth.de

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