2.9 sec in total
182 ms
2 sec
741 ms
Visit waks.com now to see the best up-to-date Waks content and also check out these interesting facts you probably never knew about waks.com
Cleveland's #1 Hit Music Station
Visit waks.comWe analyzed Waks.com page load time and found that the first response time was 182 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
waks.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.3 s
68/100
25%
Value9.3 s
13/100
10%
Value5,890 ms
0/100
30%
Value0.094
91/100
15%
Value22.6 s
1/100
10%
182 ms
86 ms
49 ms
41 ms
39 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Waks.com, 19% (30 requests) were made to Flint-img.ccrd.clearchannel.com and 18% (29 requests) were made to Content.clearchannel.com. The less responsive or slowest element that took the longest time to load (419 ms) relates to the external source Facebook.com.
Page size can be reduced by 1.5 MB (55%)
2.6 MB
1.2 MB
In fact, the total size of Waks.com main page is 2.6 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.5 MB which makes up the majority of the site volume.
Potential reduce by 103.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 21.8 kB, which is 17% 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 103.6 kB or 80% of the original size.
Potential reduce by 43.6 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. Waks images are well optimized though.
Potential reduce by 1.1 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.1 MB or 72% of the original size.
Potential reduce by 237.6 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. Waks.com needs all CSS files to be minified and compressed as it can save up to 237.6 kB or 81% of the original size.
Number of requests can be reduced by 99 (62%)
159
60
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
waks.com
182 ms
www.kisscleveland.com
86 ms
core.css
49 ms
app.css
41 ms
ihearticons.css
39 ms
station_styles.css
126 ms
custom.modernizr.js
40 ms
jquery.js
71 ms
jquery.cookie.js
39 ms
sdk.min.js
39 ms
ads.min.js
58 ms
plusone.js
105 ms
slider.min.js
59 ms
timeline.min.js
58 ms
LAB.min.js
58 ms
main.min.js
58 ms
foundation.js
59 ms
foundation.orbit.js
58 ms
foundation.forms.js
59 ms
foundation.section.js
59 ms
foundation.reveal.js
60 ms
init.js
59 ms
challenge
56 ms
gpt.js
153 ms
analytics.js
153 ms
cb=gapi.loaded_0
144 ms
sdk.js
145 ms
thumbNew.php
147 ms
widgets.js
142 ms
cb=gapi.loaded_1
140 ms
fastbutton
149 ms
search_btn_icon_black.png
130 ms
default
146 ms
spark-mobile-play-button-sprite-v2.png
90 ms
spark-mobile-iheartradio-logo.png
91 ms
localinfo_weather_icons.png
91 ms
localinfo_traffic_icon.png
93 ms
module-title-corner.png
93 ms
kissfm_grey_0_1442999287.png
92 ms
thumbCrop.php
120 ms
thumbCrop.php
95 ms
thumbCrop.php
121 ms
thumbCrop.php
96 ms
thumbCrop.php
94 ms
thumbCrop.php
99 ms
thumbCrop.php
226 ms
thumbNew.php
97 ms
thumbCrop.php
95 ms
thumbCrop.php
99 ms
thumbCrop.php
98 ms
thumbNew.php
102 ms
thumbCrop.php
99 ms
thumbCrop.php
102 ms
thumbCrop.php
100 ms
thumbCrop.php
107 ms
thumbCrop.php
103 ms
thumbCrop.php
106 ms
thumbCrop.php
106 ms
thumbCrop.php
108 ms
thumbCrop.php
108 ms
thumbCrop.php
106 ms
thumbCrop.php
109 ms
thumbCrop.php
112 ms
thumbNew.php
112 ms
cb=gapi.loaded_0
149 ms
cb=gapi.loaded_1
151 ms
p2
141 ms
pubads_impl_82.js
113 ms
postmessageRelay
115 ms
embed.html
290 ms
419 ms
ads
376 ms
container.html
41 ms
xd_arbiter.php
61 ms
xd_arbiter.php
349 ms
ti.js
219 ms
3193398744-postmessagerelay.js
350 ms
rpc:shindig_random.js
215 ms
e2eDetect.js
35 ms
s_code.js
185 ms
HTMLPoll.js
44 ms
328 ms
siteconfig.js
253 ms
recaptcha.js
31 ms
g6qlE9hbcrtCq0agucy03kPIdFYel5UicYHotHMXHKo.js
146 ms
timeline_more.html
356 ms
module-title-corner.png
94 ms
cc.js
245 ms
widget.now-playing.min.js
189 ms
widget.shoutout.min.js
200 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
206 ms
dynamic-lead-nav-sprite-black.png
90 ms
DARTfooterNewSplit.js
100 ms
DFPheader.js
165 ms
json2.js
171 ms
jquery.min.js
304 ms
jquery.cookie.js
174 ms
HTMLPlayer.js
198 ms
FlashPlayer.js
170 ms
EmbedPlayer.js
173 ms
SharePanelManager.js
195 ms
LayoutManager.js
194 ms
MediaManager.js
194 ms
PreRollManager.js
199 ms
GlobalDataObj.js
199 ms
TrackingObject.js
241 ms
WidgetModeView.js
241 ms
ima3.js
242 ms
PollsController.js
85 ms
refresh.png
122 ms
p
150 ms
bOa0NM1Her35hWadbi-bnq.js
114 ms
audio.png
87 ms
text.png
84 ms
help.png
90 ms
logo.png
90 ms
quickio.js
82 ms
ads
91 ms
bridge.min.js
76 ms
like.php
246 ms
widget.shoutout.css
40 ms
cb=gapi.loaded_0
54 ms
reload
94 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
44 ms
ads
189 ms
v2
173 ms
s_code-secure.js
151 ms
qeKvIRsJabD.js
197 ms
LVx-xkvaJ0b.png
151 ms
image
126 ms
beacon.js
212 ms
swfobject.js
100 ms
ads
108 ms
dpx
104 ms
s65180205623619
73 ms
18988132
83 ms
10181441340755661117
156 ms
moatad.js
215 ms
ads
83 ms
jot
170 ms
osd.js
106 ms
48 ms
ca.png
213 ms
12413733
48 ms
18632000
55 ms
31477952
56 ms
ads
53 ms
14227313524929814129
49 ms
xrefid.xgi
12 ms
pixel.gif
46 ms
pixel.gif
18 ms
nr-885.min.js
18 ms
pixel.gif
12 ms
25b61230c4
52 ms
rt=ifr
15 ms
pixel
16 ms
tpc=na_id
16 ms
5907
32 ms
g.json
58 ms
6 ms
7 ms
362738.gif
12 ms
waks.com accessibility score
waks.com 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
Page has valid source maps
waks.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 Waks.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 Waks.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.
waks.com
Open Graph data is detected on the main page of Waks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: