Tools & Wizards About Us
indexjournal.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

indexjournal.com

Index-Journal | indexjournal.com | The leading source for news in Greenwood, S.C. and across the Lakelands

Page Load Speed

2.6 sec in total

First Response

81 ms

Resources Loaded

2 sec

Page Rendered

537 ms

indexjournal.com screenshot

About Website

Welcome to indexjournal.com homepage info - get ready to check Index Journal best content for United States right away, or after learning these important things about indexjournal.com

The leading source for news, obituaries, opinion and sports in Greenwood, South Carolina and across the Lakelands.

Visit indexjournal.com

Key Findings

We analyzed Indexjournal.com page load time and found that the first response time was 81 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

indexjournal.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value3,900 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

indexjournal.com

81 ms

www.indexjournal.com

76 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

118 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

103 ms

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

114 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 8% of them (7 requests) were addressed to the original Indexjournal.com, 35% (33 requests) were made to Bloximages.newyork1.vip.townnews.com and 6% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source Invstatic101.creativecdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 747.5 kB (44%)

Content Size

1.7 MB

After Optimization

954.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indexjournal.com main page is 1.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 786.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 580.9 kB

  • Original 652.3 kB
  • After minification 566.8 kB
  • After compression 71.4 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 85.5 kB, which is 13% 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 580.9 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 183.0 kB
  • After minification 183.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. Index Journal images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 149.7 kB

  • Original 786.5 kB
  • After minification 786.3 kB
  • After compression 636.8 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 149.7 kB or 19% of the original size.

CSS Optimization

-21%

Potential reduce by 16.9 kB

  • Original 79.9 kB
  • After minification 79.9 kB
  • After compression 63.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. Indexjournal.com needs all CSS files to be minified and compressed as it can save up to 16.9 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (70%)

Requests Now

87

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indexjournal.com

indexjournal.com

81 ms

www.indexjournal.com

www.indexjournal.com

76 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

118 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

103 ms

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

114 ms

theme-traditional.css

theme-traditional.css

110 ms

tntslider.61e562ee97efb10698d15f5cee4962dc.css

tntslider.61e562ee97efb10698d15f5cee4962dc.css

115 ms

flex-utility-promo-button.52347555fbb6668223efabadb9c9d111.css

flex-utility-promo-button.52347555fbb6668223efabadb9c9d111.css

117 ms

flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css

flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css

123 ms

otSDKStub.js

otSDKStub.js

89 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

60 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

122 ms

user.js

user.js

81 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

122 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

123 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

125 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

132 ms

polyfill.min.js

polyfill.min.js

313 ms

user-controls.578df3df79d812af55ab13bae47f9857.js

user-controls.578df3df79d812af55ab13bae47f9857.js

128 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

139 ms

gpt.js

gpt.js

167 ms

tntslider.7177a362b66d47f546bd877a7efd6bd4.js

tntslider.7177a362b66d47f546bd877a7efd6bd4.js

139 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

239 ms

tracking.js

tracking.js

87 ms

otCCPAiab.js

otCCPAiab.js

111 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

135 ms

tracker.js

tracker.js

86 ms

delivery.js

delivery.js

74 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

73 ms

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

156 ms

sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js

sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js

157 ms

tnt.regions.b44801b45845a81b995eeaad12f4f276.js

tnt.regions.b44801b45845a81b995eeaad12f4f276.js

156 ms

embed.js

embed.js

39 ms

embed.js

embed.js

37 ms

css

css

35 ms

gtm.js

gtm.js

45 ms

376d3734-7e20-4d9d-bfce-f228e59b1d02.json

376d3734-7e20-4d9d-bfce-f228e59b1d02.json

33 ms

location

location

64 ms

analytics.js

analytics.js

16 ms

gtm.js

gtm.js

23 ms

gtm.js

gtm.js

75 ms

otBannerSdk.js

otBannerSdk.js

32 ms

publisher:getClientId

publisher:getClientId

206 ms

gtm.js

gtm.js

105 ms

en.json

en.json

149 ms

apstag.js

apstag.js

154 ms

6647a78ff046f.image.jpg

6647a78ff046f.image.jpg

149 ms

6645425c4da9b.image.jpg

6645425c4da9b.image.jpg

149 ms

6642ca3e464b0.image.jpg

6642ca3e464b0.image.jpg

148 ms

6644c8f24bd46.image.jpg

6644c8f24bd46.image.jpg

125 ms

66423ef078fa3.image.jpg

66423ef078fa3.image.jpg

125 ms

6642606574d14.image.jpg

6642606574d14.image.jpg

124 ms

66392917df0cc.image.jpg

66392917df0cc.image.jpg

151 ms

6644c1e2455d0.image.jpg

6644c1e2455d0.image.jpg

153 ms

6644fa1a0e86f.image.jpg

6644fa1a0e86f.image.jpg

152 ms

6644fa1a0e86f.image.jpg

6644fa1a0e86f.image.jpg

153 ms

6643e55b1457d.image.jpg

6643e55b1457d.image.jpg

150 ms

663c1a7cbfb80.image.jpg

663c1a7cbfb80.image.jpg

151 ms

pubads_impl.js

pubads_impl.js

94 ms

dnsfeed

dnsfeed

95 ms

tracker.gif

tracker.gif

87 ms

analytics.min.js

analytics.min.js

188 ms

collect

collect

243 ms

collect

collect

376 ms

collect

collect

369 ms

apstag.js

apstag.js

194 ms

destination

destination

195 ms

destination

destination

210 ms

otFlat.json

otFlat.json

176 ms

otPcCenter.json

otPcCenter.json

280 ms

132916964

132916964

313 ms

settings

settings

122 ms

collect

collect

107 ms

UMBQrPtMoH62xUZKdK0vfQr9.ttf

UMBQrPtMoH62xUZKdK0vfQr9.ttf

120 ms

UMBTrPtMoH62xUZCz4g_.ttf

UMBTrPtMoH62xUZCz4g_.ttf

120 ms

dbc09c4a-23c4-11ed-9bda-3b977795c43b.jpg

dbc09c4a-23c4-11ed-9bda-3b977795c43b.jpg

34 ms

870.bundle.6e2976b75e60ab2b2bf8.js

870.bundle.6e2976b75e60ab2b2bf8.js

9 ms

tsub-middleware.bundle.77315eced46c5ae4c052.js

tsub-middleware.bundle.77315eced46c5ae4c052.js

9 ms

uid2SecureSignal.js

uid2SecureSignal.js

280 ms

esp.js

esp.js

281 ms

publishertag.ids.js

publishertag.ids.js

250 ms

esp.js

esp.js

295 ms

encrypted-tag-g.js

encrypted-tag-g.js

641 ms

sync.min.js

sync.min.js

280 ms

pubcid.min.js

pubcid.min.js

294 ms

ob.js

ob.js

308 ms

polyfill.min.js

polyfill.min.js

419 ms

AGSKWxVtoYNq9Htea8qSfp5ub4obuzY5Fbvy038eQT3k7Gbf-hz7_OHsoVutCax__BNfSKHQ0PUQguNP9CLBGLM2JXZOKu9b_GTGW7xZ5Pk6tW1C7_cIoP-U0r0SqeEV6_FLJP6xkyn9MQ==

AGSKWxVtoYNq9Htea8qSfp5ub4obuzY5Fbvy038eQT3k7Gbf-hz7_OHsoVutCax__BNfSKHQ0PUQguNP9CLBGLM2JXZOKu9b_GTGW7xZ5Pk6tW1C7_cIoP-U0r0SqeEV6_FLJP6xkyn9MQ==

128 ms

quant.js

quant.js

112 ms

map

map

74 ms

rules-p-3e-uVCg6cksA_.js

rules-p-3e-uVCg6cksA_.js

37 ms

pixel;r=1027049974;source=gtm;rf=0;a=p-3e-uVCg6cksA_;url=https%3A%2F%2Fwww.indexjournal.com%2F;uh=u;uht=u;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;us_privacy=1YYN;gpp_sid=-1;ref=;d=indexjournal.com;dst=0;et=1715973559697;tzo=-180;ogl=type.website%2Curl.https%3A%2F%2Fwww%252Eindexjournal%252Ecom%2F%2Cimage.https%3A%2F%2Fbloximages%252Enewyork1%252Evip%252Etownnews%252Ecom%2Findexjournal%252Ecom%2Fcontent%2Ftncms%2Fcust%2Cimage%3Awidth.600%2Cimage%3Aheight.438%2Ctitle.indexjournal%252Ecom%20%7C%20The%20leading%20source%20for%20news%20in%20Greenwood%252C%20S%252EC%252E%20and%20across%20the%2Cdescription.The%20leading%20source%20for%20news%252C%20obituaries%252C%20opinion%20and%20sports%20in%20Greenwood%252C%20South%20%2Csite_name.Index-Journal;ses=8cd01e3b-c941-46e8-ba7f-d41bd3338446;mdl=

pixel;r=1027049974;source=gtm;rf=0;a=p-3e-uVCg6cksA_;url=https%3A%2F%2Fwww.indexjournal.com%2F;uh=u;uht=u;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;us_privacy=1YYN;gpp_sid=-1;ref=;d=indexjournal.com;dst=0;et=1715973559697;tzo=-180;ogl=type.website%2Curl.https%3A%2F%2Fwww%252Eindexjournal%252Ecom%2F%2Cimage.https%3A%2F%2Fbloximages%252Enewyork1%252Evip%252Etownnews%252Ecom%2Findexjournal%252Ecom%2Fcontent%2Ftncms%2Fcust%2Cimage%3Awidth.600%2Cimage%3Aheight.438%2Ctitle.indexjournal%252Ecom%20%7C%20The%20leading%20source%20for%20news%20in%20Greenwood%252C%20S%252EC%252E%20and%20across%20the%2Cdescription.The%20leading%20source%20for%20news%252C%20obituaries%252C%20opinion%20and%20sports%20in%20Greenwood%252C%20South%20%2Csite_name.Index-Journal;ses=8cd01e3b-c941-46e8-ba7f-d41bd3338446;mdl=

26 ms

pwt.js

pwt.js

18 ms

Accessibility Review

indexjournal.com accessibility score

93

Accessibility Issues

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

indexjournal.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

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

indexjournal.com SEO score

84

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Indexjournal.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 Indexjournal.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

indexjournal.com

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