Tools & Wizards About Us
vitalsana.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

vitalsana.com

VITALSANA Versandapotheke wird zu DocMorris - DocMorris

Page Load Speed

1.9 sec in total

First Response

43 ms

Resources Loaded

1.6 sec

Page Rendered

245 ms

vitalsana.com screenshot

About Website

Welcome to vitalsana.com homepage info - get ready to check VITALSANA best content for Germany right away, or after learning these important things about vitalsana.com

Die Apotheken Vitalsana und DocMorris vereinen sich. Informieren Sie sich hier über Ihre Vorteile bei DocMorris.

Visit vitalsana.com

Key Findings

We analyzed Vitalsana.com page load time and found that the first response time was 43 ms and then it took 1.9 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

vitalsana.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value2,300 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

vitalsana.com

43 ms

www.docmorris.de

161 ms

vitalsana

21 ms

vitalsana

726 ms

ec911fe23d7a315b.css

24 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Vitalsana.com, 97% (33 requests) were made to Docmorris.de. The less responsive or slowest element that took the longest time to load (726 ms) relates to the external source Docmorris.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.8 kB (8%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Vitalsana.com main page is 1.3 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 76.1 kB

  • Original 95.4 kB
  • After minification 95.2 kB
  • After compression 19.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. 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 76.1 kB or 80% of the original size.

JavaScript Optimization

-0%

Potential reduce by 327 B

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.2 MB

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

-90%

Potential reduce by 32.4 kB

  • Original 36.0 kB
  • After minification 3.6 kB
  • After compression 3.6 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. Vitalsana.com needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (83%)

Requests Now

30

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vitalsana.com

vitalsana.com

43 ms

www.docmorris.de

www.docmorris.de

161 ms

vitalsana

vitalsana

21 ms

vitalsana

vitalsana

726 ms

ec911fe23d7a315b.css

ec911fe23d7a315b.css

24 ms

70ba9e3a2d4fc4f7.css

70ba9e3a2d4fc4f7.css

36 ms

b4b5dc03e7d4a40d.css

b4b5dc03e7d4a40d.css

38 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

361 ms

webpack-1f67bed861aee9fe.js

webpack-1f67bed861aee9fe.js

64 ms

framework-06a5c7f945c292f9.js

framework-06a5c7f945c292f9.js

65 ms

main-4aa80a8172db8620.js

main-4aa80a8172db8620.js

66 ms

_app-c0b502bf00714efc.js

_app-c0b502bf00714efc.js

109 ms

195-91d7714432a7def6.js

195-91d7714432a7def6.js

398 ms

7556-812ae2baa0a153d1.js

7556-812ae2baa0a153d1.js

66 ms

7084-3ca29fc1320dabe2.js

7084-3ca29fc1320dabe2.js

399 ms

9099-fb873ad1a6bf4b74.js

9099-fb873ad1a6bf4b74.js

68 ms

5724-49b453eb7b909814.js

5724-49b453eb7b909814.js

109 ms

6577-60b2bbf16509d559.js

6577-60b2bbf16509d559.js

89 ms

1551-f33cfdd57e644618.js

1551-f33cfdd57e644618.js

417 ms

234-6fae07147b256f82.js

234-6fae07147b256f82.js

430 ms

1553-ca62c321d51a024f.js

1553-ca62c321d51a024f.js

435 ms

7127-e73f6aa38d8cf696.js

7127-e73f6aa38d8cf696.js

403 ms

8466-1ed0a5ee74440d2b.js

8466-1ed0a5ee74440d2b.js

404 ms

2641-368d8ebb66b89df8.js

2641-368d8ebb66b89df8.js

404 ms

6015-80c34b8b6b932e49.js

6015-80c34b8b6b932e49.js

405 ms

1327-25fcbc1d13c9d6d0.js

1327-25fcbc1d13c9d6d0.js

404 ms

8871-e4df351af4916d95.js

8871-e4df351af4916d95.js

413 ms

1723-1003005ebd561804.js

1723-1003005ebd561804.js

424 ms

3104-40200388d925e9f1.js

3104-40200388d925e9f1.js

425 ms

9956-c55badedbc8340a6.js

9956-c55badedbc8340a6.js

431 ms

%5B...slug%5D-aca8e664f06455e9.js

%5B...slug%5D-aca8e664f06455e9.js

458 ms

_buildManifest.js

_buildManifest.js

460 ms

_ssgManifest.js

_ssgManifest.js

463 ms

logo.svg

logo.svg

459 ms

Accessibility Review

vitalsana.com accessibility score

100

Accessibility Issues

Best Practices

vitalsana.com 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

Missing source maps for large first-party JavaScript

SEO Factors

vitalsana.com SEO score

100

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vitalsana.com 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 Vitalsana.com 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

vitalsana.com

Open Graph description is not detected on the main page of VITALSANA. 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: