7.8 sec in total
1.9 sec
4.7 sec
1.2 sec
Welcome to indyhub.org homepage info - get ready to check Indy Hub best content for United States right away, or after learning these important things about indyhub.org
We are an advocate for Indy’s twenty-/thirty-somethings, providing a resource and space to learn about, connect with and become a part of this city.
Visit indyhub.orgWe analyzed Indyhub.org page load time and found that the first response time was 1.9 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
indyhub.org performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value37.8 s
0/100
25%
Value6.8 s
35/100
10%
Value760 ms
39/100
30%
Value0.27
45/100
15%
Value23.5 s
1/100
10%
1877 ms
30 ms
41 ms
49 ms
50 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 85% of them (55 requests) were addressed to the original Indyhub.org, 6% (4 requests) were made to Fonts.googleapis.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Indyhub.org.
Page size can be reduced by 1.2 MB (20%)
6.2 MB
5.0 MB
In fact, the total size of Indyhub.org main page is 6.2 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. 50% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 29.7 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 29.7 kB or 79% of the original size.
Potential reduce by 690.0 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, Indy Hub needs image optimization as it can save up to 690.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 169.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 169.1 kB or 65% of the original size.
Potential reduce by 340.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. Indyhub.org needs all CSS files to be minified and compressed as it can save up to 340.5 kB or 63% of the original size.
Number of requests can be reduced by 30 (50%)
60
30
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indy Hub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
indyhub.org
1877 ms
css
30 ms
css
41 ms
css
49 ms
css
50 ms
style.css
109 ms
91bc3525_ai1ec_parsed_css.css
310 ms
cnss.css
59 ms
light_style.css
61 ms
superfish.css
66 ms
flexslider.css
73 ms
jquery.js
190 ms
jquery-migrate.min.js
145 ms
cnss.js
145 ms
core.min.js
129 ms
widget.min.js
153 ms
mouse.min.js
162 ms
sortable.min.js
193 ms
comment-reply.min.js
172 ms
collapse.js
232 ms
superfish.js
219 ms
jquery.fadescroll.js
227 ms
jquery.divsticker.js
227 ms
jquery.fitvids.js
248 ms
jquery.actual.min.js
284 ms
jquery.fittext.js
285 ms
tinynav.min.js
285 ms
jquery.isotope.min.js
447 ms
jquery.flexslider-min.js
447 ms
theme_trust.js
447 ms
wp-embed.min.js
447 ms
wp-emoji-release.min.js
343 ms
ga.js
119 ms
indyhub-main-logo_white.png
71 ms
team-denver-home-page.png
931 ms
5x5_home_1920.jpg
725 ms
EXC_home_1920.jpg
659 ms
Screen-Shot-2016-03-01-at-2.31.32-PM.png
610 ms
NMC-320x240.png
440 ms
Screen-Shot-2016-02-29-at-3.42.00-PM.png
2416 ms
millennialVoices_320x240.png
608 ms
team-denver-320px.jpg
784 ms
fsmusicfest-1.jpg
726 ms
LourenzoGiple_Headshot.jpg
795 ms
Kaufmann-200x200-BW1.jpg
831 ms
SarahRoss_Headshot.jpg
814 ms
Blaire-200x200-BW1.jpg
869 ms
Rob-Smith-200x200-BW1.jpg
944 ms
TrevorBelden_Headshot.jpg
895 ms
Katie-Vicars-200x200-BW1.jpg
919 ms
Mayowa-200x200-BW1.jpg
990 ms
Lilly-for-enews.jpg
976 ms
LillyEndowment_logo-150x150.png
1169 ms
The-Indianapolis-Foundation-209x111.jpg
1169 ms
1377105448_03-twitter-for-footer.png
993 ms
1376798313_06-facebook_grey.png
1170 ms
1403534788_grayscale_instagram.png
1169 ms
1410815644_linkedin-grey-icon.png
1170 ms
IndyHub_BlackWhite_Map.jpg
1170 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
99 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
99 ms
qZpi6ZVZg3L2RL_xoBLxWYnF5uFdDttMLvmWuJdhhgs.ttf
99 ms
xmB9oJNpSFKa3qTF2JABPqCWcynf_cDxXwCLxiixG1c.ttf
100 ms
__utm.gif
299 ms
direction_nav.png
43 ms
indyhub.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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 IDs are not unique
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
Links do not have a discernible name
indyhub.org 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
indyhub.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indyhub.org 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 Indyhub.org 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.
indyhub.org
Open Graph description is not detected on the main page of Indy Hub. 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: