951 ms in total
106 ms
626 ms
219 ms
Welcome to whyy.org homepage info - get ready to check WHYY best content for United States right away, or after learning these important things about whyy.org
WHYY is the leading public media organization in the Philadelphia Region, including Delaware, New Jersey, Pennsylvania and beyond. You can access us on television, radio, in the community and right he...
Visit whyy.orgWe analyzed Whyy.org page load time and found that the first response time was 106 ms and then it took 845 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
whyy.org performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value15.8 s
0/100
25%
Value7.8 s
24/100
10%
Value1,370 ms
16/100
30%
Value0
100/100
15%
Value16.3 s
5/100
10%
106 ms
95 ms
52 ms
50 ms
49 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 53% of them (38 requests) were addressed to the original Whyy.org, 13% (9 requests) were made to Google.com and 8% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (230 ms) relates to the external source S3.amazonaws.com.
Page size can be reduced by 656.6 kB (39%)
1.7 MB
1.0 MB
In fact, the total size of Whyy.org main page is 1.7 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. 55% of websites need less resources to load. Images take 807.9 kB which makes up the majority of the site volume.
Potential reduce by 30.6 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 8.5 kB, which is 22% 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 30.6 kB or 80% of the original size.
Potential reduce by 27.7 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. WHYY images are well optimized though.
Potential reduce by 454.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 454.5 kB or 70% of the original size.
Potential reduce by 143.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. Whyy.org needs all CSS files to be minified and compressed as it can save up to 143.7 kB or 85% of the original size.
Number of requests can be reduced by 36 (54%)
67
31
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WHYY. 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.
whyy.org
106 ms
bootstrap.css
95 ms
bootstrap-responsive.css
52 ms
flexslider.css
50 ms
mega-drop.css
49 ms
custom-home.css
52 ms
custom-general.css
100 ms
jquery-latest.min.js
6 ms
bootstrap.js
115 ms
jquery.flexslider-min.js
115 ms
custom-funcs.js
85 ms
google_service.js
17 ms
bootstrap-progressbar.js
82 ms
bootstrap-progressbar.css
70 ms
jsapi
19 ms
t13n
35 ms
brand
36 ms
urchin.js
62 ms
t13n
69 ms
brand
71 ms
google_ads.js
21 ms
aacj.js
21 ms
pagebg-home.jpg
98 ms
23 ms
m_nwelcitycommissionersx1200-1.jpg
122 ms
whyymock_logo.png
200 ms
logo-90x30.png
83 ms
whyy-fb.png
84 ms
whyy-twitter.png
84 ms
whyy-youtube.png
84 ms
whyy-soundcloud.png
83 ms
rtslide1_10.jpg
119 ms
rtslide1_11.jpg
116 ms
garden.jpg
119 ms
independentlens_wilheminaswar.jpg
121 ms
support_generic_300x180.jpg
118 ms
HA_HPI_2_WHYY_Passport.jpg
115 ms
arthur.jpg
168 ms
bowe.jpg
167 ms
voices_event.jpg
185 ms
upstairsdownstairs.jpg
185 ms
watchnow.jpg
177 ms
ticket.png
193 ms
wiltb_th.jpg
195 ms
matchgift.jpg
204 ms
pmc_camps.jpg
205 ms
bq9.js
230 ms
analytics.js
72 ms
jquery.min.js
71 ms
transliteration.css
3 ms
transliteration.I.js
9 ms
26 ms
ads
100 ms
nw_homemock_logo.png
144 ms
google_custom_search_watermark.gif
87 ms
linkid.js
29 ms
ecommerce.js
34 ms
inputtools.js
18 ms
m_nwelcitycommissionersx1200-1.jpg
62 ms
collect
39 ms
collect
94 ms
collect
47 ms
collect
104 ms
bowe.jpg
175 ms
top10.jpg
175 ms
11433178423119365905
42 ms
osd.js
19 ms
ads
55 ms
17668546629879779450
59 ms
__utm.gif
48 ms
mega-arrow.png
15 ms
chartbeat.js
22 ms
whyy.org 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-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
whyy.org 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
Page has valid source maps
whyy.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Whyy.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 Whyy.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.
whyy.org
Open Graph description is not detected on the main page of WHYY. 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: