Tools & Wizards About Us
indystar.newspapers.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

indystar.newspapers.com

Indianapolis Star archive from 1862-2024 - Indianapolis Star Archive

Page Load Speed

3.2 sec in total

First Response

856 ms

Resources Loaded

2.1 sec

Page Rendered

194 ms

indystar.newspapers.com screenshot

About Website

Visit indystar.newspapers.com now to see the best up-to-date Indy Star Newspapers content for United States and also check out these interesting facts you probably never knew about indystar.newspapers.com

The largest online newspaper archive. Used by millions every month for historical research, family history, crime investigations, journalism, and more.

Visit indystar.newspapers.com

Key Findings

We analyzed Indystar.newspapers.com page load time and found that the first response time was 856 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

indystar.newspapers.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value4,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

indystar.newspapers.com

856 ms

base.css

9 ms

search.css

30 ms

clippings.css

37 ms

papers.css

221 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 21% of them (30 requests) were addressed to the original Indystar.newspapers.com, 52% (75 requests) were made to Gannett-cdn.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (856 ms) belongs to the original domain Indystar.newspapers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (65%)

Content Size

2.9 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indystar.newspapers.com main page is 2.9 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. 70% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.4 kB

  • Original 39.9 kB
  • After minification 39.8 kB
  • After compression 9.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. 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 30.4 kB or 76% of the original size.

Image Optimization

-34%

Potential reduce by 246.3 kB

  • Original 728.0 kB
  • After minification 481.8 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 Star Newspapers needs image optimization as it can save up to 246.3 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 617.5 kB

  • Original 905.1 kB
  • After minification 842.5 kB
  • After compression 287.7 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 617.5 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 953.1 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 226.1 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. Indystar.newspapers.com needs all CSS files to be minified and compressed as it can save up to 953.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (71%)

Requests Now

136

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indystar.newspapers.com

indystar.newspapers.com

856 ms

base.css

base.css

9 ms

search.css

search.css

30 ms

clippings.css

clippings.css

37 ms

papers.css

papers.css

221 ms

index.css

index.css

33 ms

generic-silo.css

generic-silo.css

26 ms

mbox_ancestry.js

mbox_ancestry.js

33 ms

require.js

require.js

35 ms

css

css

31 ms

analytics.js

analytics.js

50 ms

utag.js

utag.js

50 ms

300.jpg

300.jpg

40 ms

300.jpg

300.jpg

40 ms

483_2713_397_335.jpg

483_2713_397_335.jpg

222 ms

3764_3624_732_400.jpg

3764_3624_732_400.jpg

131 ms

1703_187_1592_5130.jpg

1703_187_1592_5130.jpg

198 ms

1587_3326_650_1150.jpg

1587_3326_650_1150.jpg

224 ms

704_1644_722_1178.jpg

704_1644_722_1178.jpg

230 ms

2997_5127_606_606.jpg

2997_5127_606_606.jpg

199 ms

img.gif

img.gif

31 ms

pfray.png

pfray.png

36 ms

global-sprite.png

global-sprite.png

36 ms

1280

1280

547 ms

search-spriteA.png

search-spriteA.png

33 ms

help-wanted-home.png

help-wanted-home.png

32 ms

help-intro.png

help-intro.png

31 ms

help-search.png

help-search.png

34 ms

cursor-zoom.png

cursor-zoom.png

34 ms

ann-prevbgLdk.png

ann-prevbgLdk.png

60 ms

usericon.php

usericon.php

157 ms

usericon.php

usericon.php

226 ms

usericon.php

usericon.php

256 ms

usericon.php

usericon.php

235 ms

pwdbynewslogo-wht.png

pwdbynewslogo-wht.png

64 ms

PVOGkCtOX7e_D5p8KeOQ4_esZW2xOQ-xsNqO47m55DA.ttf

PVOGkCtOX7e_D5p8KeOQ4_esZW2xOQ-xsNqO47m55DA.ttf

25 ms

EWSoWmYPmujCiQESfOIkHgLUuEpTyoUstqEm5AMlJo4.ttf

EWSoWmYPmujCiQESfOIkHgLUuEpTyoUstqEm5AMlJo4.ttf

27 ms

9rDoLGxnhE7pBioG-6m53-vvDin1pK8aKteLpeZ5c0A.ttf

9rDoLGxnhE7pBioG-6m53-vvDin1pK8aKteLpeZ5c0A.ttf

27 ms

Vj6JEk1YZr8j8R8H2j0b-iZ2oysoEQEeKwjgmXLRnTc.ttf

Vj6JEk1YZr8j8R8H2j0b-iZ2oysoEQEeKwjgmXLRnTc.ttf

27 ms

newsicons-regular.woff

newsicons-regular.woff

33 ms

collect

collect

18 ms

standard

standard

166 ms

collect

collect

70 ms

utag.3.js

utag.3.js

24 ms

utag.12.js

utag.12.js

6 ms

jquery.min.js

jquery.min.js

42 ms

core.js

core.js

8 ms

app.home.main.js

app.home.main.js

39 ms

s66157922139391

s66157922139391

31 ms

js

js

29 ms

aj_getMastMembercard

aj_getMastMembercard

223 ms

aj_getbasicfacets

aj_getbasicfacets

395 ms

process.gif

process.gif

5 ms

36 ms

sdk.js

sdk.js

136 ms

utag.js

utag.js

10 ms

gpt.js

gpt.js

30 ms

pubads_impl_82.js

pubads_impl_82.js

9 ms

container.html

container.html

18 ms

noise_f6f6f6.png

noise_f6f6f6.png

20 ms

id

id

10 ms

id

id

191 ms

52 ms

207 ms

show_ads.js

show_ads.js

10 ms

main_modern.min.css

main_modern.min.css

43 ms

require.js

require.js

27 ms

xd_arbiter.php

xd_arbiter.php

289 ms

xd_arbiter.php

xd_arbiter.php

492 ms

noise_f6f6f6.png

noise_f6f6f6.png

27 ms

site-masthead-logo@2x.png

site-masthead-logo@2x.png

39 ms

site-nav-logo@2x.png

site-nav-logo@2x.png

26 ms

header-sprite.png

header-sprite.png

38 ms

futura_today_demibold.woff

futura_today_demibold.woff

41 ms

futura_today_normal.woff

futura_today_normal.woff

40 ms

futura_today_bold.woff

futura_today_bold.woff

40 ms

multi-header.js

multi-header.js

25 ms

event

event

30 ms

framework-config.js

framework-config.js

11 ms

print.css

print.css

11 ms

jquery.require.js

jquery.require.js

16 ms

underscore.js

underscore.js

15 ms

statemanager.js

statemanager.js

15 ms

header.js

header.js

15 ms

pubsub.js

pubsub.js

7 ms

utils.js

utils.js

7 ms

alert.js

alert.js

12 ms

trafficcop.js

trafficcop.js

8 ms

requestmanager.js

requestmanager.js

11 ms

resourcemanager.js

resourcemanager.js

11 ms

siteconfig.js

siteconfig.js

23 ms

base-app.js

base-app.js

194 ms

usermanager.js

usermanager.js

22 ms

routemanager.js

routemanager.js

26 ms

breaking-news.js

breaking-news.js

27 ms

direct-ad-position.js

direct-ad-position.js

193 ms

site-nav-more-module.js

site-nav-more-module.js

195 ms

userUtil.js

userUtil.js

26 ms

privacyNotice.js

privacyNotice.js

27 ms

console.setup.js

console.setup.js

25 ms

site-config.js

site-config.js

9 ms

cachemanager.js

cachemanager.js

8 ms

base-view.js

base-view.js

9 ms

barrier.js

barrier.js

8 ms

livevideo.js

livevideo.js

14 ms

alertsmanager.js

alertsmanager.js

14 ms

jquery-2.1.4.js

jquery-2.1.4.js

23 ms

css-transition-lib.js

css-transition-lib.js

7 ms

jquery.transformSupport.js

jquery.transformSupport.js

8 ms

brightcove-video.js

brightcove-video.js

30 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

23 ms

jquery.animate-colors-min.js

jquery.animate-colors-min.js

122 ms

backbone-dev.js

backbone-dev.js

23 ms

admanager.js

admanager.js

108 ms

ad-logger.js

ad-logger.js

12 ms

jquery.cookie.js

jquery.cookie.js

12 ms

s66683321050368

s66683321050368

171 ms

ad-position.js

ad-position.js

9 ms

sitemanager.js

sitemanager.js

7 ms

site-nav-dropdown.js

site-nav-dropdown.js

7 ms

ad-slot.js

ad-slot.js

7 ms

memobarrier.js

memobarrier.js

7 ms

autoplay.js

autoplay.js

9 ms

abtestmanager.js

abtestmanager.js

8 ms

templatemanager.js

templatemanager.js

7 ms

iab.js

iab.js

10 ms

template-utils.js

template-utils.js

5 ms

cxense-base.js

cxense-base.js

6 ms

swfobject.js

swfobject.js

6 ms

carousel-fullscreen.js

carousel-fullscreen.js

5 ms

carousel-autosize.js

carousel-autosize.js

6 ms

carousel.js

carousel.js

7 ms

gallery.js

gallery.js

7 ms

controls.js

controls.js

15 ms

thumbs.js

thumbs.js

7 ms

companion.js

companion.js

7 ms

taboola.js

taboola.js

8 ms

metered-ad-position.js

metered-ad-position.js

7 ms

horizontal-scroll.js

horizontal-scroll.js

7 ms

companion-ad.js

companion-ad.js

8 ms

myCapture.js

myCapture.js

5 ms

base-scroll.js

base-scroll.js

10 ms

simple-ad.js

simple-ad.js

11 ms

Accessibility Review

indystar.newspapers.com accessibility score

78

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-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

indystar.newspapers.com best practices score

92

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

Page has valid source maps

SEO Factors

indystar.newspapers.com SEO score

100

Search Engine Optimization Advices

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

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 Indystar.newspapers.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 Indystar.newspapers.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

indystar.newspapers.com

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