9.7 sec in total
2.9 sec
6.6 sec
162 ms
Welcome to voos.infraero.gov.br homepage info - get ready to check Voos Infraero best content for Brazil right away, or after learning these important things about voos.infraero.gov.br
Visit voos.infraero.gov.brWe analyzed Voos.infraero.gov.br page load time and found that the first response time was 2.9 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
voos.infraero.gov.br performance score
name
value
score
weighting
Value109.3 s
0/100
10%
Value132.2 s
0/100
25%
Value109.3 s
0/100
10%
Value1,380 ms
16/100
30%
Value0.188
65/100
15%
Value137.8 s
0/100
10%
2914 ms
370 ms
389 ms
601 ms
407 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 97% of them (92 requests) were addressed to the original Voos.infraero.gov.br, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Voos.infraero.gov.br.
Page size can be reduced by 284.1 kB (39%)
735.2 kB
451.1 kB
In fact, the total size of Voos.infraero.gov.br main page is 735.2 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. 30% of websites need less resources to load. Images take 345.7 kB which makes up the majority of the site volume.
Potential reduce by 40.5 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 5.4 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 40.5 kB or 83% of the original size.
Potential reduce by 14.4 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. Voos Infraero images are well optimized though.
Potential reduce by 203.1 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 203.1 kB or 66% of the original size.
Potential reduce by 26.0 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. Voos.infraero.gov.br needs all CSS files to be minified and compressed as it can save up to 26.0 kB or 78% of the original size.
Number of requests can be reduced by 57 (61%)
94
37
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voos Infraero. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
voos.infraero.gov.br
2914 ms
shadowbox.css
370 ms
mod_mapadosite.css
389 ms
collapze.css
601 ms
menuicon.css
407 ms
modal.css
418 ms
mootools.js
1266 ms
caption.js
580 ms
silverlight.js
808 ms
wmvplayer.js
828 ms
swfobject.js
767 ms
avreloaded.js
772 ms
modal.js
995 ms
ultifont.js
962 ms
yoo_effects.js.php
1169 ms
jquery.min.js
30 ms
jquery-comp.js
1208 ms
jquery-fpss-comp.js
853 ms
template.css
974 ms
noticias.css
1012 ms
pesquisa.css
1058 ms
imprensa.css
1168 ms
conteudo.css
1183 ms
acessibilidade.js
1211 ms
estilos.js
1226 ms
jquery-1.3.2.min.js
1291 ms
jquery.easing.1.3.js
1072 ms
jquery.galleryview-1.1.js
1172 ms
jquery.timers-1.1.2.js
1185 ms
s3Slider.css
1218 ms
template_css.php
326 ms
fundo_grande.jpg
198 ms
all2.png
196 ms
barra.png
202 ms
br.gif
205 ms
us.gif
183 ms
es.gif
225 ms
logo_infraero.png
367 ms
g3397.png
390 ms
g3329.png
393 ms
g3359.png
402 ms
default.png
407 ms
dalto.png
432 ms
contraste.png
548 ms
g6511.png
583 ms
g3355.png
587 ms
loading.gif
603 ms
Spotter_Day_Sao_Luis_1.jpg
609 ms
Manutencao_1.jpg
842 ms
Area_Comercial_1.jpg
908 ms
Quiosque_SDU_Fantasia.jpg
969 ms
Esea_Aquatico_Belem_1.jpg
973 ms
nav-bg.gif
801 ms
corner.png
812 ms
bg_botao_noticias_imprensa.png
1004 ms
bg_botao_notas_imprensa.png
1014 ms
facebook21x21.jpg
1048 ms
ico_instagram.jpg
1089 ms
twitter21x21.jpg
1164 ms
youtube21x21.jpg
1168 ms
flickr_21.png
1202 ms
f1212.png
1217 ms
voos-on-line.png
1257 ms
guia-passageiro.png
1271 ms
situacao-voos.png
1358 ms
aeroshopping.png
1350 ms
carga-aerea.png
1392 ms
ga.js
30 ms
__utm.gif
12 ms
licitacoes.png
1243 ms
concurso.png
1277 ms
servico-contra-incendio.png
1264 ms
link.png
1360 ms
tarifa-aeroportuaria.png
1361 ms
central-cobranca.png
1395 ms
portal-financeiro.png
1263 ms
banner_mosquito.gif
1435 ms
banner_guia_acess.jpg
1288 ms
relprev_infraero.jpg
1355 ms
banner_oportunidade.jpg
1354 ms
banner_infraerocargo.jpg
1397 ms
indent6.png
1285 ms
transparencia_publica.png
1305 ms
selo_acessibilidade.png
1365 ms
selo_participe.jpg
1354 ms
g3356.png
1396 ms
ui-icons_666666_256x240.png
1227 ms
borda-fundo2.png
1222 ms
next.png
1254 ms
prev.png
1238 ms
panel-nav-next.png
1181 ms
panel-nav-prev.png
1214 ms
transparent_bg.png
1227 ms
daltonismo.css
199 ms
contraste.css
197 ms
voos.infraero.gov.br 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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.
ARIA toggle fields do not have accessible names
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
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
voos.infraero.gov.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
voos.infraero.gov.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voos.infraero.gov.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Voos.infraero.gov.br 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.
voos.infraero.gov.br
Open Graph description is not detected on the main page of Voos Infraero. 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: