Tools & Wizards About Us
aeroportofortaleza.net screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

aeroportofortaleza.net

Aeroporto Internacional de Fortaleza - Pinto Martins - CE - FOR

Page Load Speed

6.5 sec in total

First Response

685 ms

Resources Loaded

5.7 sec

Page Rendered

153 ms

aeroportofortaleza.net screenshot

About Website

Visit aeroportofortaleza.net now to see the best up-to-date Aeroporto Fortaleza content for Brazil and also check out these interesting facts you probably never knew about aeroportofortaleza.net

Site do Aeroporto Internacional Pinto Martins - Fortaleza. Informações sobre voos online, formas de transporte, companhias aéreas, estacionamento e mais.

Visit aeroportofortaleza.net

Key Findings

We analyzed Aeroportofortaleza.net page load time and found that the first response time was 685 ms and then it took 5.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.

Performance Metrics

aeroportofortaleza.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

www.aeroportofortaleza.net

685 ms

js

90 ms

style.css

310 ms

home.css

343 ms

nivo-slider.css

371 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 24% of them (33 requests) were addressed to the original Aeroportofortaleza.net, 13% (18 requests) were made to Cm.g.doubleclick.net and 10% (13 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Aeroportofortaleza.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.0 kB (34%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aeroportofortaleza.net main page is 1.8 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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 50.1 kB

  • Original 61.9 kB
  • After minification 61.3 kB
  • After compression 11.9 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 50.1 kB or 81% of the original size.

Image Optimization

-22%

Potential reduce by 64.5 kB

  • Original 290.8 kB
  • After minification 226.3 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, Aeroporto Fortaleza needs image optimization as it can save up to 64.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-34%

Potential reduce by 480.6 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 913.4 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 480.6 kB or 34% of the original size.

CSS Optimization

-37%

Potential reduce by 4.8 kB

  • Original 12.8 kB
  • After minification 10.7 kB
  • After compression 8.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. Aeroportofortaleza.net needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (66%)

Requests Now

121

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aeroporto Fortaleza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.aeroportofortaleza.net

www.aeroportofortaleza.net

685 ms

js

js

90 ms

style.css

style.css

310 ms

home.css

home.css

343 ms

nivo-slider.css

nivo-slider.css

371 ms

frontend.css

frontend.css

383 ms

colorbox.css

colorbox.css

356 ms

jquery.js

jquery.js

353 ms

jquery-migrate.min.js

jquery-migrate.min.js

625 ms

gallery.js

gallery.js

678 ms

colorbox.js

colorbox.js

711 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

668 ms

home.js

home.js

677 ms

adsbygoogle.js

adsbygoogle.js

196 ms

gpt.js

gpt.js

110 ms

cookieconsent.min.js

cookieconsent.min.js

55 ms

reset.css

reset.css

395 ms

rebuild.css

rebuild.css

623 ms

2c-r.css

2c-r.css

672 ms

admin-ajax.php

admin-ajax.php

1041 ms

tranquilo-seguro-viagem-praia-310x200.jpg

tranquilo-seguro-viagem-praia-310x200.jpg

372 ms

bg-aeroporto.png

bg-aeroporto.png

315 ms

logo-aeroportos-brasil.jpg

logo-aeroportos-brasil.jpg

315 ms

aeroporto-portugues.jpg

aeroporto-portugues.jpg

314 ms

airport-english.jpg

airport-english.jpg

314 ms

twitter-header.png

twitter-header.png

313 ms

fb-header.png

fb-header.png

344 ms

como-chegar.jpg

como-chegar.jpg

632 ms

companhias-aereas-aeroporto.jpg

companhias-aereas-aeroporto.jpg

635 ms

anuncie-aeroportos.jpg

anuncie-aeroportos.jpg

640 ms

show_ads_impl.js

show_ads_impl.js

449 ms

pubads_impl.js

pubads_impl.js

41 ms

icones-home.jpg

icones-home.jpg

501 ms

painel_home.inc.php

painel_home.inc.php

572 ms

overlay.png

overlay.png

734 ms

ads

ads

106 ms

container.html

container.html

28 ms

controls.png

controls.png

678 ms

border.png

border.png

679 ms

loading_background.png

loading_background.png

681 ms

loading.gif

loading.gif

776 ms

abg_lite.js

abg_lite.js

29 ms

jquery.min.js

jquery.min.js

17 ms

icon.png

icon.png

1395 ms

9764228047456953810

9764228047456953810

48 ms

zrt_lookup.html

zrt_lookup.html

42 ms

ads

ads

619 ms

ads

ads

425 ms

ads

ads

434 ms

ads

ads

655 ms

ads

ads

543 ms

gen_204

gen_204

110 ms

pixel

pixel

110 ms

3001567967837777366

3001567967837777366

120 ms

abg_lite.js

abg_lite.js

68 ms

omrhp.js

omrhp.js

108 ms

Q12zgMmT.js

Q12zgMmT.js

60 ms

window_focus.js

window_focus.js

107 ms

cookie_push_onload.html

cookie_push_onload.html

100 ms

qs_click_protection.js

qs_click_protection.js

123 ms

ufs_web_display.js

ufs_web_display.js

176 ms

icon.png

icon.png

88 ms

reactive_library.js

reactive_library.js

371 ms

pixel

pixel

300 ms

62bHydCX.html

62bHydCX.html

44 ms

gen_204

gen_204

281 ms

16704803404567929762

16704803404567929762

245 ms

google

google

671 ms

usersync.aspx

usersync.aspx

643 ms

sync

sync

641 ms

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

249 ms

activeview

activeview

383 ms

14763004658117789537

14763004658117789537

281 ms

load_preloaded_resource.js

load_preloaded_resource.js

279 ms

s

s

282 ms

60efddb729a951d3495fe79f6eb41a86.js

60efddb729a951d3495fe79f6eb41a86.js

291 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

183 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

247 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

296 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

297 ms

i.match

i.match

426 ms

gp_match

gp_match

234 ms

sync

sync

145 ms

css

css

97 ms

pixel

pixel

44 ms

pixel

pixel

43 ms

pixel

pixel

38 ms

rum

rum

52 ms

pixel

pixel

41 ms

bounce

bounce

41 ms

pixel

pixel

43 ms

pixel

pixel

44 ms

pixel

pixel

37 ms

pixel

pixel

36 ms

pixel

pixel

52 ms

pixel

pixel

46 ms

pixel

pixel

47 ms

pixel

pixel

47 ms

pixel

pixel

42 ms

pixel

pixel

43 ms

pixel

pixel

32 ms

rum

rum

120 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

133 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

134 ms

pixel

pixel

27 ms

i.match

i.match

128 ms

activeview

activeview

183 ms

pixel

pixel

22 ms

dark-bottom.css

dark-bottom.css

21 ms

like.php

like.php

185 ms

widgets.js

widgets.js

69 ms

plusone.js

plusone.js

31 ms

sodar

sodar

100 ms

logo.png

logo.png

27 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

fastbutton

fastbutton

27 ms

34 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

210 ms

postmessageRelay

postmessageRelay

89 ms

sodar2.js

sodar2.js

12 ms

runner.html

runner.html

12 ms

aframe

aframe

37 ms

developers.google.com

developers.google.com

390 ms

vAyXKx-8ZBt.js

vAyXKx-8ZBt.js

46 ms

FEppCFCt76d.png

FEppCFCt76d.png

42 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

42 ms

rpc:shindig_random.js

rpc:shindig_random.js

21 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

settings

settings

70 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

23 ms

embeds

embeds

35 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

35 ms

pixel

pixel

20 ms

spacer.gif

spacer.gif

147 ms

Accessibility Review

aeroportofortaleza.net accessibility score

73

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

aeroportofortaleza.net best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

aeroportofortaleza.net SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aeroportofortaleza.net 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 Aeroportofortaleza.net 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.

Social Sharing Optimization

aeroportofortaleza.net

Open Graph data is detected on the main page of Aeroporto Fortaleza. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: