2.7 sec in total
140 ms
1.8 sec
774 ms
Visit wsrw.com now to see the best up-to-date WSRW content and also check out these interesting facts you probably never knew about wsrw.com
Hillsboro's Classic Hits!
Visit wsrw.comWe analyzed Wsrw.com page load time and found that the first response time was 140 ms and then it took 2.5 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. This domain responded with an error, which can significantly jeopardize Wsrw.com rating and web reputation
wsrw.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.3 s
68/100
25%
Value11.9 s
4/100
10%
Value5,830 ms
0/100
30%
Value0.094
91/100
15%
Value29.1 s
0/100
10%
140 ms
299 ms
44 ms
39 ms
36 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wsrw.com, 24% (36 requests) were made to Content.clearchannel.com and 18% (27 requests) were made to Flint-img.ccrd.clearchannel.com. The less responsive or slowest element that took the longest time to load (378 ms) relates to the external source Wsrw.iheart.com.
Page size can be reduced by 1.5 MB (52%)
2.9 MB
1.4 MB
In fact, the total size of Wsrw.com main page is 2.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. 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 94.4 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 22.9 kB, which is 20% 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 94.4 kB or 81% of the original size.
Potential reduce by 42.2 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. WSRW images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 71% of the original size.
Potential reduce by 236.2 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. Wsrw.com needs all CSS files to be minified and compressed as it can save up to 236.2 kB or 81% of the original size.
Number of requests can be reduced by 89 (61%)
146
57
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WSRW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 70 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
wsrw.com
140 ms
wsrw.iheart.com
299 ms
core.css
44 ms
app.css
39 ms
ihearticons.css
36 ms
station_styles.css
135 ms
custom.modernizr.js
34 ms
jquery.js
57 ms
jquery.cookie.js
33 ms
sdk.min.js
42 ms
ads.min.js
41 ms
plusone.js
65 ms
slider.min.js
34 ms
timeline.min.js
51 ms
LAB.min.js
50 ms
cr.js
325 ms
main.min.js
50 ms
foundation.js
50 ms
foundation.orbit.js
50 ms
foundation.forms.js
51 ms
foundation.section.js
50 ms
foundation.reveal.js
50 ms
init.js
51 ms
challenge
54 ms
gpt.js
164 ms
analytics.js
163 ms
cb=gapi.loaded_0
155 ms
thumbNew.php
159 ms
cb=gapi.loaded_1
150 ms
fastbutton
172 ms
search_btn_icon_black.png
138 ms
default
139 ms
spark-mobile-play-button-sprite-v2.png
81 ms
localinfo_weather_icons.png
82 ms
localinfo_traffic_icon.png
83 ms
module-title-corner.png
82 ms
wsrw_0_1439575934.png
106 ms
thumbCrop.php
172 ms
thumbCrop.php
83 ms
thumbCrop.php
107 ms
thumbCrop.php
84 ms
thumbCrop.php
85 ms
thumbNew.php
85 ms
thumbCrop.php
85 ms
thumbCrop.php
119 ms
thumbCrop.php
117 ms
thumbCrop.php
85 ms
thumbCrop.php
86 ms
thumbCrop.php
86 ms
thumbCrop.php
101 ms
thumbCrop.php
112 ms
thumbCrop.php
102 ms
thumbCrop.php
104 ms
thumbCrop.php
104 ms
thumbCrop.php
104 ms
thumbCrop.php
105 ms
thumbCrop.php
106 ms
thumbCrop.php
106 ms
thumbCrop.php
107 ms
thumbCrop.php
109 ms
thumbCrop.php
110 ms
thumbNew.php
110 ms
thumbCrop.php
168 ms
thumbCrop.php
110 ms
thumbCrop.php
165 ms
thumbCrop.php
110 ms
thumbCrop.php
165 ms
thumbCrop.php
166 ms
thumbCrop.php
170 ms
p2
90 ms
cb=gapi.loaded_0
80 ms
cb=gapi.loaded_1
82 ms
pubads_impl_82.js
61 ms
collect
48 ms
postmessageRelay
107 ms
embed.html
234 ms
ads
223 ms
container.html
39 ms
ti.js
162 ms
3193398744-postmessagerelay.js
188 ms
rpc:shindig_random.js
184 ms
e2eDetect.js
147 ms
s_code.js
308 ms
HTMLPoll.js
144 ms
246 ms
siteconfig.js
234 ms
recaptcha.js
19 ms
WRc9c.js
162 ms
DARTfooterNewSplit.js
148 ms
DFPheader.js
213 ms
json2.js
238 ms
jquery.min.js
239 ms
jquery.cookie.js
233 ms
HTMLPlayer.js
237 ms
FlashPlayer.js
219 ms
EmbedPlayer.js
235 ms
SharePanelManager.js
236 ms
LayoutManager.js
235 ms
MediaManager.js
270 ms
PreRollManager.js
270 ms
GlobalDataObj.js
256 ms
TrackingObject.js
270 ms
WidgetModeView.js
262 ms
ima3.js
302 ms
g6qlE9hbcrtCq0agucy03kPIdFYel5UicYHotHMXHKo.js
139 ms
timeline_more.html
378 ms
cc.js
178 ms
widget.now-playing.min.js
230 ms
widget.shoutout.min.js
229 ms
module-title-corner.png
108 ms
dynamic-lead-nav-sprite-black.png
40 ms
PollsController.js
34 ms
p
191 ms
bOa0NM1Her35hWadbi-bnq.js
99 ms
ads
120 ms
cb=gapi.loaded_0
66 ms
refresh.png
56 ms
audio.png
26 ms
text.png
39 ms
help.png
38 ms
logo.png
37 ms
bridge.min.js
40 ms
s_code-secure.js
55 ms
ads
54 ms
ads
48 ms
reload
42 ms
v2
64 ms
beacon.js
54 ms
swfobject.js
27 ms
6578230373492504093
149 ms
moatad.js
153 ms
ads
109 ms
osd.js
41 ms
image
49 ms
dpx
89 ms
ads
75 ms
2335131530282825464
16 ms
s85704997912980
54 ms
xrefid.xgi
5 ms
52154.gif
8 ms
nr-885.min.js
17 ms
rt=ifr
21 ms
25b61230c4
45 ms
g.json
49 ms
5907
88 ms
pixel
17 ms
tpc=na_id
15 ms
8 ms
5 ms
362738.gif
11 ms
wsrw.com accessibility score
wsrw.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
wsrw.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wsrw.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 Wsrw.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.
wsrw.com
Open Graph data is detected on the main page of WSRW. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: