Tools & Wizards About Us
ind.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

ind.com

Indianapolis Airport Authority (Home) | Indianapolis Airport Authority

Page Load Speed

2.2 sec in total

First Response

52 ms

Resources Loaded

1.8 sec

Page Rendered

319 ms

ind.com screenshot

About Website

Visit ind.com now to see the best up-to-date Ind content for United States and also check out these interesting facts you probably never knew about ind.com

Official Indianapolis International Airport website - view live flight times and live parking information.

Visit ind.com

Key Findings

We analyzed Ind.com page load time and found that the first response time was 52 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ind.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value4,020 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

ind.com

52 ms

ind.com

178 ms

cyx0qxy.js

25 ms

styles.faeac992aee12c9ffa0e6c5241d9665c.css

20 ms

crowdriff.js

477 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 47% of them (34 requests) were addressed to the original Ind.com, 15% (11 requests) were made to Youtube.com and 14% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (623 ms) belongs to the original domain Ind.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.9 kB (10%)

Content Size

462.4 kB

After Optimization

415.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ind.com main page is 462.4 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. 80% 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 198.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 44.2 kB

  • Original 53.3 kB
  • After minification 46.1 kB
  • After compression 9.2 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 7.2 kB, which is 14% 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 44.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 56 B

  • Original 151.4 kB
  • After minification 151.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. Ind images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 198.1 kB
  • After minification 198.1 kB
  • After compression 195.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 59.5 kB
  • After minification 59.5 kB
  • After compression 59.5 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. Ind.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (68%)

Requests Now

56

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ind.com

ind.com

52 ms

ind.com

ind.com

178 ms

cyx0qxy.js

cyx0qxy.js

25 ms

styles.faeac992aee12c9ffa0e6c5241d9665c.css

styles.faeac992aee12c9ffa0e6c5241d9665c.css

20 ms

crowdriff.js

crowdriff.js

477 ms

vendor.9ab9541a9f0c1842f37b050868d60567.js

vendor.9ab9541a9f0c1842f37b050868d60567.js

318 ms

app.d01722d863ddb48f8de4b5184e64cc5c.js

app.d01722d863ddb48f8de4b5184e64cc5c.js

511 ms

gtm.js

gtm.js

479 ms

K_u1yav_Fes

K_u1yav_Fes

572 ms

analytics.js

analytics.js

440 ms

terminal--1500.jpg

terminal--1500.jpg

168 ms

iaa-logo-white.svg

iaa-logo-white.svg

167 ms

r-arrow.png

r-arrow.png

201 ms

select-arrow.png

select-arrow.png

204 ms

tsa-precheck-logo2x.png

tsa-precheck-logo2x.png

203 ms

r-w-arrow.png

r-w-arrow.png

267 ms

parking.svg

parking.svg

201 ms

one-of-a-kind-white.svg

one-of-a-kind-white.svg

204 ms

facebook.svg

facebook.svg

268 ms

x.svg

x.svg

268 ms

instagram.svg

instagram.svg

313 ms

youtube.svg

youtube.svg

311 ms

flight.svg

flight.svg

313 ms

parking-white.svg

parking-white.svg

309 ms

car-transportation.svg

car-transportation.svg

311 ms

more.svg

more.svg

311 ms

d

d

46 ms

d

d

78 ms

d

d

98 ms

d

d

99 ms

d

d

100 ms

d

d

99 ms

d

d

100 ms

d

d

140 ms

d

d

164 ms

collect

collect

113 ms

collect

collect

115 ms

15_797f1f4d2e32e755131c.js

15_797f1f4d2e32e755131c.js

77 ms

21_06e4ae969fcfeb1d30f6.js

21_06e4ae969fcfeb1d30f6.js

75 ms

5_cc7f09d9c642a7cecc65.js

5_cc7f09d9c642a7cecc65.js

76 ms

30_e7b71ceab778c17d68c6.js

30_e7b71ceab778c17d68c6.js

75 ms

19_35a388295d3e8e90a74e.js

19_35a388295d3e8e90a74e.js

76 ms

7_a0f89cac8cf2f2e22b90.js

7_a0f89cac8cf2f2e22b90.js

75 ms

3_723fb689ab4f7b068759.js

3_723fb689ab4f7b068759.js

85 ms

27_68f4766bfeb034f0bb24.js

27_68f4766bfeb034f0bb24.js

84 ms

16_26c6eb08a1a37f890d69.js

16_26c6eb08a1a37f890d69.js

84 ms

14_368e98f960b4bd5a5866.js

14_368e98f960b4bd5a5866.js

83 ms

4_27efdb9e598b3f3b33f3.js

4_27efdb9e598b3f3b33f3.js

84 ms

p.gif

p.gif

53 ms

js

js

71 ms

js

js

252 ms

fbevents.js

fbevents.js

250 ms

www-player.css

www-player.css

20 ms

www-embed-player.js

www-embed-player.js

19 ms

base.js

base.js

19 ms

js

js

179 ms

iframe_api

iframe_api

167 ms

K_u1yav_Fes

K_u1yav_Fes

282 ms

index

index

265 ms

index

index

623 ms

www-widgetapi.js

www-widgetapi.js

118 ms

819228363313227

819228363313227

379 ms

www-player.css

www-player.css

22 ms

www-embed-player.js

www-embed-player.js

20 ms

base.js

base.js

79 ms

ad_status.js

ad_status.js

238 ms

wQkdmVX08K_HD_9NHn0QjGfgu04J0GwVvAmYELAxlpM.js

wQkdmVX08K_HD_9NHn0QjGfgu04J0GwVvAmYELAxlpM.js

180 ms

embed.js

embed.js

102 ms

id

id

33 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

124 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

123 ms

Create

Create

89 ms

Accessibility Review

ind.com accessibility score

90

Accessibility Issues

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

High

ARIA progressbar elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

ind.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ind.com SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

ind.com

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