4.2 sec in total
615 ms
3 sec
611 ms
Welcome to onhealth.de homepage info - get ready to check Onhealth best content right away, or after learning these important things about onhealth.de
Wir unterstützen Sie mit ganzheitlichen Lösungen über die komplette Patientenjourney hinweg – für ein zukunftsfähiges digitales Gesundheitswesen.
Visit onhealth.deWe analyzed Onhealth.de page load time and found that the first response time was 615 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
onhealth.de performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value5.2 s
23/100
25%
Value6.3 s
42/100
10%
Value380 ms
70/100
30%
Value0.368
29/100
15%
Value5.4 s
72/100
10%
615 ms
196 ms
270 ms
563 ms
282 ms
Our browser made a total of 53 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 (1.1 sec) relates to the external source Telekom-healthcare.com.
Page size can be reduced by 400.9 kB (14%)
2.9 MB
2.5 MB
In fact, the total size of Onhealth.de main page is 2.9 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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 54.4 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 7.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 54.4 kB or 78% of the original size.
Potential reduce by 346.5 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. Obviously, Onhealth needs image optimization as it can save up to 346.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
We found no issues to fix!
46
46
The browser has sent 46 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.
www.telekom-healthcare.com
615 ms
loader-f0a043e8f1c42a31b66555bb057db17e.css.gzip
196 ms
merged-4f8464576dabaa1b7deec66c386f359d-152ed020305bd985f4a789779563fec6.css.gzip
270 ms
merged-f3bea4b270c94006c48dd94e86d1bfdc-334cc9dea60b529aa4a4142ebc0be75b.js.gzip
563 ms
myscript2.js
282 ms
DT_healtcare_solutions_rgb_p.svg
112 ms
m1-m2.png
458 ms
m2-m1.png
367 ms
m3.png
106 ms
csm_iStock-810600330_8900f410b2.jpg
298 ms
m2.png
273 ms
csm_iStock-695337958_d6b823b89e.jpg
448 ms
csm_GettyImages-578806154_1_5444e1e6e5.jpg
562 ms
csm_Sicherheitszertifikat-konnektor-telekom-healthcare_519f2ba955.jpg
479 ms
csm_Potrait_Gottfried_Ludewig_090322_a5db605546.jpg
397 ms
csm_Kooperation_GoogleCloud_Universitaetsklinik_Telekom_8bab0b0fd2.jpg
470 ms
csm_bi-230912-symbolfoto-digital-identity-barmer_5b699bb4e6.jpg
592 ms
m5.png
545 ms
csm_MSU_8074_a8ec8fca15.jpg
554 ms
csm_VAMED_TELEKOM_d676ba72c4.jpg
568 ms
m1.png
583 ms
csm_1280x720_LinkedIn_A__rzte_WhatsApp_20230426_EEM_20c24fa7aa.jpg
730 ms
csm_TelekomKnappschaftRecare3866x2579-TelekomCom_2874938702.jpg
650 ms
csm_telekom_com_THS_Blutbahnen_RGB_4520e2059d.jpg
662 ms
csm_Telekom_Patientenabrechnung_88ddca9903.jpg
670 ms
csm_TelekomRecare_A_neu_120123_c15c9276b3.jpg
694 ms
csm_THC_Karriere_462e80aad8.jpg
694 ms
csm_video-krankenkassen-telekom-healthcare-teaser_13bad4ff8b.png
1016 ms
heart.svg
764 ms
pulse.svg
771 ms
cloud.svg
793 ms
THC_E-Health_Icon.svg
800 ms
THC_Klinik-IT_Icon_Telematikinfrastruktur.svg
826 ms
csm_THC_Erfolgsgeschichte_Teaser-BG_46ee0c2a5c.jpg
1057 ms
csm_Gemeinsam_360digital__IT-Profis_aus_Kliniken_treiben_Digitalisierung_im_Gesundheitswesen_voran_85eb86b97c.jpg
873 ms
csm_BG_Esslingen_f41ad3a4b0.jpg
897 ms
csm_BG_UKE_Hamburg_7858a586f2.jpg
898 ms
csm_BG_Bonn_6ca39d08b6.jpg
926 ms
csm_BG_Knappschaft_042a29075e.jpg
974 ms
csm_THC_Refersh-IT_Teaser-BG_73a31c8dfe.jpg
1098 ms
csm_THC_Download-Teaser_600x300px-31_6b5c1306c4.jpg
905 ms
telegrotesknext-regular.woff
1003 ms
telegrotesknext-thin.woff
961 ms
telegrotesknext-ultra.woff
934 ms
icomoon.ttf
816 ms
telegrotesknext-regularitalic.woff
800 ms
slick.woff
780 ms
csm_THC_Download-Teaser_600x300px-42_280988dbae.jpg
789 ms
csm_THC_Download-Teaser_600x300px-21_1d03012a4b.jpg
781 ms
kunde2.svg
762 ms
starw.svg
788 ms
DT_healtcare_solutions_rgb_n.svg
725 ms
ajax-loader.gif
736 ms
onhealth.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
onhealth.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
onhealth.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
DE
![]()
DE
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.
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: