2.7 sec in total
30 ms
2.1 sec
498 ms
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.comWe analyzed Wqxr.com page load time and found that the first response time was 30 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wqxr.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value21.0 s
0/100
25%
Value12.9 s
2/100
10%
Value4,610 ms
0/100
30%
Value0.183
66/100
15%
Value27.8 s
0/100
10%
30 ms
75 ms
448 ms
5 ms
44 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wqxr.com, 19% (18 requests) were made to Api.wnyc.org and 17% (16 requests) were made to Media.wnyc.org. The less responsive or slowest element that took the longest time to load (707 ms) relates to the external source Analytics.twitter.com.
Page size can be reduced by 215.1 kB (12%)
1.8 MB
1.6 MB
In fact, the total size of Wqxr.com main page is 1.8 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. Javascripts take 752.9 kB which makes up the majority of the site volume.
Potential reduce by 212.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. 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 212.3 kB or 72% of the original size.
Potential reduce by 783 B
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. WQXR images are well optimized though.
Potential reduce by 1.9 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.
Potential reduce by 108 B
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 has all CSS files already compressed.
Number of requests can be reduced by 34 (47%)
73
39
The browser has sent 73 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 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
wqxr.com
30 ms
www.wqxr.org
75 ms
gpt.js
448 ms
font-awesome.min.css
5 ms
vendor-886c600b1a77af73b51eb09472b23e91.css
44 ms
wqxr-web-client-8f9228c85653c7abe153d7202eecdc26.css
57 ms
jsapi
43 ms
js
90 ms
pym.v1.min.js
49 ms
vendor-0163ed2acd4c587274905c2c66bd757a.js
75 ms
wqxr-web-client-24b53469252b2e3a1c745d035367ed8d.js
51 ms
loader.js
35 ms
css
44 ms
transparent-144db5c84d6446307d763fffc0ca7bf1.png
322 ms
wqxr_image.png
419 ms
Beethoven_Final_sm-54026ce06a43d59f490466470d09eb90.png
509 ms
471 ms
THE_HOURS_11_17_22_6337.jpg
209 ms
011724_full.jpg
185 ms
openears-s2-episode15-marthalanefox-square.jp
280 ms
220501_WQXR_BCM_.jpg
279 ms
Pictures_at_an_Exhibition_full_piano_fma_scale.jpg.jpg
211 ms
4_3_1600x1200.jpg
275 ms
slp.png
337 ms
CREDIT_Astrid_Ackermann.jpg
277 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
277 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
416 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
434 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
466 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
466 ms
S6uyw4BMUTPHjx4wWw.ttf
466 ms
fontawesome-webfont.woff
189 ms
hotjar-467005.js
275 ms
analytics.js
259 ms
gtm.js
262 ms
sdk.js
190 ms
223 ms
227 ms
356 ms
220 ms
340 ms
pubads_impl.js
81 ms
sdk.js
78 ms
gtm.js
160 ms
css
142 ms
main.0bf7f1cc.css
141 ms
main.240a321e.js
410 ms
modules.404c8789d11e259a4872.js
505 ms
js
215 ms
js
166 ms
destination
362 ms
fbevents.js
102 ms
uwt.js
439 ms
api.min.js
441 ms
273 ms
272 ms
274 ms
270 ms
309 ms
308 ms
307 ms
305 ms
306 ms
303 ms
346 ms
357060381479544
219 ms
collect
134 ms
activityi;src=6523833;type=count0;cat=pagev00;ord=2672183300531;npa=0;auiddc=136175442.1716044780;pscdl=noapi;frm=0;gtm=45fe45f0z876343915za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.wqxr.org%2F
560 ms
activityi;src=6523833;type=count0;cat=sitev00;ord=1;num=5423318492016;npa=0;auiddc=136175442.1716044780;pscdl=noapi;frm=0;gtm=45fe45f0z876343915za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.wqxr.org%2F
702 ms
collect
70 ms
adsct
671 ms
adsct
707 ms
466 ms
454 ms
wqxr_image.png
126 ms
collect
94 ms
collect
90 ms
THE_HOURS_11_17_22_6337.jpg
186 ms
openears-s2-episode15-marthalanefox-square.jp
132 ms
Pictures_at_an_Exhibition_full_piano_fma_scale.jpg.jpg
189 ms
4_3_1600x1200.jpg
188 ms
slp.png
185 ms
ads
153 ms
container.html
179 ms
151 ms
src=6523833;type=count0;cat=pagev00;ord=2672183300531;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe45f0z876343915za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.wqxr.org%2F
172 ms
collect
135 ms
viewed
134 ms
collect
129 ms
image-loading-a1caa9644945c61ca48d07ccf18a72aa.gif
75 ms
WQXR_Headshots_JukeBox_PaulCavalconte.jpg
64 ms
ufs_web_display.js
99 ms
css
43 ms
main.0bf7f1cc.css
28 ms
ga-audiences
87 ms
src=6523833;type=count0;cat=sitev00;ord=1;num=5423318492016;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe45f0z876343915za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.wqxr.org%2F
85 ms
wqxr.com accessibility score
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
<frame> or <iframe> elements do not have a title
wqxr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wqxr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
wqxr.com
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: