Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

Page Load Speed

6.4 sec in total

First Response

456 ms

Resources Loaded

5 sec

Page Rendered

865 ms

About Website

Click here to check amazing Asklepion content. Otherwise, check out these important facts you probably never knew about asklepion.io

Building bridges between projects that integrate technologies for reshaping the future of the global health ecosystem.

Visit asklepion.io

Key Findings

We analyzed Asklepion.io page load time and found that the first response time was 456 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

asklepion.io performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.151

76/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

asklepion.io

456 ms

193 ms

css

46 ms

settings.css

456 ms

bootstrap.min.css

609 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 74% of them (40 requests) were addressed to the original Asklepion.io, 11% (6 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Asklepion.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.1 kB (4%)

Content Size

1.3 MB

After Optimization

1.3 MB

In fact, the total size of Asklepion.io 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 20.8 kB

  • Original 27.5 kB
  • After minification 26.6 kB
  • After compression 6.7 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 20.8 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 19.6 kB

  • Original 1.1 MB
  • After minification 1.1 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. Asklepion images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 724 B

  • Original 146.1 kB
  • After minification 146.1 kB
  • After compression 145.4 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

-17%

Potential reduce by 14.0 kB

  • Original 84.8 kB
  • After minification 84.8 kB
  • After compression 70.8 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. Asklepion.io needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (47%)

Requests Now

43

After Optimization

23

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

Accessibility Review

asklepion.io accessibility score

64

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

Form elements do not have associated labels

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

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

asklepion.io 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

asklepion.io SEO score

98

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asklepion.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Asklepion.io 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 Asklepion. 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: