Tools & Wizards About Us
medeligo.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

medeligo.com

MEDELIGO – Oncology Search Tool | FINGERTIP ACCESS TO THE LATEST ONCOLOGY INFORMATION

Page Load Speed

3.5 sec in total

First Response

98 ms

Resources Loaded

1.6 sec

Page Rendered

1.9 sec

medeligo.com screenshot

About Website

Welcome to medeligo.com homepage info - get ready to check MEDELIGO best content right away, or after learning these important things about medeligo.com

Visit medeligo.com

Key Findings

We analyzed Medeligo.com page load time and found that the first response time was 98 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

medeligo.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,100 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

medeligo.com

98 ms

js

77 ms

medeligo.com

239 ms

styles.css

45 ms

form-basic.css

51 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 48% of them (27 requests) were addressed to the original Medeligo.com, 21% (12 requests) were made to Kinstastage.medeligo.com and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (905 ms) relates to the external source Kinstastage.medeligo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (30%)

Content Size

6.5 MB

After Optimization

4.6 MB

  • HTML
  • Images

In fact, the total size of Medeligo.com main page is 6.5 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. 70% of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 140.0 kB

  • Original 164.9 kB
  • After minification 161.5 kB
  • After compression 24.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 140.0 kB or 85% of the original size.

Image Optimization

-29%

Potential reduce by 1.8 MB

  • Original 6.4 MB
  • After minification 4.5 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. Obviously, MEDELIGO needs image optimization as it can save up to 1.8 MB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 27 (57%)

Requests Now

47

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

medeligo.com

medeligo.com

98 ms

js

js

77 ms

medeligo.com

medeligo.com

239 ms

styles.css

styles.css

45 ms

form-basic.css

form-basic.css

51 ms

css

css

41 ms

style.min.css

style.min.css

75 ms

Defaults.css

Defaults.css

38 ms

ultimate.min.css

ultimate.min.css

56 ms

icons.css

icons.css

74 ms

frontend-gtag.min.js

frontend-gtag.min.js

73 ms

jquery.min.js

jquery.min.js

109 ms

rbtools.min.js

rbtools.min.js

110 ms

rs6.min.js

rs6.min.js

111 ms

core.min.js

core.min.js

110 ms

ultimate.min.js

ultimate.min.js

111 ms

ultimate_bg.min.js

ultimate_bg.min.js

113 ms

rs6.css

rs6.css

114 ms

hooks.min.js

hooks.min.js

124 ms

i18n.min.js

i18n.min.js

125 ms

index.js

index.js

133 ms

index.js

index.js

144 ms

magnific-popup.js

magnific-popup.js

143 ms

us.core.min.js

us.core.min.js

169 ms

vhparallax.min.js

vhparallax.min.js

147 ms

white-iphone-12-SS.png

white-iphone-12-SS.png

489 ms

en-us

en-us

275 ms

integrated-logo-1.png

integrated-logo-1.png

87 ms

Solution-ltr.png

Solution-ltr.png

109 ms

heartbeat-full-teal.png

heartbeat-full-teal.png

66 ms

white-iphone-12-tumors.png

white-iphone-12-tumors.png

517 ms

white-iphone-12-general.png

white-iphone-12-general.png

727 ms

white-iphone-12-therapy.png

white-iphone-12-therapy.png

494 ms

white-iphone-12-query.png

white-iphone-12-query.png

523 ms

white-iphone-12-results-list.png

white-iphone-12-results-list.png

510 ms

white-iphone-12-filter.png

white-iphone-12-filter.png

834 ms

white-iphone-12-gallery.png

white-iphone-12-gallery.png

836 ms

white-iphone-12-image.png

white-iphone-12-image.png

859 ms

white-iphone-12-video.png

white-iphone-12-video.png

897 ms

white-iphone-12-article-lancet.png

white-iphone-12-article-lancet.png

905 ms

white-iphone-12-share.png

white-iphone-12-share.png

876 ms

476 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

75 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

86 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

94 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

95 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

84 ms

Defaults.woff

Defaults.woff

221 ms

en-us

en-us

619 ms

widget-5-4e9069de0c32.js

widget-5-4e9069de0c32.js

26 ms

widget-8-3b9d1075e7f6.js

widget-8-3b9d1075e7f6.js

28 ms

widget-9-f6a058e890c6.js

widget-9-f6a058e890c6.js

43 ms

logo-200x120-3190df52.png

logo-200x120-3190df52.png

34 ms

widget-0-a9afc1d1c15e.js

widget-0-a9afc1d1c15e.js

22 ms

widget-1-558f643a25d8.js

widget-1-558f643a25d8.js

21 ms

Accessibility Review

medeligo.com accessibility score

81

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

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

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

Page has valid source maps

SEO Factors

medeligo.com SEO score

91

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

High

Tap targets are not sized appropriately

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

medeligo.com

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