4.3 sec in total
1.2 sec
2.8 sec
281 ms
Welcome to aea.be homepage info - get ready to check Aea best content for United States right away, or after learning these important things about aea.be
Visit aea.beWe analyzed Aea.be page load time and found that the first response time was 1.2 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
aea.be performance score
1168 ms
89 ms
263 ms
174 ms
176 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 85% of them (78 requests) were addressed to the original Aea.be, 12% (11 requests) were made to Use.typekit.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Aea.be.
Page size can be reduced by 585.3 kB (35%)
1.7 MB
1.1 MB
In fact, the total size of Aea.be main page is 1.7 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. 55% of websites need less resources to load. Images take 979.3 kB which makes up the majority of the site volume.
Potential reduce by 56.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. 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 56.6 kB or 84% of the original size.
Potential reduce by 53.7 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. Aea images are well optimized though.
Potential reduce by 235.3 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 235.3 kB or 70% of the original size.
Potential reduce by 239.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. Aea.be needs all CSS files to be minified and compressed as it can save up to 239.8 kB or 87% of the original size.
Number of requests can be reduced by 18 (23%)
80
62
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aea. 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 8 to 1 for CSS and as a result speed up the page load time.
aea.be
1168 ms
base.css
89 ms
bootstrap.min.css
263 ms
bootstrap-theme.min.css
174 ms
flexslider.css
176 ms
jquery.mCustomScrollbar.css
183 ms
aea.css
186 ms
jquery-1.9.1.min.js
280 ms
bootstrap.min.js
262 ms
jquery.flexslider.js
277 ms
jquery.sticky.js
278 ms
jquery.fancybox.js
278 ms
jquery.mCustomScrollbar.concat.min.js
352 ms
jquery.html5-placeholder-shim.js
349 ms
custom.js
357 ms
ryr5wvt.js
178 ms
jquery.fancybox.css
348 ms
jquery.nailthumb.1.0.min.js
440 ms
1bf
198 ms
logo.png
89 ms
tw_tp.png
86 ms
lin_tp.png
90 ms
cockpit_banner.jpg
423 ms
AEA_Bulc-3MAR2016.jpg
544 ms
arrdep_banner.jpg
380 ms
flightmap_banner.jpg
683 ms
mod_img2.jpg
299 ms
art_plane1.jpg
174 ms
mod_img3.jpg
396 ms
mod_img1.jpg
340 ms
menu_toggle.png
355 ms
white_trans.png
395 ms
star_pic.jpg
419 ms
atb_2012.jpg
442 ms
ahk_quote3.jpg
442 ms
aegean_web.jpg
473 ms
airbaltic_web.jpg
483 ms
airfrance_web.jpg
520 ms
airmalta_web.jpg
525 ms
austrian_web.jpg
554 ms
snbrussels_web.jpg
556 ms
cargolux_web.jpg
567 ms
croatia_web.jpg
602 ms
dhl_web.jpg
609 ms
finnair_web.jpg
638 ms
icelandair_web.jpg
641 ms
klm_web.jpg
650 ms
lot_web.jpg
687 ms
lufthansa_web.jpg
692 ms
luxair_web.jpg
693 ms
sas_web.jpg
721 ms
swiss_web.jpg
724 ms
tap_web.jpg
736 ms
tarom_web.jpg
769 ms
avenirltstd-light.woff
774 ms
tnt_web.jpg
778 ms
turkish_web.jpg
801 ms
uia_web.jpg
800 ms
webaea_sita.jpg
723 ms
analytics.js
48 ms
RvDvKmLLW_ARa_rclv-8tollmZGJn5Q-PAVeXtminw6ffFzcgsMZeMI6MK6g5Mb.eot
67 ms
T_iHGhb8SQyddGP2azuy_gvptqvw64DCQv1R8PYYa4qffFxcgsMZeMI6MK6g5MS.eot
134 ms
e7h2aiaCvnywIIetjjjgcpCVrA9RaXfPDV_Uh7om-tSffH2dggMZeMI6MK6f5Mt.eot
159 ms
gc0zh4LYTiBuX5YGqxEhWClWF9d82xdIPj95RGHqfb6ff41dggMZeMI6MK6f5gI.eot
160 ms
gUsbv9_25xTxbK28nF1IWFqJX38GXLpbkUMphNBCDdIffHDdggMZeMI6MK6f5Mb.eot
160 ms
x0z7CeftxzooYIfCqvTmf1L5Or4MeyyaczoXyWSTGUjff4ddggMZeMI6MK6f5MS.eot
166 ms
YwJFch76qr4AmaiXgZDNnq_G3eb5y1esWI02VnP7pRIffHQdggMZeMI6MK6f5Mw.eot
300 ms
lHlWwXSQfzcxkEFSW7VnrgKgnKc6DhhVLJBabZwN1R3ffFDcgsMZeMI6MK6g5Mt.eot
190 ms
iNnQGboXnxZfAEU0vylacL32Ra7Iv1Fx4zkiTMZZJG9ff52cgsMZeMI6MK6g5gI.eot
211 ms
index.php
717 ms
collect
11 ms
avenirltstd-heavy.woff
597 ms
webaea_cfm.jpg
551 ms
webaea_seabury.jpg
581 ms
webaea_pw.jpg
554 ms
webaea_embraer.jpg
557 ms
webaea_heico.jpg
557 ms
webaea_nomad.jpg
533 ms
webaea_nats.jpg
540 ms
webaea_safran.jpg
528 ms
webaea_skyguide.jpg
526 ms
webaea_capa.jpg
557 ms
webaea_uatp.jpg
554 ms
tw_bt.png
517 ms
lin_bt.png
541 ms
banner_stroke.jpg
520 ms
member_seperator.jpg
524 ms
footer_grad.png
547 ms
stroke_ftr.png
519 ms
feed.png
512 ms
banner_title_stroke.jpg
540 ms
nr-885.min.js
51 ms
aea.be SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aea.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 Aea.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.
aea.be
Open Graph description is not detected on the main page of Aea. 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: