Tools & Wizards About Us
wrti.org screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

wrti.org

Homepage | WRTI

Page Load Speed

2.4 sec in total

First Response

35 ms

Resources Loaded

1.7 sec

Page Rendered

688 ms

wrti.org screenshot

About Website

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

Over 300,000 listeners tune to WRTI each week on the radio, and an ever-growing number of people listen online via our two 24-hour web streams, on Internet radio, or on the WRTI Mobile App. The statio...

Visit wrti.org

Key Findings

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

wrti.org performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

wrti.org

35 ms

www.wrti.org

36 ms

www.wrti.org

35 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

33 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

68 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Wrti.org, 26% (24 requests) were made to Npr.brightspotcdn.com and 12% (11 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (659 ms) relates to the external source Vuhaus-assets-production.global.ssl.fastly.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 414.2 kB (21%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wrti.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. 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 171.1 kB

  • Original 205.4 kB
  • After minification 171.9 kB
  • After compression 34.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 33.5 kB, which is 16% 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 171.1 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 37.5 kB

  • Original 564.8 kB
  • After minification 527.3 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. WRTI images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 202.6 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 895.5 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 202.6 kB or 18% of the original size.

CSS Optimization

-4%

Potential reduce by 3.1 kB

  • Original 72.1 kB
  • After minification 72.1 kB
  • After compression 69.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. Wrti.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (48%)

Requests Now

80

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wrti.org

wrti.org

35 ms

www.wrti.org

www.wrti.org

36 ms

www.wrti.org

www.wrti.org

35 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

All.min.ab6eee59525552b9100e33650d638008.gz.css

33 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

68 ms

gpt.js

gpt.js

123 ms

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

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

23 ms

sdk.js

sdk.js

29 ms

gtm.js

gtm.js

175 ms

css

css

104 ms

f4c65a85-fb02-4033-a12c-053055e0cac0

f4c65a85-fb02-4033-a12c-053055e0cac0

166 ms

now.html

now.html

32 ms

now.html

now.html

34 ms

10 ms

13 ms

21 ms

22 ms

22 ms

22 ms

24 ms

24 ms

30 ms

32 ms

37 ms

31 ms

30 ms

29 ms

35 ms

33 ms

35 ms

sdk.js

sdk.js

19 ms

jquery.min.js

jquery.min.js

258 ms

whatson.js

whatson.js

30 ms

jquery-deparam.js

jquery-deparam.js

63 ms

330 ms

pubads_impl.js

pubads_impl.js

220 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

287 ms

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

156 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

387 ms

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

156 ms

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

233 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

550 ms

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

155 ms

gpt.js

gpt.js

405 ms

app.css

app.css

405 ms

app.d.js

app.d.js

659 ms

vendor.js

vendor.js

633 ms

embed.js

embed.js

509 ms

js

js

211 ms

js

js

313 ms

analytics.js

analytics.js

441 ms

gtm.js

gtm.js

395 ms

chartbeat.js

chartbeat.js

511 ms

v2.css

v2.css

89 ms

moment.isocalendar.js

moment.isocalendar.js

89 ms

moment.isocalendar.js

moment.isocalendar.js

130 ms

now

now

635 ms

now

now

590 ms

api.min.js

api.min.js

313 ms

collect

collect

260 ms

collect

collect

285 ms

collect

collect

254 ms

collect

collect

292 ms

collect

collect

250 ms

collect

collect

302 ms

ping

ping

244 ms

f4c65a85-fb02-4033-a12c-053055e0cac0

f4c65a85-fb02-4033-a12c-053055e0cac0

104 ms

jsapi

jsapi

62 ms

collect

collect

31 ms

collect

collect

39 ms

js

js

58 ms

ga-audiences

ga-audiences

337 ms

loader.js

loader.js

23 ms

loader.js

loader.js

128 ms

addthis_widget.js

addthis_widget.js

285 ms

npr-music-logo-42cd4c034ba60f8179ebc9029f64bccc.png

npr-music-logo-42cd4c034ba60f8179ebc9029f64bccc.png

104 ms

polyfills.intersection-observer.js

polyfills.intersection-observer.js

365 ms

googima.js

googima.js

397 ms

jwpsrv.js

jwpsrv.js

400 ms

gapro.js

gapro.js

402 ms

related.js

related.js

403 ms

share_video-91562e86ac8890d2aa8665821bd0c82e.svg

share_video-91562e86ac8890d2aa8665821bd0c82e.svg

95 ms

tooltip.css

tooltip.css

46 ms

util.css

util.css

50 ms

table.css

table.css

48 ms

format.css

format.css

50 ms

jsapi_compiled_default_module.js

jsapi_compiled_default_module.js

56 ms

jsapi_compiled_graphics_module.js

jsapi_compiled_graphics_module.js

51 ms

jsapi_compiled_ui_module.js

jsapi_compiled_ui_module.js

92 ms

jsapi_compiled_corechart_module.js

jsapi_compiled_corechart_module.js

52 ms

jsapi_compiled_table_module.js

jsapi_compiled_table_module.js

52 ms

jw-icons.woff

jw-icons.woff

6 ms

Accessibility Review

wrti.org accessibility score

95

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

Best Practices

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

wrti.org SEO score

99

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

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

wrti.org

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