6.4 sec in total
456 ms
5 sec
865 ms
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.ioWe 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.
asklepion.io performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value9.2 s
1/100
25%
Value8.8 s
16/100
10%
Value120 ms
97/100
30%
Value0.151
76/100
15%
Value9.5 s
30/100
10%
456 ms
193 ms
46 ms
456 ms
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 size can be reduced by 55.1 kB (4%)
1.3 MB
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.
Potential reduce by 20.8 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.
Potential reduce by 19.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. Asklepion images are well optimized though.
Potential reduce by 724 B
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.
Potential reduce by 14.0 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.
Number of requests can be reduced by 20 (47%)
43
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.
asklepion.io
456 ms
193 ms
css
46 ms
settings.css
456 ms
bootstrap.min.css
609 ms
all.css
60 ms
style.css
729 ms
animate.min.css
505 ms
email-decode.min.js
61 ms
jquery.min.js
655 ms
bootstrap.min.js
622 ms
jquery.magnific-popup.min.js
916 ms
imagesloaded.pkgd.min.js
933 ms
jquery.appear.js
1045 ms
owl.carousel.min.js
1045 ms
jquery.stellar.min.js
1096 ms
isotope.pkgd.min.js
1267 ms
main.js
1346 ms
jquery.themepunch.tools.min.js
1620 ms
jquery.themepunch.revolution.min.js
1617 ms
rocket-loader.min.js
1052 ms
logo_asklepion.png
1487 ms
tr.png
1650 ms
buildyourhealth-en.png
1279 ms
coverme-en.png
1993 ms
eseruyanik.jpg
1916 ms
canerokan.jpg
2180 ms
serkansaracci.jpg
2303 ms
musacanminaz.jpg
2182 ms
jolandatermaten.jpg
2351 ms
aysegulbirlik.jpg
2351 ms
opdrmehmet.jpg
2700 ms
afsarakal_1.jpg
2872 ms
arifeunal.jpg
2983 ms
tfb.png
3041 ms
bloxperiment.png
2787 ms
biogena-p.png
3004 ms
yuzyilhastanesi-p.png
3124 ms
logo_asklepion_dark.png
3216 ms
asklepion_static.jpg
2923 ms
asklepion_team.jpg
2948 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
96 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
95 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
101 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
118 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
119 ms
fa-solid-900.woff
52 ms
fa-regular-400.woff
93 ms
fa-brands-400.woff
98 ms
js
121 ms
jquery.min.js
571 ms
analytics.js
24 ms
collect
16 ms
asklepion.io accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
asklepion.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
asklepion.io SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
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.
asklepion.io
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: