4.1 sec in total
249 ms
3.6 sec
224 ms
Visit axi.be now to see the best up-to-date AXI content for Belgium and also check out these interesting facts you probably never knew about axi.be
AXI is een allround IT partner die strategisch denkt en werkt. We helpen u de digitalisering toe te passen in uw dagelijkse realiteit.
Visit axi.beWe analyzed Axi.be page load time and found that the first response time was 249 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
axi.be performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value18.5 s
0/100
25%
Value11.8 s
4/100
10%
Value610 ms
48/100
30%
Value0.01
100/100
15%
Value17.8 s
4/100
10%
249 ms
517 ms
190 ms
193 ms
201 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 90% of them (18 requests) were addressed to the original Axi.be, 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Axi.be.
Page size can be reduced by 305.5 kB (30%)
1.0 MB
720.9 kB
In fact, the total size of Axi.be main page is 1.0 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. Only 10% of websites need less resources to load. Images take 767.1 kB which makes up the majority of the site volume.
Potential reduce by 16.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. This page needs HTML code to be minified as it can gain 3.0 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 16.8 kB or 73% of the original size.
Potential reduce by 122.8 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. Obviously, AXI needs image optimization as it can save up to 122.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 120.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 120.0 kB or 67% of the original size.
Potential reduce by 45.9 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. Axi.be needs all CSS files to be minified and compressed as it can save up to 45.9 kB or 79% of the original size.
Number of requests can be reduced by 6 (43%)
14
8
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AXI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
axi.be
249 ms
517 ms
css_rEI_5cK_B9hB4So2yZUtr5weuEV3heuAllCDE6XsIkI.css
190 ms
css_jRj8b6s17tUHHJ2TAk0YJut_fpSxj1NvP7M0BBgGYzY.css
193 ms
css__Diysw7_hbcRTgXlEiXDIxUj61PsN_V7Maii9vcvHSQ.css
201 ms
css_LsF49gMYv4zUyowsbkSspYmIqSTB9RD_XeyNDxJaknc.css
403 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
540 ms
js_-41xCKSys7Scdzd_V0EYxabKC5IcA10_4nwMmzUFY2c.js
331 ms
js_C5YgIPZudQ9JsZgnJ4FuAJCu4WHRFcULW4U49eyBocw.js
284 ms
analytics.js
86 ms
logo.png
105 ms
Banner_Home_jan16_0.png
2258 ms
circle1-arrow-white.png
98 ms
Logo-NMBS-Logistics_0_0.png
115 ms
Banner_Nieuw_Pand_Breda.png
1720 ms
1ff86dd4-d3b2-4325-89bc-c6eb493cedba.woff
291 ms
4e7b2126-77d3-4e53-810d-7ccfde46450a.woff
376 ms
a2627bb2-ea46-4fd0-8a37-d2388fb180b1.woff
319 ms
5eb34b29-e99d-441a-b53f-33ccd73ae841.woff
334 ms
collect
11 ms
axi.be 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.
axi.be 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
axi.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Axi.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Axi.be 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.
axi.be
Open Graph description is not detected on the main page of AXI. 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: