10.7 sec in total
277 ms
5.4 sec
5 sec
Visit egencia.be now to see the best up-to-date Egencia content for Belgium and also check out these interesting facts you probably never knew about egencia.be
Discover corporate travel management solutions that suit any business, large or small. Egencia is making business travel easier — and better.
Visit egencia.beWe analyzed Egencia.be page load time and found that the first response time was 277 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
egencia.be performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value13.5 s
0/100
25%
Value27.6 s
0/100
10%
Value44,840 ms
0/100
30%
Value0.019
100/100
15%
Value59.8 s
0/100
10%
277 ms
398 ms
439 ms
491 ms
531 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Egencia.be, 52% (23 requests) were made to D298y50y5eugia.cloudfront.net and 7% (3 requests) were made to Info.egencia.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn.bizible.com.
Page size can be reduced by 169.1 kB (29%)
577.0 kB
407.8 kB
In fact, the total size of Egencia.be main page is 577.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 299.8 kB which makes up the majority of the site volume.
Potential reduce by 153.6 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 19.5 kB, which is 11% 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 153.6 kB or 84% of the original size.
Potential reduce by 4.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. Obviously, Egencia needs image optimization as it can save up to 4.5 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 10.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 156 B
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. Egencia.be has all CSS files already compressed.
Number of requests can be reduced by 17 (47%)
36
19
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Egencia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
egencia.be
277 ms
398 ms
css_hg7ux-Bgt8-xSsgkBPosWcWF_Et3Ib1S5LsvB6H2l-g.css
439 ms
css_TTM2WyXKrbWYaKiB1ZWdIftyxb9a2hK7jJd-9LhkNpE.css
491 ms
css_W1JEFjsBmRQU_m9Y4mq1rczKuhVAxsKf2Lrm7VvzLsc.css
531 ms
uc.js
884 ms
optimize.js
669 ms
js_IlBYXTp2xp7usp57O08w3xfNmTqJWWSVgAte3ROw_Bk.js
883 ms
forms2.min.js
940 ms
js_8OgtShUu93ED1THI9nG98GMABoVI8qiaK10_mAi3T_o.js
528 ms
js_AH4QtG2RFFTDr-lcEMkuO8nmTIeXeoyN8SzCtIQ3wlE.js
648 ms
bizible.js
1198 ms
js_N9bc0w89kCI965AWOuRJ07CfSZEDgJXyESF69BEYcrA.js
625 ms
cc.js
443 ms
css_Y4H_4BqmgyCtG7E7YdseTs2qvy9C34c51kBamDdgark.css
635 ms
gtm.js
594 ms
logo.svg
493 ms
onboarding_welcome.svg
364 ms
onboarding_documents.svg
363 ms
checkin.svg
333 ms
launch.svg
405 ms
EG%20Dotcom%20Icons%20Byzantium_17.svg
274 ms
EG%20Dotcom%20Icons%20Byzantium_19.svg
367 ms
Traveler.svg
407 ms
Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917.svg
449 ms
google-play-badge.png
451 ms
global_icon.svg
647 ms
curve.svg
645 ms
bc-v4.min.html
670 ms
roboto-light.woff
448 ms
ei.js
387 ms
ipv
77 ms
u
407 ms
lazysizes.js
51 ms
9jp34b0nzn
1130 ms
E-v1.js
915 ms
teknkl-simpledto-1.0.4.js
136 ms
js
123 ms
roboto-regular.ttf
200 ms
egencia.woff
200 ms
egencia.woff
182 ms
analytics.js
924 ms
xdc.js
847 ms
page-title.js
778 ms
egencia.be accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
egencia.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
egencia.be 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
Image elements do not have [alt] attributes
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 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 Egencia.be 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 Egencia.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.
egencia.be
Open Graph data is detected on the main page of Egencia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: