1.2 sec in total
92 ms
952 ms
157 ms
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.comWe analyzed Ind.com page load time and found that the first response time was 92 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
ind.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.3 s
93/100
25%
Value2.3 s
98/100
10%
Value2,140 ms
6/100
30%
Value0.013
100/100
15%
Value13.2 s
12/100
10%
92 ms
234 ms
20 ms
21 ms
35 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ind.com, 84% (61 requests) were made to Indianapolisairport.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (234 ms) relates to the external source Indianapolisairport.com.
Page size can be reduced by 553.1 kB (41%)
1.3 MB
780.4 kB
In fact, the total size of Ind.com main page is 1.3 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. 35% of websites need less resources to load. Images take 659.9 kB which makes up the majority of the site volume.
Potential reduce by 26.0 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 4.6 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 26.0 kB or 77% of the original size.
Potential reduce by 41.6 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.
Potential reduce by 436.6 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 436.6 kB or 75% of the original size.
Potential reduce by 48.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. Ind.com needs all CSS files to be minified and compressed as it can save up to 48.8 kB or 87% of the original size.
Number of requests can be reduced by 34 (50%)
68
34
The browser has sent 68 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 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ind.com
92 ms
www.indianapolisairport.com
234 ms
buttons.css
20 ms
form.css
21 ms
layout.css
35 ms
reset.css
23 ms
typography.css
24 ms
print.css
28 ms
screen.css
30 ms
adobe.js
29 ms
prototype.js
84 ms
scriptaculous.js
32 ms
jquery.min.js
113 ms
banner.js
39 ms
WebResource.axd
100 ms
ScriptResource.axd
100 ms
ScriptResource.axd
45 ms
google.js
48 ms
sojern.js
58 ms
bizo.js
81 ms
builder.js
19 ms
effects.js
23 ms
dragdrop.js
33 ms
controls.js
31 ms
slider.js
31 ms
sound.js
39 ms
analytics.js
29 ms
644
89 ms
insight.min.js
46 ms
bg-body.gif
34 ms
header-iaa.jpg
38 ms
bg-sign_bar.jpg
38 ms
btn-home.jpg
37 ms
btn-airlines_flights.jpg
36 ms
btn-maps_directions.jpg
36 ms
btn-parking_transportation.jpg
38 ms
btn-services_amenities.jpg
42 ms
btn-travel_preparation.jpg
41 ms
btn-employment_business.jpg
42 ms
btn-information_news.jpg
43 ms
bg-nav.jpg
44 ms
btn24-search.gif
45 ms
image_rotator_bg.jpg
57 ms
bg-module.jpg
57 ms
icn-flight_status.jpg
69 ms
0930-1027_OnlineAd_V2.jpg
114 ms
ParkIND-Plus-Banner300x250_000.jpg
108 ms
twitter-bird-light-bgs.png
107 ms
Facebook_000.JPG
106 ms
YouTube_24x24.jpg
107 ms
big-p-button.png
107 ms
Instagram_Icon_Small.png
122 ms
bg-module_featured.gif
123 ms
aci-did-you-know-video.jpg
131 ms
ad-feedback.jpg
126 ms
10.14.10INDyInsiderBannerAd_000.jpg
130 ms
collect
17 ms
collect
82 ms
beacon
81 ms
src=4897185;type=sales;cat=ep1shde8;qty=1;cost=0;u1=[cid];ord=[OrderID]
57 ms
pixel
48 ms
pixel
14 ms
AdX
60 ms
bannerImage0.jpg
35 ms
bannerImage1.jpg
49 ms
bannerImage2.jpg
30 ms
bannerImage3.jpg
52 ms
bannerImage4.jpg
74 ms
bannerImage5.jpg
76 ms
bannerImage6.jpg
63 ms
bannerImage7.jpg
81 ms
bannerImage8.jpg
79 ms
31 ms
ind.com 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 progressbar elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ind.com 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
Missing source maps for large first-party JavaScript
ind.com SEO score
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
EN
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
ind.com
Open Graph description is not detected on the main page of Ind. 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: