2.2 sec in total
120 ms
1.3 sec
794 ms
Click here to check amazing RUSC content for United States. Otherwise, check out these important facts you probably never knew about rusc.com
Over 40,000 of the most popular (and the most obscure!) old time radio shows from the golden age of radio in the 1930s, 40s and 50s. Download as mp3 or stream online. Also featuring in-depth old time ...
Visit rusc.comWe analyzed Rusc.com page load time and found that the first response time was 120 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
rusc.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value6.8 s
7/100
25%
Value3.7 s
85/100
10%
Value550 ms
53/100
30%
Value0
100/100
15%
Value7.7 s
45/100
10%
120 ms
377 ms
70 ms
138 ms
210 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 29% of them (16 requests) were addressed to the original Rusc.com, 16% (9 requests) were made to I.po.st and 11% (6 requests) were made to Cdn2.rusc.com. The less responsive or slowest element that took the longest time to load (736 ms) relates to the external source Cdn2.rusc.com.
Page size can be reduced by 794.4 kB (55%)
1.4 MB
652.4 kB
In fact, the total size of Rusc.com main page is 1.4 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. 40% of websites need less resources to load. Javascripts take 956.9 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.9 kB or 72% of the original size.
Potential reduce by 1.9 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. RUSC images are well optimized though.
Potential reduce by 631.7 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 631.7 kB or 66% of the original size.
Potential reduce by 124.0 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. Rusc.com needs all CSS files to be minified and compressed as it can save up to 124.0 kB or 86% of the original size.
Number of requests can be reduced by 29 (59%)
49
20
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RUSC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rusc.com
120 ms
www.rusc.com
377 ms
gateway2.css
70 ms
Telerik.Web.UI.WebResource.axd
138 ms
Telerik.Web.UI.WebResource.axd
210 ms
Gateway.js
45 ms
post-widget.js
62 ms
radio-show_details_2_small.png
433 ms
arrow-small-right.gif
25 ms
join_RUSC_now.gif
30 ms
radio-series-description-small-3.png
736 ms
join_RUSC_now.gif
545 ms
ned_and_joy_sig.gif
558 ms
partial-list-of-old-time-radio-series.png
602 ms
rusc-member-comments.png
658 ms
analytics.js
8 ms
collect
16 ms
embed.html
136 ms
bg.jpg
91 ms
headerbg.png
41 ms
header.png
93 ms
leftmenuselected.gif
66 ms
leftmenu.gif
67 ms
bullet.gif
67 ms
footer.png
51 ms
centerfooter.png
50 ms
r1post.css
19 ms
post-native.png
15 ms
ra1-icoset.png
15 ms
set-16.png
16 ms
set-16.png
17 ms
status
13 ms
p
5 ms
p23
4 ms
pixel
21 ms
ucm
4 ms
ucm
2 ms
counter
7 ms
tap.php
6 ms
sd
30 ms
jquery-1.8.2.min.gz.js
69 ms
EmbedCanvas.gz.js
79 ms
ucm
10 ms
rmxucm
3 ms
ptn529pc4
66 ms
copyPaste.js
2 ms
beacon.js
16 ms
shareQuote.js
2 ms
share2quote.css
2 ms
countAccess.php
22 ms
45y46h03953844o23v3473ic36316t27.gz.js
11 ms
css
29 ms
scale-750x750
43 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
4 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
scale-750x750
78 ms
rusc.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
rusc.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
rusc.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rusc.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rusc.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.
rusc.com
Open Graph description is not detected on the main page of RUSC. 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: