3.2 sec in total
79 ms
2.4 sec
653 ms
Welcome to indymaven.com homepage info - get ready to check Indy Maven best content right away, or after learning these important things about indymaven.com
Indy Maven connects women in Indianapolis through captivating news stories, crazy fun events, and partnerships with local businesses.
Visit indymaven.comWe analyzed Indymaven.com page load time and found that the first response time was 79 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
indymaven.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value17.8 s
0/100
25%
Value11.4 s
5/100
10%
Value3,000 ms
3/100
30%
Value0.056
98/100
15%
Value28.2 s
0/100
10%
79 ms
106 ms
138 ms
94 ms
69 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 60% of them (99 requests) were addressed to the original Indymaven.com, 20% (32 requests) were made to Fonts.gstatic.com and 9% (14 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Indymaven.com.
Page size can be reduced by 406.9 kB (9%)
4.4 MB
4.0 MB
In fact, the total size of Indymaven.com main page is 4.4 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. Only a small number of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 143.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 143.9 kB or 81% of the original size.
Potential reduce by 223.5 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 Maven images are well optimized though.
Potential reduce by 16.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. This website has mostly compressed JavaScripts.
Potential reduce by 23.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. Indymaven.com has all CSS files already compressed.
Number of requests can be reduced by 95 (75%)
127
32
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indy Maven. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
indymaven.com
79 ms
indymaven.com
106 ms
js
138 ms
sbi-styles.min.css
94 ms
thegem-preloader.css
69 ms
thegem-reset.css
68 ms
thegem-grid.css
60 ms
thegem-header.css
70 ms
style.css
59 ms
style.css
125 ms
thegem-widgets.css
126 ms
thegem-new-css.css
104 ms
thegem-perevazka-css.css
102 ms
css
133 ms
custom-RTT9ufmO.css
106 ms
js_composer.min.css
136 ms
thegem-js_composer_columns.css
154 ms
thegem-additional-blog-1.css
150 ms
jquery.fancybox.min.css
151 ms
thegem-vc_elements.css
152 ms
style.min.css
82 ms
mediaelementplayer-legacy.min.css
92 ms
wp-mediaelement.css
188 ms
font-awesome.min.css
189 ms
angwp.bundle.js.css
176 ms
animate.min.css
175 ms
spr_columns.css
181 ms
sassy-social-share-public.css
181 ms
Defaults.css
183 ms
jquery.min.js
126 ms
jquery-migrate.min.js
93 ms
frontend-gtag.min.js
184 ms
advertising.js
183 ms
icons-fontawesome.css
183 ms
thegem-blog.css
183 ms
thegem-additional-blog.css
258 ms
thegem-itemsAnimations.css
257 ms
css
143 ms
animate.min.css
257 ms
thegem-testimonials.css
261 ms
css
128 ms
formreset.min.css
304 ms
formsmain.min.css
298 ms
readyclass.min.css
258 ms
browsers.min.css
258 ms
core.min.js
89 ms
menu.min.js
89 ms
wp-polyfill-inert.min.js
112 ms
regenerator-runtime.min.js
114 ms
wp-polyfill.min.js
123 ms
dom-ready.min.js
123 ms
hooks.min.js
122 ms
i18n.min.js
123 ms
a11y.min.js
124 ms
autocomplete.min.js
123 ms
e-202410.js
119 ms
api.js
143 ms
thegem-form-elements.js
254 ms
jquery.easing.js
204 ms
SmoothScroll.js
203 ms
jquery.dlmenu.js
204 ms
thegem-menu_init.js
231 ms
thegem-header.js
230 ms
functions.js
214 ms
jquery.mousewheel.pack.js
200 ms
jquery.fancybox.min.js
189 ms
jquery.fancybox-init.js
188 ms
angwp.bundle.js
264 ms
spr_inViewport.js
181 ms
parallax.min.js
160 ms
sassy-social-share-public.js
236 ms
js_composer_front.min.js
290 ms
thegem-scrollMonitor.js
291 ms
jquery.touchSwipe.min.js
291 ms
jquery.carouFredSel.js
207 ms
thegem-gallery.js
261 ms
thegem-itemsAnimations.js
259 ms
thegem-blog-core.js
257 ms
thegem-blog.js
486 ms
news-carousel.js
485 ms
vc-waypoints.min.js
484 ms
testimonials-carousel.js
483 ms
sbi-scripts.min.js
480 ms
fbevents.js
94 ms
gtm.js
146 ms
jquery.json.min.js
424 ms
gravityforms.min.js
524 ms
placeholders.jquery.min.js
415 ms
utils.min.js
522 ms
vendor-theme.min.js
415 ms
scripts-theme.min.js
412 ms
akismet-frontend.js
412 ms
sbi-sprite.png
526 ms
logo_0e512af4f8dd7ca7a6882b02b66831d2_1x.png
519 ms
logo_06e3a8ebd342099c32dadd7310f87308_1x.png
519 ms
Maven-to-Know-Template-36-thegem-blog-slider-halfwidth.png
527 ms
The-Archivist-1-thegem-blog-slider-halfwidth.jpg
493 ms
March-Enneagram-Column-thegem-blog-slider-halfwidth.png
582 ms
March-Horoscope-Header-thegem-blog-slider-halfwidth.png
494 ms
CEE_9863-scaled-thegem-blog-slider-halfwidth.jpg
488 ms
zac-gudakov-wwqZ8CM21gg-unsplash-scaled-thegem-blog-slider-halfwidth.jpg
609 ms
Maven-to-Know-Template-36-thegem-blog-compact.png
609 ms
The-Archivist-1-thegem-blog-compact.jpg
604 ms
March-Enneagram-Column-thegem-blog-compact.png
605 ms
Indy-Maven-Content.jpg
604 ms
Indy-Maven-Curated-Events.jpg
802 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDT.woff
135 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vUDT.woff
358 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebukDT.woff
361 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiukDT.woff
363 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFukDT.woff
363 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsukDT.woff
362 ms
thegem-socials.woff
643 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
362 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
361 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
361 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
365 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
366 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
365 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
365 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
474 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
469 ms
thegem-icons.woff
568 ms
montserrat-ultralight.woff
1060 ms
Indy-Maven-Community.jpg
1008 ms
Indy-Maven-Meetup-Women-Shopping.png
1010 ms
Leslie-Circle-Headshot-300x300.png
1007 ms
placeholder.png
671 ms
INDY-MAVEN-white-logo.png
672 ms
preloader-1.gif
1004 ms
VXKiTNIuN3M
279 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aXw.woff
232 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aXw.woff
231 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9aXw.woff
232 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9aXw.woff
232 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8aXw.woff
234 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6aXw.woff
233 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6aXw.woff
232 ms
font
234 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16aXw.woff
232 ms
font
229 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_pqTbtU.woff
229 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_naUbtU.woff
229 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UbtU.woff
231 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_iiUbtU.woff
230 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUbtU.woff
230 ms
www-player.css
97 ms
www-embed-player.js
132 ms
base.js
159 ms
ad_status.js
623 ms
diffuser.js
625 ms
QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js
159 ms
embed.js
113 ms
id
150 ms
KFOmCnqEu92Fr1Mu4mxM.woff
56 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
56 ms
recaptcha__en.js
215 ms
Create
353 ms
431708295_326853703221761_7753116634926131825_nlow.jpg
15 ms
431727876_1434591050818266_8686280319209237638_nlow.jpg
98 ms
431484349_929395861844247_5403609023747105055_nlow.jpg
98 ms
430865949_366792696311468_6379837784647415128_nlow.jpg
97 ms
430910087_925155478892916_7975479654988111441_nlow.jpg
93 ms
430051796_1548033609279082_9105252932043791716_nlow.jpg
92 ms
indymaven.com 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.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
indymaven.com 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
Browser errors were logged to the console
Page has valid source maps
indymaven.com SEO score
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 Indymaven.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 Indymaven.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.
indymaven.com
Open Graph data is detected on the main page of Indy Maven. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: