Tools & Wizards About Us
indystar.mycapture.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

indystar.mycapture.com

Indianapolis Star

Page Load Speed

2.1 sec in total

First Response

90 ms

Resources Loaded

1.8 sec

Page Rendered

160 ms

indystar.mycapture.com screenshot

About Website

Click here to check amazing Indy Star Mycapture content for United States. Otherwise, check out these important facts you probably never knew about indystar.mycapture.com

Visit indystar.mycapture.com

Key Findings

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

Performance Metrics

indystar.mycapture.com performance score

0

Network Requests Diagram

indystar.mycapture.com

90 ms

index.asp

96 ms

image-slideshow.css

48 ms

Styles-1.2.css

76 ms

affStyles.css

50 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 28% of them (11 requests) were addressed to the original Indystar.mycapture.com, 36% (14 requests) were made to Gannett-cdn.com and 10% (4 requests) were made to Photos.mycapture.com. The less responsive or slowest element that took the longest time to load (636 ms) relates to the external source Indystar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 958.0 kB (77%)

Content Size

1.2 MB

After Optimization

282.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indystar.mycapture.com main page is 1.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. 40% of websites need less resources to load. CSS take 842.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 23.5 kB

  • Original 29.0 kB
  • After minification 24.7 kB
  • After compression 5.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 4.3 kB, which is 15% 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 23.5 kB or 81% of the original size.

Image Optimization

-61%

Potential reduce by 151.9 kB

  • Original 250.7 kB
  • After minification 98.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 Mycapture needs image optimization as it can save up to 151.9 kB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 90.3 kB

  • Original 118.7 kB
  • After minification 54.6 kB
  • After compression 28.4 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 90.3 kB or 76% of the original size.

CSS Optimization

-82%

Potential reduce by 692.2 kB

  • Original 842.4 kB
  • After minification 835.5 kB
  • After compression 150.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.mycapture.com needs all CSS files to be minified and compressed as it can save up to 692.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (31%)

Requests Now

32

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indystar.mycapture.com

indystar.mycapture.com

90 ms

index.asp

index.asp

96 ms

image-slideshow.css

image-slideshow.css

48 ms

Styles-1.2.css

Styles-1.2.css

76 ms

affStyles.css

affStyles.css

50 ms

image-slideshow.js

image-slideshow.js

51 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

52 ms

gpt.js

gpt.js

21 ms

utag.js

utag.js

8 ms

312 ms

636 ms

noise_f6f6f6.png

noise_f6f6f6.png

17 ms

58236269T.jpg

58236269T.jpg

219 ms

poweredby_light.png

poweredby_light.png

65 ms

54713786T.jpg

54713786T.jpg

101 ms

29271320T.jpg

29271320T.jpg

97 ms

28638910T.jpg

28638910T.jpg

107 ms

top-bkgd.jpg

top-bkgd.jpg

54 ms

topRight.jpg

topRight.jpg

52 ms

btm-bkgd.jpg

btm-bkgd.jpg

52 ms

bottomRight.jpg

bottomRight.jpg

52 ms

ga.js

ga.js

6 ms

36 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

28 ms

show_ads.js

show_ads.js

4 ms

main_modern.min.css

main_modern.min.css

52 ms

require.js

require.js

16 ms

poweredby_light.png

poweredby_light.png

159 ms

noise_f6f6f6.png

noise_f6f6f6.png

7 ms

site-masthead-logo@2x.png

site-masthead-logo@2x.png

134 ms

site-nav-logo@2x.png

site-nav-logo@2x.png

6 ms

header-sprite.png

header-sprite.png

8 ms

multi-header.js

multi-header.js

129 ms

futura_today_demibold.woff

futura_today_demibold.woff

8 ms

futura_today_normal.woff

futura_today_normal.woff

11 ms

futura_today_bold.woff

futura_today_bold.woff

11 ms

print.css

print.css

7 ms

framework-config.js

framework-config.js

15 ms

SEO Factors

indystar.mycapture.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indystar.mycapture.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.mycapture.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

indystar.mycapture.com

Open Graph description is not detected on the main page of Indy Star Mycapture. 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: