Tools & Wizards About Us
publicradiotulsa.org screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

publicradiotulsa.org

Public Radio Tulsa

Page Load Speed

1.5 sec in total

First Response

42 ms

Resources Loaded

712 ms

Page Rendered

699 ms

publicradiotulsa.org screenshot

About Website

Visit publicradiotulsa.org now to see the best up-to-date Public Radio Tulsa content for United States and also check out these interesting facts you probably never knew about publicradiotulsa.org

A listener-supported service of The University of Tulsa

Visit publicradiotulsa.org

Key Findings

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

Performance Metrics

publicradiotulsa.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

publicradiotulsa.org

42 ms

www.publicradiotulsa.org

11 ms

www.publicradiotulsa.org

26 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

43 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

90 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Publicradiotulsa.org, 66% (25 requests) were made to Npr.brightspotcdn.com and 8% (3 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (548 ms) relates to the external source Npr.brightspotcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.0 kB (19%)

Content Size

2.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Publicradiotulsa.org main page is 2.3 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 169.0 kB

  • Original 202.2 kB
  • After minification 169.1 kB
  • After compression 33.2 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.1 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 169.0 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 174.6 kB

  • Original 1.6 MB
  • After minification 1.4 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. Obviously, Public Radio Tulsa needs image optimization as it can save up to 174.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 74.3 kB

  • Original 372.4 kB
  • After minification 372.4 kB
  • After compression 298.1 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 74.3 kB or 20% of the original size.

CSS Optimization

-2%

Potential reduce by 1.1 kB

  • Original 66.1 kB
  • After minification 66.1 kB
  • After compression 65.0 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. Publicradiotulsa.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (21%)

Requests Now

28

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Radio Tulsa. 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 as a result speed up the page load time.

Network Requests Diagram

publicradiotulsa.org

publicradiotulsa.org

42 ms

www.publicradiotulsa.org

www.publicradiotulsa.org

11 ms

www.publicradiotulsa.org

www.publicradiotulsa.org

26 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

All.min.ab6eee59525552b9100e33650d638008.gz.css

43 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

90 ms

gpt.js

gpt.js

146 ms

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

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

86 ms

sdk.js

sdk.js

34 ms

gtm.js

gtm.js

222 ms

css

css

83 ms

15 ms

17 ms

17 ms

21 ms

21 ms

205 ms

27 ms

27 ms

312 ms

23 ms

24 ms

58 ms

58 ms

62 ms

548 ms

60 ms

444 ms

62 ms

sdk.js

sdk.js

10 ms

pubads_impl.js

pubads_impl.js

117 ms

ppub_config

ppub_config

242 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

237 ms

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

110 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

237 ms

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

109 ms

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

109 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

237 ms

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

235 ms

Accessibility Review

publicradiotulsa.org accessibility score

94

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

Links do not have a discernible name

Best Practices

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

publicradiotulsa.org SEO score

98

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

publicradiotulsa.org

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