1.6 sec in total
66 ms
798 ms
687 ms
Welcome to wesa.fm homepage info - get ready to check WESA best content for United States right away, or after learning these important things about wesa.fm
Breaking news and in-depth reporting by the journalists of WESA, the NPR news station in Pittsburgh, Pa.
Visit wesa.fmWe analyzed Wesa.fm page load time and found that the first response time was 66 ms and then it took 1.5 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.
wesa.fm performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value7.2 s
5/100
25%
Value6.1 s
44/100
10%
Value1,580 ms
12/100
30%
Value0
100/100
15%
Value13.5 s
11/100
10%
66 ms
14 ms
28 ms
37 ms
28 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 20% of them (9 requests) were addressed to the original Wesa.fm, 46% (21 requests) were made to Mediad.publicbroadcasting.net and 13% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (386 ms) relates to the external source Tpc.googlesyndication.com.
Page size can be reduced by 757.7 kB (36%)
2.1 MB
1.4 MB
In fact, the total size of Wesa.fm main page is 2.1 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 63.9 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 63.9 kB or 79% of the original size.
Potential reduce by 30.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. WESA images are well optimized though.
Potential reduce by 415.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 415.5 kB or 70% of the original size.
Potential reduce by 247.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. Wesa.fm needs all CSS files to be minified and compressed as it can save up to 247.7 kB or 86% of the original size.
Number of requests can be reduced by 18 (46%)
39
21
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WESA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
wesa.fm
66 ms
css_zXr1pRkjUmFHX10b6Pv5_DqzyewvdLNQ8QgccGQIRQQ.css
14 ms
css_XHTm2cMU6sD6pzlNwtS19lgDRK8GjAz14nQaxKhle30.css
28 ms
css_uY1_bHNTrAu2UuUwumZ6AuPc2Egu5fV5FiJ2-fv7ySk.css
37 ms
css
28 ms
css_AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs.css
23 ms
css_-DT6mi0tdbZWf4uHUVbhWLCBkXYpdrg5Vxw5UzeZt6U.css
70 ms
js_xSpMA4ArVcBKOZ43sPqNRk0gxQZdDVifw27pIUCzWU0.js
53 ms
js_exlly3cT5PMwSjSPuLbcphgU2TQwPVE1zybxhKB1IOQ.js
30 ms
js_-WcrGf3pH5GnSWA1Y-B28tyjknNjFr4asJklCZQ5NUA.js
32 ms
js_ZcZajqjC7KCS8_A2dOG5Y53mBT4KJLE7BiKX15HUv7g.js
42 ms
gpt.js
6 ms
js_V8xCDGAdrFLqDN8aQmQ5EX61xovZLOae1cnhlDlKYJI.js
45 ms
js_txrSF3Dd1fUAlTmSh9DFPoIBNEfX08MZKJopgUzq_OQ.js
30 ms
pubads_impl_81.js
5 ms
container.html
386 ms
aalz.js
382 ms
logo_fid.png
379 ms
playpause-sprite-r.png
367 ms
IMG_5368.JPG
215 ms
468256538.jpeg
212 ms
468568833.jpg
213 ms
9249914093_1c06ee3d9b_o.jpg
215 ms
penn_plaza_0.jpg
213 ms
15627562799_2350186d1a_o.jpg
213 ms
lead_l_tom.jpg
216 ms
2513782657_6608d84bea_o.jpg
217 ms
468282722.jpg
219 ms
468504029.jpg
216 ms
468256173.jpg
216 ms
newsletter_round.jpg
219 ms
social_club.jpg
220 ms
JazzWorkslogo.png
217 ms
ads
155 ms
feed
54 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
37 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
37 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
54 ms
4cKlrioa77J2iqTqBgkRWg.ttf
53 ms
responso.woff
36 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
54 ms
HkF_qI1x_noxlxhrhMQYEKCWcynf_cDxXwCLxiixG1c.ttf
53 ms
analytics.js
8 ms
jquery.min.js
89 ms
linkid.js
5 ms
ecommerce.js
22 ms
wesa.fm accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
wesa.fm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
wesa.fm SEO score
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 Wesa.fm 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 Wesa.fm 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.
wesa.fm
Open Graph description is not detected on the main page of WESA. 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: