3.6 sec in total
303 ms
3.1 sec
264 ms
Click here to check amazing Aexis content. Otherwise, check out these important facts you probably never knew about aexis.com
We help you with your journey to digitalisation by offering the right corporate performance management solution for your business.
Visit aexis.comWe analyzed Aexis.com page load time and found that the first response time was 303 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.
aexis.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value20.6 s
0/100
25%
Value11.9 s
4/100
10%
Value1,720 ms
10/100
30%
Value0.141
78/100
15%
Value18.9 s
3/100
10%
303 ms
443 ms
25 ms
491 ms
378 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 57% of them (47 requests) were addressed to the original Aexis.com, 12% (10 requests) were made to O.twimg.com and 7% (6 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Aexis.com.
Page size can be reduced by 465.8 kB (24%)
1.9 MB
1.5 MB
In fact, the total size of Aexis.com main page is 1.9 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.5 MB which makes up the majority of the site volume.
Potential reduce by 22.1 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 22.1 kB or 76% of the original size.
Potential reduce by 142.2 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. Aexis images are well optimized though.
Potential reduce by 104.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 104.7 kB or 58% of the original size.
Potential reduce by 196.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. Aexis.com needs all CSS files to be minified and compressed as it can save up to 196.8 kB or 86% of the original size.
Number of requests can be reduced by 26 (35%)
75
49
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aexis. 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 10 to 1 for CSS and as a result speed up the page load time.
aexis.com
303 ms
www.aexis.com
443 ms
css
25 ms
style.css
491 ms
responsive.css
378 ms
flexslider.css
190 ms
prettyPhoto.css
289 ms
jquery.min.js
485 ms
jquery.flexslider-min.js
291 ms
jquery.bxSlider.min.js
385 ms
jquery.prettyPhoto.js
583 ms
js_func.js
519 ms
AexisGroup-NewsEventsAexisBelgium
70 ms
classic-081711.css
24 ms
ga.js
44 ms
index2_bg.png
101 ms
logo.png
245 ms
corpeumlogo.png
242 ms
ibmlogo.jpg
243 ms
infor-sidebar.png
285 ms
social_shadow.png
242 ms
spritewhite.png
307 ms
sprite.png
380 ms
moover_bg.png
558 ms
moover_shadow.png
555 ms
slider2.jpg
777 ms
slider3.jpg
947 ms
slider4.jpg
968 ms
block1-Alliance.jpg
773 ms
block2.jpg
929 ms
block6.jpg
945 ms
kbc.png
967 ms
kinepolis.png
1059 ms
colruyt.png
1118 ms
vw.png
1134 ms
sncf.jpg
1135 ms
roularta.png
1150 ms
makro.png
1152 ms
bacardi.png
1247 ms
albron.png
1307 ms
ingram.png
1325 ms
babyliss.jpg
1327 ms
antwerpen.png
1341 ms
social_bg.png
1344 ms
white_dot.png
1438 ms
greyback.png
1497 ms
logowhite.png
1516 ms
widgets.js
211 ms
whiteheader.png
1497 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
60 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
62 ms
buzzboost-pwrd.gif
24 ms
__utm.gif
39 ms
jquery.form-n-validate.js
37 ms
zoom.png
1451 ms
bg_direction_nav.png
1642 ms
bg_direction_nav.png
1548 ms
widget_v2.134.js
59 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
140 ms
syndication
80 ms
304197689032179712
166 ms
proxy.jpg
32 ms
proxy.jpg
44 ms
proxy.jpg
38 ms
proxy.jpg
38 ms
proxy.jpg
37 ms
proxy.jpg
38 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
40 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
143 ms
3cf068f32ec8479c5c7bc6531451a578_normal.png
198 ms
logo_Corpeum_normal.jpg
305 ms
HmM48RpN_normal.png
311 ms
Mv4fgDci_normal.jpg
320 ms
72e602a718a9cc1eed74bd1b6308470c_normal.jpeg
322 ms
B3SNZ-GIUAAWMz9.jpg:small
340 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
18 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
80 ms
proxy.jpg
6 ms
proxy.jpg
4 ms
proxy.jpg
4 ms
proxy.jpg
3 ms
jot.html
36 ms
aexis.com 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
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
aexis.com 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
Uses deprecated APIs
aexis.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aexis.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 Aexis.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.
aexis.com
Open Graph description is not detected on the main page of Aexis. 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: