3.7 sec in total
352 ms
2.3 sec
985 ms
Click here to check amazing Healios content. Otherwise, check out these important facts you probably never knew about healios.io
A medical technology company enabling precision medicine to become a reality in neuroscience research and development
Visit healios.ioWe analyzed Healios.io page load time and found that the first response time was 352 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
healios.io performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.8 s
15/100
25%
Value7.7 s
24/100
10%
Value240 ms
85/100
30%
Value0.021
100/100
15%
Value11.8 s
17/100
10%
352 ms
393 ms
500 ms
70 ms
186 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Healios.io, 77% (20 requests) were made to Indivi.io and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source Indivi.io.
Page size can be reduced by 288.6 kB (12%)
2.4 MB
2.1 MB
In fact, the total size of Healios.io main page is 2.4 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 37.3 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 6.5 kB, which is 13% 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 37.3 kB or 75% of the original size.
Potential reduce by 172.5 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. Healios images are well optimized though.
Potential reduce by 77.0 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 77.0 kB or 54% of the original size.
Potential reduce by 1.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. Healios.io has all CSS files already compressed.
Number of requests can be reduced by 8 (38%)
21
13
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Healios. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
healios.io
352 ms
healios.io
393 ms
indivi.io
500 ms
js
70 ms
script.js
186 ms
style.min.css
112 ms
bootstrap.min.css
234 ms
style.css
329 ms
css2
41 ms
script.js
326 ms
bootstrap.bundle.min.js
507 ms
index.js
324 ms
index.js
325 ms
log
444 ms
1-1.png
365 ms
Angela-e1709221337185.png
454 ms
iPhone-12-Pro-Max-14-e1709122077248.png
184 ms
section_3_callout_3_image-e1709122159120.png
183 ms
indivi-rc2nb-logos.png
94 ms
callout-1-image-1.png
455 ms
callout-2-image.jpg
557 ms
image-1.png
546 ms
Frame-17-1-scaled.jpg
457 ms
footer-image.png
456 ms
logo--bsi-certified.png
544 ms
OverusedGrotesk-VF.ttf
484 ms
healios.io accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
healios.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
healios.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healios.io 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 Healios.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.
healios.io
Open Graph data is detected on the main page of Healios. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: