Tools & Wizards About Us
indytoday.6amcity.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

indytoday.6amcity.com

INDYtoday | Your Resource for All Things Indianapolis, IN

Page Load Speed

3.1 sec in total

First Response

10 ms

Resources Loaded

1.9 sec

Page Rendered

1.2 sec

indytoday.6amcity.com screenshot

About Website

Welcome to indytoday.6amcity.com homepage info - get ready to check INDYtoday 6 Amcity best content for United States right away, or after learning these important things about indytoday.6amcity.com

INDYtoday is Your Resource for the Best of What You Need to Know About Indianapolis, IN – Curated, Condensed & Delivered to Your Inbox & Social Feeds.

Visit indytoday.6amcity.com

Key Findings

We analyzed Indytoday.6amcity.com page load time and found that the first response time was 10 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.

Performance Metrics

indytoday.6amcity.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value7,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.292

41/100

15%

TTI (Time to Interactive)

Value45.3 s

0/100

10%

Network Requests Diagram

indytoday.6amcity.com

10 ms

indytoday.6amcity.com

432 ms

All.min.d336e284dc318be0d433024f02542529.gz.css

52 ms

webcomponents-loader.2938a610ca02c611209b1a5ba2884385.gz.js

65 ms

All.min.5b7f2774668689f25efa05fa9c8983ec.gz.js

67 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Indytoday.6amcity.com, 31% (33 requests) were made to 6amcity.brightspotcdn.com and 18% (19 requests) were made to Cdn59755463.blazingcdn.net. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 605.1 kB (11%)

Content Size

5.6 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indytoday.6amcity.com main page is 5.6 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 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 231.0 kB

  • Original 275.9 kB
  • After minification 243.0 kB
  • After compression 44.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. This page needs HTML code to be minified as it can gain 32.9 kB, which is 12% 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 231.0 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 364.4 kB

  • Original 4.2 MB
  • After minification 3.8 MB

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. INDYtoday 6 Amcity images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 8.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.1 MB

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

-5%

Potential reduce by 1.8 kB

  • Original 38.1 kB
  • After minification 38.1 kB
  • After compression 36.3 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. Indytoday.6amcity.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (45%)

Requests Now

76

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indytoday.6amcity.com

indytoday.6amcity.com

10 ms

indytoday.6amcity.com

indytoday.6amcity.com

432 ms

All.min.d336e284dc318be0d433024f02542529.gz.css

All.min.d336e284dc318be0d433024f02542529.gz.css

52 ms

webcomponents-loader.2938a610ca02c611209b1a5ba2884385.gz.js

webcomponents-loader.2938a610ca02c611209b1a5ba2884385.gz.js

65 ms

All.min.5b7f2774668689f25efa05fa9c8983ec.gz.js

All.min.5b7f2774668689f25efa05fa9c8983ec.gz.js

67 ms

init-2.min.js

init-2.min.js

73 ms

CitySparkModule.js

CitySparkModule.js

304 ms

get.js

get.js

64 ms

element.js

element.js

87 ms

tag

tag

72 ms

bsp-analytics.min.3d492319d8b084de04ab3a208c32f0b5.gz.js

bsp-analytics.min.3d492319d8b084de04ab3a208c32f0b5.gz.js

63 ms

gotham.css

gotham.css

109 ms

tag

tag

19 ms

IEPolyfills.3af8d32fc874177c8b40f77d0ae336b5.gz.js

IEPolyfills.3af8d32fc874177c8b40f77d0ae336b5.gz.js

33 ms

gtm.js

gtm.js

152 ms

sdk.js

sdk.js

119 ms

7360.js

7360.js

182 ms

css

css

229 ms

128 ms

indy-topphonesubmodule.png

indy-topphonesubmodule.png

164 ms

237 ms

163 ms

165 ms

242 ms

240 ms

236 ms

239 ms

236 ms

242 ms

247 ms

244 ms

243 ms

242 ms

243 ms

245 ms

247 ms

246 ms

245 ms

249 ms

247 ms

248 ms

250 ms

248 ms

251 ms

250 ms

249 ms

10754.jsx

10754.jsx

231 ms

sdk.js

sdk.js

88 ms

fbevents.js

fbevents.js

70 ms

js

js

166 ms

4076190.js

4076190.js

329 ms

spm.v1.min.js

spm.v1.min.js

277 ms

a-092l.min.js

a-092l.min.js

328 ms

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

317 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

395 ms

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

641 ms

337 ms

WidgetTemplate.min.css

WidgetTemplate.min.css

172 ms

angular.min.js

angular.min.js

368 ms

widgetcombined2.min.js

widgetcombined2.min.js

226 ms

widget.js

widget.js

322 ms

p-uq0GLFySb_d1T.gif

p-uq0GLFySb_d1T.gif

193 ms

team_f27b7875ab9f.js

team_f27b7875ab9f.js

500 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

367 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

396 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

366 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

395 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

395 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

408 ms

icomoon.woff

icomoon.woff

98 ms

6amcity_c398d_6am.js

6amcity_c398d_6am.js

392 ms

ads.min.js

ads.min.js

484 ms

banner.js

banner.js

388 ms

web-interactives-embed.js

web-interactives-embed.js

398 ms

4076190.js

4076190.js

458 ms

widget_app_base_1710008228184.js

widget_app_base_1710008228184.js

245 ms

ajax-loader.gif

ajax-loader.gif

203 ms

d41TygENF0SUTDAlLh38_g.medium.jpg

d41TygENF0SUTDAlLh38_g.medium.jpg

175 ms

6TnW1OAABkSPgu-Hbb5_Yg.medium.jpg

6TnW1OAABkSPgu-Hbb5_Yg.medium.jpg

173 ms

GRvJuGmUGUCJ347E1Rl5iw.medium.jpg

GRvJuGmUGUCJ347E1Rl5iw.medium.jpg

197 ms

0uVSBvUJFUCBpV8weAPD_A.medium.png

0uVSBvUJFUCBpV8weAPD_A.medium.png

213 ms

lFx925BaXUyAbdypmkb2QA.medium.jpg

lFx925BaXUyAbdypmkb2QA.medium.jpg

213 ms

L-dCS7l_Bk67Y2p1v62Pxg.medium.jpg

L-dCS7l_Bk67Y2p1v62Pxg.medium.jpg

217 ms

C1UR-lw3YUKst28EpXj0dA.medium.jpg

C1UR-lw3YUKst28EpXj0dA.medium.jpg

211 ms

1EcySeNF20Odq04ArOdGew.medium.png

1EcySeNF20Odq04ArOdGew.medium.png

217 ms

QZyqB_kzIEaOjve7Lqw02Q.medium.jpg

QZyqB_kzIEaOjve7Lqw02Q.medium.jpg

210 ms

8IWsTUg8BEaEUcWH8bXqhw.medium.png

8IWsTUg8BEaEUcWH8bXqhw.medium.png

212 ms

c0fe6339-2077-4ca6-a890-64ee86c90f68.medium.png

c0fe6339-2077-4ca6-a890-64ee86c90f68.medium.png

217 ms

Uv_z_MHlhUC-4U07K6-hwg.medium.png

Uv_z_MHlhUC-4U07K6-hwg.medium.png

217 ms

b6de82da-1d91-47ae-b28b-7eae174b2f21.medium.PNG

b6de82da-1d91-47ae-b28b-7eae174b2f21.medium.PNG

212 ms

395ea931-9340-456a-952d-94f16b937e14.medium.png

395ea931-9340-456a-952d-94f16b937e14.medium.png

215 ms

Xp9s9ngFHEi9s6u28U1R0w.medium.png

Xp9s9ngFHEi9s6u28U1R0w.medium.png

216 ms

VbiyqLFFGk24Zhar3kCSlA.medium.jpg

VbiyqLFFGk24Zhar3kCSlA.medium.jpg

231 ms

8h7jXJGEa0yPApzv0lYQ8g.medium.jpg

8h7jXJGEa0yPApzv0lYQ8g.medium.jpg

232 ms

c78057ba-b40c-484a-a845-22ab8e251692.medium.png

c78057ba-b40c-484a-a845-22ab8e251692.medium.png

242 ms

tVq1c-dBekiaN_PNRwJuwg.medium.jpg

tVq1c-dBekiaN_PNRwJuwg.medium.jpg

232 ms

p-uq0GLFySb_d1T.gif

p-uq0GLFySb_d1T.gif

94 ms

load-cookie.html

load-cookie.html

98 ms

rid

rid

74 ms

apstag.js

apstag.js

71 ms

gpt.js

gpt.js

118 ms

prebid.min.js

prebid.min.js

46 ms

adthrive.min.js

adthrive.min.js

69 ms

cookie_sync

cookie_sync

95 ms

pubads_impl.js

pubads_impl.js

6 ms

Accessibility Review

indytoday.6amcity.com accessibility score

94

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-hidden="true"] elements contain focusable descendents

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.

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

High

<frame> or <iframe> elements do not have a title

Best Practices

indytoday.6amcity.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

indytoday.6amcity.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Indytoday.6amcity.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 Indytoday.6amcity.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

indytoday.6amcity.com

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