Tools & Wizards About Us
medeor.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

medeor.org

action medeor – Die Notapotheke der Welt

Page Load Speed

6 sec in total

First Response

289 ms

Resources Loaded

5.4 sec

Page Rendered

303 ms

medeor.org screenshot

About Website

Visit medeor.org now to see the best up-to-date Medeor content and also check out these interesting facts you probably never knew about medeor.org

Als Notapotheke der Welt verbessert das Medikamentenhilfswerk action medeor den Zugang zu einer medizinischen Grundversorgung für Menschen in Not.

Visit medeor.org

Key Findings

We analyzed Medeor.org page load time and found that the first response time was 289 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

medeor.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.599

11/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

medeor.org

289 ms

medeor.de

353 ms

625 ms

template.css

98 ms

jquery.min.js

306 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Medeor.org, 85% (35 requests) were made to Medeor.de and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Medeor.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 390.6 kB (53%)

Content Size

740.1 kB

After Optimization

349.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Medeor.org main page is 740.1 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. 15% of websites need less resources to load. Javascripts take 352.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 76.0 kB

  • Original 96.0 kB
  • After minification 92.4 kB
  • After compression 19.9 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.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 3.0 kB

  • Original 208.5 kB
  • After minification 205.6 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. Medeor images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 242.8 kB

  • Original 352.9 kB
  • After minification 316.6 kB
  • After compression 110.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 242.8 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 68.8 kB

  • Original 82.7 kB
  • After minification 60.5 kB
  • After compression 13.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. Medeor.org needs all CSS files to be minified and compressed as it can save up to 68.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (45%)

Requests Now

38

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

medeor.org

medeor.org

289 ms

medeor.de

medeor.de

353 ms

625 ms

template.css

template.css

98 ms

jquery.min.js

jquery.min.js

306 ms

jquery-noconflict.js

jquery-noconflict.js

289 ms

jquery-migrate.min.js

jquery-migrate.min.js

296 ms

bootstrap.min.js

bootstrap.min.js

396 ms

j2store.namespace.js

j2store.namespace.js

299 ms

j2storejqui.js

j2storejqui.js

661 ms

jquery-ui-timepicker-addon.js

jquery-ui-timepicker-addon.js

486 ms

j2store.js

j2store.js

393 ms

template-online.css

template-online.css

503 ms

flaticon.css

flaticon.css

404 ms

medeor.js

medeor.js

492 ms

1d5762.js

1d5762.js

359 ms

picturefill.js

picturefill.js

492 ms

analytics.js

analytics.js

34 ms

visitor.js

visitor.js

355 ms

medeor-logo-de.svg

medeor-logo-de.svg

101 ms

adh.png

adh.png

104 ms

Transparente_Zivilgesellsch.png

Transparente_Zivilgesellsch.png

100 ms

spendenrat.png

spendenrat.png

100 ms

Mother-of-Mercy_2.jpg

Mother-of-Mercy_2.jpg

382 ms

Idomeni1_s.jpg

Idomeni1_s.jpg

101 ms

Buergerkrieg-Syrien-2014-Ankunft-action-medeor-Medikamente-11_s.JPG

Buergerkrieg-Syrien-2014-Ankunft-action-medeor-Medikamente-11_s.JPG

193 ms

Anlassspenden_s.jpg

Anlassspenden_s.jpg

180 ms

erklaerfilm-action-medeor.jpg

erklaerfilm-action-medeor.jpg

193 ms

3-Togo2013-1340_s.jpg

3-Togo2013-1340_s.jpg

184 ms

Schiefner_s.jpg

Schiefner_s.jpg

209 ms

orient_hospital_s.jpg

orient_hospital_s.jpg

280 ms

IMG_3554_s.JPG

IMG_3554_s.JPG

282 ms

aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff

aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff

384 ms

flaticon.woff

flaticon.woff

290 ms

743 ms

collect

collect

11 ms

842088d0-1ae2-40d0-8561-3c95761ba7a6.woff

842088d0-1ae2-40d0-8561-3c95761ba7a6.woff

430 ms

print.css

print.css

100 ms

301 ms

1707 ms

collect

collect

2 ms

Accessibility Review

medeor.org accessibility score

88

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

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

Links do not have a discernible name

Best Practices

medeor.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

medeor.org SEO score

91

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

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 Medeor.org 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 Medeor.org 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

medeor.org

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