Tools & Wizards About Us
schwitzen.de screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

schwitzen.de

Hyperhidrose - übermäßiges Schwitzen - starkes Schwitzen

Page Load Speed

9 sec in total

First Response

274 ms

Resources Loaded

7.4 sec

Page Rendered

1.4 sec

schwitzen.de screenshot

About Website

Click here to check amazing Schwitzen content. Otherwise, check out these important facts you probably never knew about schwitzen.de

Deutsches Hyperhidrosezentrum DHHZ München behandelt Hyperhidrose d.h. übermäßiges, starkes Schwitzen. Termin und Fragen 089 / 2727 2012

Visit schwitzen.de

Key Findings

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

Performance Metrics

schwitzen.de performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.313

37/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

www.dhhz.de

274 ms

dhhz.de

695 ms

js

63 ms

sgcm-fe.css

300 ms

sgcm-design.css

318 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Schwitzen.de, 6% (5 requests) were made to Googletagmanager.com and 1% (1 request) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Dhhz.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.2 kB (7%)

Content Size

3.2 MB

After Optimization

3.0 MB

  • HTML
  • Images

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

HTML Optimization

-85%

Potential reduce by 209.3 kB

  • Original 246.5 kB
  • After minification 238.2 kB
  • After compression 37.2 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 209.3 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 20.9 kB

  • Original 3.0 MB
  • After minification 3.0 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. Schwitzen images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 56 (65%)

Requests Now

86

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.dhhz.de

www.dhhz.de

274 ms

dhhz.de

dhhz.de

695 ms

js

js

63 ms

sgcm-fe.css

sgcm-fe.css

300 ms

sgcm-design.css

sgcm-design.css

318 ms

style.min.css

style.min.css

309 ms

style.min.css

style.min.css

313 ms

cms-navigation-base.css

cms-navigation-base.css

321 ms

cms-navigation.css

cms-navigation.css

318 ms

style.min.css

style.min.css

405 ms

theme.min.css

theme.min.css

408 ms

header-footer.min.css

header-footer.min.css

421 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

524 ms

post-6.css

post-6.css

425 ms

elementor-icons.min.css

elementor-icons.min.css

436 ms

swiper.min.css

swiper.min.css

517 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

510 ms

global.css

global.css

531 ms

post-15.css

post-15.css

536 ms

post-838.css

post-838.css

543 ms

post-852.css

post-852.css

611 ms

ecs-style.css

ecs-style.css

625 ms

post-1480.css

post-1480.css

624 ms

font.css

font.css

645 ms

fontawesome.min.css

fontawesome.min.css

654 ms

brands.min.css

brands.min.css

660 ms

solid.min.css

solid.min.css

715 ms

language-cookie.js

language-cookie.js

729 ms

frontend-gtag.min.js

frontend-gtag.min.js

731 ms

jquery.min.js

jquery.min.js

867 ms

jquery-migrate.min.js

jquery-migrate.min.js

763 ms

js

js

53 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

774 ms

ecs.js

ecs.js

816 ms

js

js

75 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

830 ms

widget-loop-builder.min.css

widget-loop-builder.min.css

751 ms

widget-posts.min.css

widget-posts.min.css

884 ms

post-3128.css

post-3128.css

884 ms

sgcm-fe-app.js

sgcm-fe-app.js

885 ms

sgcm-fe-script.js

sgcm-fe-script.js

799 ms

hello-frontend.min.js

hello-frontend.min.js

767 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

759 ms

imagesloaded.min.js

imagesloaded.min.js

754 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

752 ms

webpack.runtime.min.js

webpack.runtime.min.js

750 ms

frontend-modules.min.js

frontend-modules.min.js

750 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

707 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

705 ms

wp-polyfill.min.js

wp-polyfill.min.js

692 ms

hooks.min.js

hooks.min.js

688 ms

i18n.min.js

i18n.min.js

701 ms

frontend.min.js

frontend.min.js

649 ms

waypoints.min.js

waypoints.min.js

691 ms

core.min.js

core.min.js

677 ms

frontend.min.js

frontend.min.js

678 ms

elements-handlers.min.js

elements-handlers.min.js

677 ms

jquery.sticky.min.js

jquery.sticky.min.js

698 ms

js

js

98 ms

js

js

94 ms

maxresdefault.jpg

maxresdefault.jpg

193 ms

Hauptlogo-1.svg

Hauptlogo-1.svg

348 ms

de.svg

de.svg

400 ms

en.svg

en.svg

396 ms

Hero-Image-768x712.png

Hero-Image-768x712.png

603 ms

Hero-Image.png

Hero-Image.png

814 ms

Gluckliche-Frau-1-e1701684466158-1024x1007.png

Gluckliche-Frau-1-e1701684466158-1024x1007.png

1103 ms

6B9E9995-F890-48A5-86A2-B107391DF0A6-e1700484394704.png

6B9E9995-F890-48A5-86A2-B107391DF0A6-e1700484394704.png

738 ms

Vorort.png

Vorort.png

793 ms

unnamed-1.png

unnamed-1.png

508 ms

4.png

4.png

619 ms

1.png

1.png

713 ms

2.png

2.png

726 ms

5.png

5.png

825 ms

9.png

9.png

832 ms

3.png

3.png

779 ms

7.png

7.png

832 ms

8.png

8.png

858 ms

6.png

6.png

864 ms

PD-Dr-Schick-DHHZ-1-768x1022.jpg

PD-Dr-Schick-DHHZ-1-768x1022.jpg

895 ms

App-hand-e1701684649128-768x742.png

App-hand-e1701684649128-768x742.png

904 ms

6B9E9995-F890-48A5-86A2-B107391DF0A6-e1700484394704-300x196.png

6B9E9995-F890-48A5-86A2-B107391DF0A6-e1700484394704-300x196.png

860 ms

5.10.23-UGC-draromycampos-IG-IS-DE_IG-300x300.png

5.10.23-UGC-draromycampos-IG-IS-DE_IG-300x300.png

889 ms

Design-ohne-Titel-13-e1700483657788-300x195.png

Design-ohne-Titel-13-e1700483657788-300x195.png

890 ms

Ery-768x581.png

Ery-768x581.png

1064 ms

Ery.png

Ery.png

961 ms

Hauptlogo.png

Hauptlogo.png

949 ms

SeoGoal_Logo.png

SeoGoal_Logo.png

957 ms

fa-brands-400.woff

fa-brands-400.woff

945 ms

fa-solid-900.woff

fa-solid-900.woff

995 ms

Accessibility Review

schwitzen.de accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

schwitzen.de best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

schwitzen.de SEO score

85

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

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

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 Schwitzen.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 Schwitzen.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

schwitzen.de

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