Tools & Wizards About Us

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

wqxr.org

WQXR | New York's Classical Music Radio Station

Page Load Speed

3 sec in total

First Response

10 ms

Resources Loaded

2.6 sec

Page Rendered

441 ms

About Website

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

WQXR - New York Public Radio

Visit wqxr.org

Key Findings

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

wqxr.org performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value4,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.168

71/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

wqxr.org

10 ms

www.wqxr.org

28 ms

gpt.js

559 ms

font-awesome.min.css

10 ms

vendor-886c600b1a77af73b51eb09472b23e91.css

77 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Wqxr.org, 19% (18 requests) were made to Api.wnyc.org and 12% (11 requests) were made to Media.wnyc.org. The less responsive or slowest element that took the longest time to load (952 ms) relates to the external source T.co.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wqxr.org main page is 2.5 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. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 198.8 kB

  • Original 281.5 kB
  • After minification 272.8 kB
  • After compression 82.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 198.8 kB or 71% of the original size.

Image Optimization

-19%

Potential reduce by 273.4 kB

  • Original 1.5 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. Obviously, WQXR needs image optimization as it can save up to 273.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

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

CSS Optimization

-1%

Potential reduce by 108 B

  • Original 7.9 kB
  • After minification 7.9 kB
  • After compression 7.8 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. Wqxr.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (51%)

Requests Now

71

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

wqxr.org accessibility score

98

Accessibility Issues

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

wqxr.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wqxr.org SEO score

82

Search Engine Optimization Advices

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

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