Tools & Wizards About Us
lakeshorepublicmedia.org screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

lakeshorepublicmedia.org

Home

Page Load Speed

3 sec in total

First Response

170 ms

Resources Loaded

2 sec

Page Rendered

889 ms

lakeshorepublicmedia.org screenshot

About Website

Welcome to lakeshorepublicmedia.org homepage info - get ready to check Lakeshorepublicmedia best content for United States right away, or after learning these important things about lakeshorepublicmedia.org

Lakeshore Public Media is Northwest Indiana and Chicagoland's Public Broadcasting Station since 1987

Visit lakeshorepublicmedia.org

Key Findings

We analyzed Lakeshorepublicmedia.org page load time and found that the first response time was 170 ms and then it took 2.9 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

lakeshorepublicmedia.org performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

55/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,760 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

lakeshorepublicmedia.org

170 ms

www.lakeshorepublicmedia.org

60 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

44 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

121 ms

gpt.js

121 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Lakeshorepublicmedia.org, 73% (40 requests) were made to Npr.brightspotcdn.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Clarity.ms.

Page Optimization Overview & Recommendations

Page size can be reduced by 418.0 kB (14%)

Content Size

3.0 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lakeshorepublicmedia.org main page is 3.0 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. 75% 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. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 211.4 kB

  • Original 248.3 kB
  • After minification 206.9 kB
  • After compression 36.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 41.4 kB, which is 17% 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 211.4 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 108.4 kB

  • Original 2.1 MB
  • After minification 2.0 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. Lakeshorepublicmedia images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 97.0 kB

  • Original 602.3 kB
  • After minification 597.8 kB
  • After compression 505.3 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 97.0 kB or 16% of the original size.

CSS Optimization

-2%

Potential reduce by 1.3 kB

  • Original 67.6 kB
  • After minification 67.6 kB
  • After compression 66.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. Lakeshorepublicmedia.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (17%)

Requests Now

46

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lakeshorepublicmedia.org

lakeshorepublicmedia.org

170 ms

www.lakeshorepublicmedia.org

www.lakeshorepublicmedia.org

60 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

All.min.ab6eee59525552b9100e33650d638008.gz.css

44 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

121 ms

gpt.js

gpt.js

121 ms

classic-061523.css

classic-061523.css

104 ms

mc-validate.js

mc-validate.js

171 ms

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

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

79 ms

gtm.js

gtm.js

424 ms

sdk.js

sdk.js

114 ms

kcm3iomi0y

kcm3iomi0y

1694 ms

css

css

201 ms

29 ms

40 ms

339 ms

338 ms

91 ms

91 ms

92 ms

338 ms

97 ms

97 ms

100 ms

100 ms

184 ms

pubads_impl.js

pubads_impl.js

21 ms

sdk.js

sdk.js

86 ms

87 ms

79 ms

80 ms

79 ms

77 ms

346 ms

82 ms

81 ms

80 ms

81 ms

82 ms

artboard-1.png

artboard-1.png

83 ms

81 ms

83 ms

84 ms

87 ms

86 ms

88 ms

87 ms

87 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

69 ms

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

44 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

156 ms

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

44 ms

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

43 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

156 ms

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

44 ms

138 ms

Accessibility Review

lakeshorepublicmedia.org accessibility score

98

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.

Best Practices

lakeshorepublicmedia.org 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

Missing source maps for large first-party JavaScript

SEO Factors

lakeshorepublicmedia.org 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

robots.txt is not valid

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 Lakeshorepublicmedia.org 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 Lakeshorepublicmedia.org 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

lakeshorepublicmedia.org

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