Tools & Wizards About Us
wehling-hartmann.de screenshot

Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wehling-hartmann.de

Dr. Wehling & Partner - Regenerative Orthopedics and Pain Medicine

Page Load Speed

2.3 sec in total

First Response

262 ms

Resources Loaded

1.7 sec

Page Rendered

352 ms

wehling-hartmann.de screenshot

About Website

Click here to check amazing Wehling Hartmann content. Otherwise, check out these important facts you probably never knew about wehling-hartmann.de

Dr. Peter Wehling is the inventor of the Regenokine® Program and specialist for regenerative orthopedics, sports medicine and pain management from Düsseldorf, Germany.

Visit wehling-hartmann.de

Key Findings

We analyzed Wehling-hartmann.de page load time and found that the first response time was 262 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wehling-hartmann.de performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

wehling-hartmann.de

262 ms

doctor-wehling.com

614 ms

cookie-law-info-public.css

104 ms

cookie-law-info-gdpr.css

210 ms

style.css

271 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wehling-hartmann.de, 67% (36 requests) were made to Fonts.gstatic.com and 31% (17 requests) were made to Doctor-wehling.com. The less responsive or slowest element that took the longest time to load (614 ms) relates to the external source Doctor-wehling.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.5 kB (20%)

Content Size

850.4 kB

After Optimization

677.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wehling-hartmann.de main page is 850.4 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. 50% of websites need less resources to load. Images take 530.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 163.3 kB

  • Original 197.4 kB
  • After minification 196.9 kB
  • After compression 34.1 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 163.3 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 8.6 kB

  • Original 530.6 kB
  • After minification 522.1 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. Wehling Hartmann images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 245 B

  • Original 114.1 kB
  • After minification 114.1 kB
  • After compression 113.9 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

-16%

Potential reduce by 1.3 kB

  • Original 8.3 kB
  • After minification 8.3 kB
  • After compression 6.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. Wehling-hartmann.de needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (60%)

Requests Now

15

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wehling-hartmann.de

wehling-hartmann.de

262 ms

doctor-wehling.com

doctor-wehling.com

614 ms

cookie-law-info-public.css

cookie-law-info-public.css

104 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

210 ms

style.css

style.css

271 ms

jquery.min.js

jquery.min.js

362 ms

jquery-migrate.min.js

jquery-migrate.min.js

281 ms

cookie-law-info-public.js

cookie-law-info-public.js

280 ms

et-core-unified-72.min.css

et-core-unified-72.min.css

292 ms

script.js

script.js

308 ms

scripts.min.js

scripts.min.js

546 ms

common.js

common.js

469 ms

logo-wehling.png

logo-wehling.png

113 ms

sprinter-1.jpg

sprinter-1.jpg

288 ms

wehling-peter.jpg

wehling-peter.jpg

392 ms

couple-making-yoga.jpg

couple-making-yoga.jpg

359 ms

et-divi-dynamic-tb-1182-72-late.css

et-divi-dynamic-tb-1182-72-late.css

99 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

22 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

29 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

28 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

25 ms

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

27 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

28 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

28 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

29 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

31 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

33 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

32 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

32 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

33 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

33 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

34 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

33 ms

pxiGyp8kv8JHgFVrLPTucHtG.woff

pxiGyp8kv8JHgFVrLPTucHtG.woff

36 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

36 ms

pxiDyp8kv8JHgFVrJJLm21lVF9eI.woff

pxiDyp8kv8JHgFVrJJLm21lVF9eI.woff

37 ms

pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf

pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf

37 ms

pxiDyp8kv8JHgFVrJJLmv1pVF9eI.woff

pxiDyp8kv8JHgFVrJJLmv1pVF9eI.woff

38 ms

pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf

pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf

38 ms

pxiAyp8kv8JHgFVrJJLmE0tCMPQ.woff

pxiAyp8kv8JHgFVrJJLmE0tCMPQ.woff

39 ms

pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf

pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf

37 ms

pxiGyp8kv8JHgFVrJJLucHtG.woff

pxiGyp8kv8JHgFVrJJLucHtG.woff

38 ms

pxiGyp8kv8JHgFVrJJLucHtF.ttf

pxiGyp8kv8JHgFVrJJLucHtF.ttf

39 ms

pxiDyp8kv8JHgFVrJJLmg1hVF9eI.woff

pxiDyp8kv8JHgFVrJJLmg1hVF9eI.woff

41 ms

pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf

pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf

41 ms

pxiDyp8kv8JHgFVrJJLmr19VF9eI.woff

pxiDyp8kv8JHgFVrJJLmr19VF9eI.woff

42 ms

pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf

43 ms

pxiDyp8kv8JHgFVrJJLmy15VF9eI.woff

pxiDyp8kv8JHgFVrJJLmy15VF9eI.woff

41 ms

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

42 ms

pxiDyp8kv8JHgFVrJJLm111VF9eI.woff

pxiDyp8kv8JHgFVrJJLm111VF9eI.woff

42 ms

pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf

pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf

43 ms

pxiDyp8kv8JHgFVrJJLm81xVF9eI.woff

pxiDyp8kv8JHgFVrJJLm81xVF9eI.woff

43 ms

pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf

pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf

44 ms

modules.woff

modules.woff

215 ms

Accessibility Review

wehling-hartmann.de accessibility score

84

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.

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

wehling-hartmann.de 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

SEO Factors

wehling-hartmann.de SEO score

93

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 uses 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 Wehling-hartmann.de 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 Wehling-hartmann.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

wehling-hartmann.de

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