Tools & Wizards About Us
aevis.com screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

aevis.com

Home -AEVIS VICTORIA SA – Investing for a better life

Page Load Speed

2.1 sec in total

First Response

99 ms

Resources Loaded

1.9 sec

Page Rendered

100 ms

aevis.com screenshot

About Website

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

AEVIS VICTORIA invests in healthcare, lifestyle and infrastructure. Investments include a group of private hospitals, a digital health organisation and a better aging brand.

Visit aevis.com

Key Findings

We analyzed Aevis.com page load time and found that the first response time was 99 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

aevis.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

99 ms

uc.js

20 ms

style.css

95 ms

styles.css

206 ms

main_4b8e8a8d.css

278 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 51% of them (20 requests) were addressed to the original Aevis.com, 38% (15 requests) were made to Charts3.equitystory.com and 5% (2 requests) were made to Aevis.matomo.cloud. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Aevis.matomo.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.6 kB (43%)

Content Size

727.0 kB

After Optimization

413.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Aevis.com main page is 727.0 kB. 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 624.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 31.4 kB

  • Original 38.8 kB
  • After minification 35.0 kB
  • After compression 7.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. 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 31.4 kB or 81% of the original size.

JavaScript Optimization

-43%

Potential reduce by 270.5 kB

  • Original 624.9 kB
  • After minification 624.9 kB
  • After compression 354.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 270.5 kB or 43% of the original size.

CSS Optimization

-18%

Potential reduce by 11.7 kB

  • Original 63.3 kB
  • After minification 63.3 kB
  • After compression 51.6 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. Aevis.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (68%)

Requests Now

22

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

99 ms

uc.js

uc.js

20 ms

style.css

style.css

95 ms

styles.css

styles.css

206 ms

main_4b8e8a8d.css

main_4b8e8a8d.css

278 ms

language-cookie.js

language-cookie.js

278 ms

jquery.min.js

jquery.min.js

370 ms

jquery.validate.min.js

jquery.validate.min.js

290 ms

loader.js

loader.js

455 ms

main_4b8e8a8d.js

main_4b8e8a8d.js

434 ms

matomo.js

matomo.js

94 ms

eHuqYWvR-aevis_logo-1.svg

eHuqYWvR-aevis_logo-1.svg

166 ms

7vEKP85G-aevis_logo_negative.svg

7vEKP85G-aevis_logo_negative.svg

170 ms

roboto700_adcde98f.woff

roboto700_adcde98f.woff

97 ms

roboto900_bb1e4dc6.woff

roboto900_bb1e4dc6.woff

93 ms

roboto500_87284894.woff

roboto500_87284894.woff

96 ms

roboto400_60fa3c06.woff

roboto400_60fa3c06.woff

106 ms

roboto300_b00849e0.woff

roboto300_b00849e0.woff

192 ms

roboto100_5cb7edfc.woff

roboto100_5cb7edfc.woff

189 ms

icomoon_1aa930bb.woff

icomoon_1aa930bb.woff

202 ms

robotocondensed400_5c7a07a5.woff

robotocondensed400_5c7a07a5.woff

192 ms

robotocondensed300_b8f4e373.woff

robotocondensed300_b8f4e373.woff

205 ms

robotocondensed700_2b92236b.woff

robotocondensed700_2b92236b.woff

212 ms

249 ms

matomo.php

matomo.php

486 ms

configs.php

configs.php

390 ms

common.css

common.css

95 ms

main.css

main.css

188 ms

libs.js

libs.js

386 ms

main.js

main.js

279 ms

common-v3.1.0.min.js

common-v3.1.0.min.js

279 ms

iframeResizer.contentWindow.min.js

iframeResizer.contentWindow.min.js

280 ms

loading.gif

loading.gif

95 ms

Roboto-Bold.woff

Roboto-Bold.woff

186 ms

Roboto-Black.woff

Roboto-Black.woff

271 ms

Roboto-Medium.woff

Roboto-Medium.woff

270 ms

Roboto-Regular.woff

Roboto-Regular.woff

270 ms

Roboto-Light.woff

Roboto-Light.woff

280 ms

Roboto-Thin.woff

Roboto-Thin.woff

280 ms

Accessibility Review

aevis.com accessibility score

85

Accessibility Issues

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

High

Links do not have a discernible name

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

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

aevis.com SEO score

100

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

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

aevis.com

Open Graph data is detected on the main page of AEVIS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: