Tools & Wizards About Us
wnpr.org screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% 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

  • 91

    SEO

    Google-friendlier than
    70% of websites

wnpr.org

Connecticut Public | Media for the curious | Connecticut Public

Page Load Speed

1.8 sec in total

First Response

64 ms

Resources Loaded

859 ms

Page Rendered

898 ms

wnpr.org screenshot

About Website

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

WNPR radio & WNPR News online are Connecticut's public-media source for NPR, local news/talk programs and news, arts, health, politics, education, and business

Visit wnpr.org

Key Findings

We analyzed Wnpr.org page load time and found that the first response time was 64 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

wnpr.org performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.33

34/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

wnpr.org

64 ms

wnpr.org

42 ms

www.ctpublic.org

59 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

47 ms

css2

68 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Wnpr.org, 65% (51 requests) were made to Npr.brightspotcdn.com and 15% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (384 ms) relates to the external source Npr.brightspotcdn.com.

Page Optimization Overview & Recommendations

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

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 346.3 kB

  • Original 398.6 kB
  • After minification 321.3 kB
  • After compression 52.3 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 77.4 kB, which is 19% 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 346.3 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 1.2 MB
  • After minification 1.2 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. Wnpr images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 218 B

  • Original 300.7 kB
  • After minification 300.7 kB
  • After compression 300.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 1.9 kB

  • Original 70.1 kB
  • After minification 70.1 kB
  • After compression 68.2 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. Wnpr.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (20%)

Requests Now

60

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wnpr. 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 from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wnpr.org

wnpr.org

64 ms

wnpr.org

wnpr.org

42 ms

www.ctpublic.org

www.ctpublic.org

59 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

All.min.ab6eee59525552b9100e33650d638008.gz.css

47 ms

css2

css2

68 ms

2023.css

2023.css

87 ms

global.css

global.css

95 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

65 ms

gpt.js

gpt.js

204 ms

postscribe.min.js

postscribe.min.js

66 ms

0479.js

0479.js

67 ms

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

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

60 ms

gtm.js

gtm.js

108 ms

sdk.js

sdk.js

105 ms

css

css

24 ms

19 ms

59 ms

128 ms

127 ms

127 ms

134 ms

128 ms

133 ms

133 ms

132 ms

132 ms

132 ms

158 ms

290 ms

290 ms

155 ms

157 ms

155 ms

292 ms

292 ms

304 ms

305 ms

305 ms

304 ms

304 ms

303 ms

381 ms

381 ms

338 ms

382 ms

381 ms

381 ms

380 ms

383 ms

382 ms

383 ms

384 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

302 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

302 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

301 ms

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

381 ms

pubads_impl.js

pubads_impl.js

121 ms

ppub_config

ppub_config

259 ms

sdk.js

sdk.js

101 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

215 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

214 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

180 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

260 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

260 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

258 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

260 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

258 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

257 ms

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

264 ms

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

264 ms

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

261 ms

259 ms

258 ms

257 ms

259 ms

258 ms

259 ms

259 ms

335 ms

Accessibility Review

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

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

wnpr.org SEO score

91

Search Engine Optimization Advices

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

wnpr.org

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