Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

wqxr.com

WQXR | New York's Classical Music Radio Station

Page Load Speed

2.7 sec in total

First Response

86 ms

Resources Loaded

2.2 sec

Page Rendered

375 ms

wqxr.com screenshot

About Website

Visit wqxr.com now to see the best up-to-date WQXR content and also check out these interesting facts you probably never knew about wqxr.com

WQXR - New York Public Radio

Visit wqxr.com

Key Findings

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

wqxr.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value3,860 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.318

36/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

wqxr.com

86 ms

www.wqxr.org

16 ms

de2be10b8abc.css

19 ms

0e0f22a6e8c3.js

36 ms

f7b20a75eddc.js

35 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wqxr.com, 22% (40 requests) were made to Media.wnyc.org and 20% (37 requests) were made to Media2.wnyc.org. The less responsive or slowest element that took the longest time to load (374 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (63%)

Content Size

4.9 MB

After Optimization

1.8 MB

In fact, the total size of Wqxr.com main page is 4.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. 85% 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 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 9.4 kB

  • Original 13.4 kB
  • After minification 12.6 kB
  • After compression 4.0 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 9.4 kB or 70% of the original size.

Image Optimization

-33%

Potential reduce by 219.8 kB

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

JavaScript Optimization

-69%

Potential reduce by 2.1 MB

  • Original 3.1 MB
  • After minification 3.0 MB
  • After compression 942.3 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 2.1 MB or 69% of the original size.

CSS Optimization

-64%

Potential reduce by 715.1 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 403.7 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.com needs all CSS files to be minified and compressed as it can save up to 715.1 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 105 (59%)

Requests Now

177

After Optimization

72

The browser has sent 177 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 51 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

wqxr.com accessibility score

91

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

High

Image elements do not have [alt] attributes

Best Practices

wqxr.com 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.com SEO score

75

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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.com 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.com 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: