2.1 sec in total
147 ms
1.3 sec
692 ms
Welcome to indy.gov homepage info - get ready to check Indy best content for United States right away, or after learning these important things about indy.gov
Visit indy.govWe analyzed Indy.gov page load time and found that the first response time was 147 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
indy.gov performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value10.4 s
0/100
25%
Value4.5 s
72/100
10%
Value420 ms
65/100
30%
Value0.179
68/100
15%
Value11.0 s
21/100
10%
147 ms
380 ms
80 ms
97 ms
101 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 58% of them (28 requests) were addressed to the original Indy.gov, 23% (11 requests) were made to Callback-service.prod.cityba.se and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (444 ms) belongs to the original domain Indy.gov.
Page size can be reduced by 23.6 kB (1%)
2.5 MB
2.5 MB
In fact, the total size of Indy.gov main page is 2.5 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 11.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 3.5 kB, which is 24% 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 11.5 kB or 80% of the original size.
Potential reduce by 12.1 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. Indy images are well optimized though.
Potential reduce by 26 B
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. Indy.gov has all CSS files already compressed.
Number of requests can be reduced by 3 (9%)
35
32
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
indy.gov
147 ms
www.indy.gov
380 ms
icon
80 ms
css
97 ms
css
101 ms
app-15d7a9990097928d929a538e1af1924a.css
69 ms
csp
304 ms
csp
304 ms
csp
304 ms
csp
306 ms
3a8d594998524a648fcfa3cdfc607004.jpg
191 ms
bidding.jpg
137 ms
mortgage-deduction-med.jpg
186 ms
homestead.jpg
300 ms
mailbox.jpg
200 ms
records.jpg
199 ms
IMPD-cruiser.jpg
205 ms
moving.jpg
204 ms
hanging-files.jpg
299 ms
property-deductions.jpg
302 ms
do-business.jpg
301 ms
contact-mayor.jpg
302 ms
vote.jpg
334 ms
hogsett.jpg
315 ms
council.jpg
317 ms
courts.jpg
344 ms
oconnor.jpg
343 ms
voorhies.jpg
345 ms
eldridge.jpg
378 ms
sloan.jpg
385 ms
prosecutor.jpg
395 ms
bell.jpg
403 ms
sheriff.jpg
403 ms
jenkins.jpg
402 ms
shift-indy.svg
444 ms
csp
301 ms
csp
301 ms
csp
361 ms
csp
363 ms
csp
363 ms
csp
371 ms
bounce
11 ms
bounce
32 ms
csp
278 ms
indy-skyline-71e9200a9a54cb5a8929584d772da3c6.jpg
413 ms
font
22 ms
font
31 ms
font
41 ms
indy.gov accessibility score
indy.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
indy.gov 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indy.gov 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 Indy.gov 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.
indy.gov
Open Graph description is not detected on the main page of Indy. 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: