Tools & Wizards About Us
stlpublicradio.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

stlpublicradio.org

STLPR - Homepage | STLPR

Page Load Speed

3 sec in total

First Response

142 ms

Resources Loaded

1.9 sec

Page Rendered

906 ms

stlpublicradio.org screenshot

About Website

Click here to check amazing Stlpublicradio content for United States. Otherwise, check out these important facts you probably never knew about stlpublicradio.org

Delivering accuracy and understanding through storytelling revealing context and humanity in the news. Award-winning local and NPR news, podcasts and music

Visit stlpublicradio.org

Key Findings

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

stlpublicradio.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value3,820 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.073

95/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

stlpublicradio.org

142 ms

www.stlpr.org

469 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

50 ms

all.min.css

74 ms

det1xcl.css

77 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Stlpublicradio.org, 37% (32 requests) were made to Npr.brightspotcdn.com and 10% (9 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (598 ms) relates to the external source Signup.e2ma.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 348.6 kB (18%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stlpublicradio.org main page is 1.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. Only a small number of websites need less resources to load. Javascripts take 964.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 193.2 kB

  • Original 230.8 kB
  • After minification 192.5 kB
  • After compression 37.7 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 38.3 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 193.2 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 23.5 kB

  • Original 623.4 kB
  • After minification 599.9 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. Stlpublicradio images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 104.4 kB

  • Original 964.1 kB
  • After minification 964.1 kB
  • After compression 859.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 104.4 kB or 11% of the original size.

CSS Optimization

-24%

Potential reduce by 27.6 kB

  • Original 116.8 kB
  • After minification 116.8 kB
  • After compression 89.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. Stlpublicradio.org needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

68

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stlpublicradio.org

stlpublicradio.org

142 ms

www.stlpr.org

www.stlpr.org

469 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

All.min.ab6eee59525552b9100e33650d638008.gz.css

50 ms

all.min.css

all.min.css

74 ms

det1xcl.css

det1xcl.css

77 ms

html-modules.css

html-modules.css

70 ms

main.css

main.css

87 ms

print.css

print.css

77 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

66 ms

gpt.js

gpt.js

151 ms

glade.js

glade.js

96 ms

js

js

74 ms

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

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

39 ms

p.css

p.css

31 ms

sdk.js

sdk.js

84 ms

gtm.js

gtm.js

85 ms

js

js

214 ms

css

css

301 ms

60 ms

208 ms

584 ms

49 ms

52 ms

139 ms

139 ms

138 ms

137 ms

138 ms

204 ms

204 ms

205 ms

205 ms

204 ms

285 ms

285 ms

350 ms

286 ms

547 ms

548 ms

547 ms

575 ms

578 ms

580 ms

pubads_impl.js

pubads_impl.js

112 ms

ppub_config

ppub_config

168 ms

sdk.js

sdk.js

151 ms

js

js

244 ms

js

js

240 ms

analytics.js

analytics.js

467 ms

gtm.js

gtm.js

451 ms

chartbeat.js

chartbeat.js

448 ms

598 ms

soundwave-trimmed-white-with-gap.png

soundwave-trimmed-white-with-gap.png

233 ms

d

d

124 ms

d

d

160 ms

d

d

163 ms

d

d

210 ms

d

d

163 ms

d

d

164 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

333 ms

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

163 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

372 ms

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

159 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

407 ms

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

158 ms

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

158 ms

d

d

241 ms

d

d

330 ms

ping

ping

315 ms

collect

collect

91 ms

collect

collect

174 ms

collect

collect

168 ms

collect

collect

256 ms

collect

collect

168 ms

collect

collect

252 ms

destination

destination

145 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

263 ms

d1b8bc557dd0bcfc9e12b7605442bfbb3a54214a-compiled-public-forms.css

d1b8bc557dd0bcfc9e12b7605442bfbb3a54214a-compiled-public-forms.css

227 ms

css2

css2

130 ms

react.production.min.js

react.production.min.js

245 ms

react-dom.production.min.js

react-dom.production.min.js

247 ms

d7ddb21d93259c470d76340a376a3ea1cd48381b-compiled-public-forms.js

d7ddb21d93259c470d76340a376a3ea1cd48381b-compiled-public-forms.js

236 ms

collect

collect

78 ms

ping

ping

56 ms

collect

collect

27 ms

collect

collect

27 ms

Accessibility Review

stlpublicradio.org accessibility score

92

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

Best Practices

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

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

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

stlpublicradio.org

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