4.4 sec in total
464 ms
3.5 sec
421 ms
Visit weisse-liste.aok-gesundheitsnavi.de now to see the best up-to-date Weisse Liste AOK Gesundheitsnavi content for Germany and also check out these interesting facts you probably never knew about weisse-liste.aok-gesundheitsnavi.de
Geben Sie einfach Ihre Symptome oder Krankheit in unserer Krankenhaussuche ein: Wir informieren über das nächste Fachzentrum & über gesuchte Fachgebiete!
Visit weisse-liste.aok-gesundheitsnavi.deWe analyzed Weisse-liste.aok-gesundheitsnavi.de page load time and found that the first response time was 464 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
weisse-liste.aok-gesundheitsnavi.de performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value15.3 s
0/100
25%
Value11.6 s
5/100
10%
Value250 ms
84/100
30%
Value0.498
16/100
15%
Value14.7 s
8/100
10%
464 ms
99 ms
469 ms
176 ms
266 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Weisse-liste.aok-gesundheitsnavi.de, 3% (3 requests) were made to Navigatoren-cdn.aok.de and 1% (1 request) were made to Browser.sentry-cdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Navigatoren-cdn.aok.de.
Page size can be reduced by 72.8 kB (31%)
231.2 kB
158.4 kB
In fact, the total size of Weisse-liste.aok-gesundheitsnavi.de main page is 231.2 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. 55% of websites need less resources to load. Javascripts take 92.5 kB which makes up the majority of the site volume.
Potential reduce by 58.3 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.9 kB, which is 12% 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 58.3 kB or 76% of the original size.
Potential reduce by 14.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 14.1 kB or 15% of the original size.
Potential reduce by 332 B
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. Weisse-liste.aok-gesundheitsnavi.de has all CSS files already compressed.
Number of requests can be reduced by 78 (96%)
81
3
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weisse Liste AOK Gesundheitsnavi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
464 ms
99 ms
469 ms
base-pk-6404d18c2ae23a9bddda86334e921b8e.css.gzip
176 ms
y000.min-30858f1c7ef0fe71f01b49a231d6bcf7.css.gzip
266 ms
y036.min-55c746d802716aba26d8ed69183d19aa.css.gzip
356 ms
featherlight-theme-aok.min-1797243527fc3fdeb1576fa8eb539091.css.gzip
370 ms
y042.min-b9bfb88c958af8248def61c6139caabd.css.gzip
384 ms
forms.min-c4a09ddd56deb03fa01ac3ea10c709fe.css.gzip
389 ms
y013.min-1dfb822cc76858d1dc6abae36aadf0e4.css.gzip
392 ms
search-form.min-7403620588df50b3045c45368fe7aa57.css.gzip
399 ms
portalsuche-v1.min-fddd66fac6b450bd2c52a973cffcf0ad.css.gzip
444 ms
pagination.min-9efbba485f05c99406ac204f34f5ce2f.css.gzip
457 ms
breadcrumb.min-b730129514377188361e1b5e43e4fdbb.css.gzip
471 ms
jqueryui.min-a8a531afa5541064626699bc811302eb.css.gzip
476 ms
localisation.min-c822c70ec5b98ce9e8181c932e36ba8c.css.gzip
480 ms
k20.min-ca176178a91197721a81c1f748c6bf11.css.gzip
487 ms
y017.min-764b8aee7fa08bce926323149689ba88.css.gzip
531 ms
y015.min-8c0d0258be2a5855d63c78cf6013305d.css.gzip
547 ms
service-menu.min-518560f4c80cfcadeab90b9f3900265b.css.gzip
559 ms
flexslider.min-b90f612d16013aa95a404a5f21f0fa10.css.gzip
564 ms
portalsuche.min-d9c78dd3efb2782cb1f433365041e671.css.gzip
569 ms
header.min-a81a1e302a67ecb7497287f83a540c83.css.gzip
575 ms
y030.min-845b1f5ca066d33618fc1a0e9f588281.css.gzip
621 ms
y037.min-85cb0d8854171f9aca9a3d566659388d.css.gzip
635 ms
y005.min-053e1343c14d34794379fef0065aeae1.css.gzip
648 ms
accordion.min-058abd32725fe23b86157d5571617e68.css.gzip
654 ms
audio.min-324bb8bc863e4c1fd241ba7530c4d951.css.gzip
657 ms
videoPopover.min-c98d89f13cb1b83464f87488cb48476b.css.gzip
663 ms
video.min-6445fd4be78aaaf4e144091cbc64f87e.css.gzip
708 ms
socialMediaPopover.min-cfc184c04172e3f2bc814a8ef6abb70e.css.gzip
723 ms
y008v3.min-861dcb2e43194eb9ea922c6934f9cf9c.css.gzip
736 ms
location-search.min-fcaaf2f4fffeed8d0d01ce8eece9a16a.css.gzip
742 ms
flatpickr.min-176afd1e7edba4a573c0bae615895cc5.css.gzip
745 ms
base.min-d3cba773ed08fac06ed3c0afb2ce5ba1.css.gzip
752 ms
y048.min-24fa1c5a3c2439440e81fbadc5d814bb.css.gzip
799 ms
react.min-0353cd4a8cdfe4f92bcac025e52f281f.js.gzip
824 ms
react-dom.min-cecd2e1681c3bf4e3d496a752c84f8bd.js.gzip
932 ms
bundle.min.js
44 ms
main.chunk.js
1017 ms
runtime-main.js
495 ms
vendor.chunk.js
1098 ms
jquery.min-3e9a6300eb3e86e75051e7d60d89cda1.js.gzip
883 ms
jquery.matchHeight-min-bfe768810d985f85ac1a3544a1537537.js.gzip
682 ms
jquery.actual.min-59cd8e975521f48af7cf2984c6dd5531.js.gzip
598 ms
js.cookie-0a6283da0ab7062299ed79cd30a7ae0b.js.gzip
549 ms
bootstrap.bundle.min-2bfe8f39e1c94713c2a236b99e883f87.js.gzip
625 ms
select2.full.min-bf542c29f47818edc7e5e42ea1d99831.js.gzip
632 ms
featherlight.min-8815a262528f7f324b7e59224bc6d237.js.gzip
596 ms
version-8eb51f887da49a7865835d0c71cc5b00.js.gzip
597 ms
widget-9aa99c51ea9209fbea80eb11edb9a3b3.js.gzip
611 ms
position-106b99610288c58485966effdafe0300.js.gzip
570 ms
keycode-7b6aeae7d1abbb5d1677e8fc55a78238.js.gzip
570 ms
safe-active-element-944eb5d50cf5bc52455e40f1952075ea.js.gzip
605 ms
unique-id-240f7b3888a35d90e0d6c73304bbca7a.js.gzip
607 ms
menu-726f60284116ad0e485dad7b56385b30.js.gzip
616 ms
autocomplete-a038ea76870829fd3b3a6f352d7b7229.js.gzip
614 ms
jquery.flexslider-min-204617c45e04e41d43e3e41307445210.js.gzip
571 ms
flexslider.min-c74d4079d98da0352b615f0b1bd01130.js.gzip
567 ms
accordion-b91d96e74f1b7c473fdd10a2c79985e3.js.gzip
605 ms
videoPopover-2c02d186e014a09dad1762a1f1589c77.js.gzip
606 ms
socialMediaPopover-d087de54be0032cd3369e6436ca83f82.js.gzip
616 ms
location-search.min-4a53f424f412670aa20eafd16abffd80.js.gzip
615 ms
flatpickr.min-a000028ca3991ed733b8791a2606f026.js.gzip
572 ms
de-abf78131df06d809b97bf83244211035.js.gzip
568 ms
trackingCodeReader-810a60bc69d53c955ae9bf12b626b819.js.gzip
604 ms
consentScriptsConfig-769157cc656c87a3b92d4e93b4c96707.js.gzip
604 ms
consent-script-loader.min-af3dc3b2d8a7a8a1eb8005c75a74b5f1.js.gzip
618 ms
cookie-settings-manager.min-ea81a74915cdf57728f40488f6dab026.js.gzip
615 ms
base-98e2e9fc9338c5e0466a19ac35eff96f.js.gzip
657 ms
modules.min-9e61b0f4f337df170de0f69ac5b9f38b.js.gzip
573 ms
jquery.plugin.mindbreezeAutocomplete-bb33dc9ced2bad62e0ba13a0ea3e7a98.js.gzip
605 ms
jquery.plugin.mindbreezeAutocompleteSimple-70784414301c31ff9aa69839a6bbd233.js.gzip
603 ms
mindbreezeLoadMoreButton-a200d77c1bca3d334f2e01b078f03141.js.gzip
616 ms
ajaxUriWrapper-51077518367ce208f8ef317d7c8a8855.js.gzip
698 ms
scrollToElementIfSelectorIsInSessionStorage-1730a74b63ef9a70df385aca64a1a46d.js.gzip
629 ms
press-icon.jquery-33b60161715a4e46201fe042f0bcf4fe.js.gzip
629 ms
localisation.min-da5232721f62cb01130df5d1b5daf2e4.js.gzip
598 ms
reactModules-d4abf57b766e605ca19dce039e54bed0.js.gzip
560 ms
feedback-formular-58c1076e4222f80017b757c36bc48036.js.gzip
561 ms
newsletter-formular-e6d8bb1c43df411f8d23cbc658595513.js.gzip
485 ms
vhs-assets-libs.js
749 ms
vhs-assets-app.js
627 ms
ef7e8467-66c5-4521-afc4-777f6cf72ec4.woff
551 ms
3963cec0-c35f-41fa-adb6-4ef3fc0bb056.woff
564 ms
8b1cbfbd-4fa3-4330-8e32-552125871646.woff
555 ms
aok-icons-functional.woff
543 ms
logo-aok-green.svg
607 ms
weisse-liste.aok-gesundheitsnavi.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
weisse-liste.aok-gesundheitsnavi.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
Page has valid source maps
weisse-liste.aok-gesundheitsnavi.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 Weisse-liste.aok-gesundheitsnavi.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 Weisse-liste.aok-gesundheitsnavi.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.
weisse-liste.aok-gesundheitsnavi.de
Open Graph description is not detected on the main page of Weisse Liste AOK Gesundheitsnavi. 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: