Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

esmo.org

European Society for Medical Oncology

Page Load Speed

2.9 sec in total

First Response

270 ms

Resources Loaded

2.4 sec

Page Rendered

242 ms

esmo.org screenshot

About Website

Visit esmo.org now to see the best up-to-date Esmo content for United States and also check out these interesting facts you probably never knew about esmo.org

ESMO is the European Society for Medical Oncology, providing a professional network for its members and working with national societies across Europe.

Visit esmo.org

Key Findings

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

Performance Metrics

esmo.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

esmo.org

270 ms

www.esmo.org

938 ms

font-awesome.min.css

29 ms

12560cbdf7cedfbcb90605a5276eadc4_1456743346_screen_print.css

317 ms

recaptcha_ajax.js

29 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 65% of them (28 requests) were addressed to the original Esmo.org, 7% (3 requests) were made to Google-analytics.com and 5% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (938 ms) belongs to the original domain Esmo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (60%)

Content Size

2.3 MB

After Optimization

920.0 kB

In fact, the total size of Esmo.org main page is 2.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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 89.0 kB

  • Original 102.4 kB
  • After minification 51.0 kB
  • After compression 13.4 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. This page needs HTML code to be minified as it can gain 51.4 kB, which is 50% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 89.0 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 25.7 kB

  • Original 512.4 kB
  • After minification 486.7 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. Esmo images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 882.0 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 341.7 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 882.0 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 392.1 kB

  • Original 470.3 kB
  • After minification 457.7 kB
  • After compression 78.2 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. Esmo.org needs all CSS files to be minified and compressed as it can save up to 392.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (32%)

Requests Now

37

After Optimization

25

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

Accessibility Review

esmo.org accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

esmo.org SEO score

84

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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