4.7 sec in total
1.2 sec
2.8 sec
633 ms
Visit haze.fm now to see the best up-to-date Haze content and also check out these interesting facts you probably never knew about haze.fm
The best music on the Planet! Your radio 24/7 Free, just the way you like it. Hip hop, R&B brought to you explicit. Also gospel, Clean, and Latin channels. No subscription. Register Today.
Visit haze.fmWe analyzed Haze.fm page load time and found that the first response time was 1.2 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
haze.fm performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.2 s
24/100
25%
Value13.4 s
2/100
10%
Value690 ms
43/100
30%
Value0.06
98/100
15%
Value15.7 s
6/100
10%
1218 ms
86 ms
84 ms
124 ms
89 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 63% of them (89 requests) were addressed to the original Haze.fm, 8% (11 requests) were made to I2.wp.com and 7% (10 requests) were made to I1.wp.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Haze.fm.
Page size can be reduced by 1.1 MB (49%)
2.2 MB
1.1 MB
In fact, the total size of Haze.fm main page is 2.2 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. 65% of websites need less resources to load. Javascripts take 882.5 kB which makes up the majority of the site volume.
Potential reduce by 85.8 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 85.8 kB or 81% of the original size.
Potential reduce by 21.8 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. Haze images are well optimized though.
Potential reduce by 628.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 628.7 kB or 71% of the original size.
Potential reduce by 358.8 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. Haze.fm needs all CSS files to be minified and compressed as it can save up to 358.8 kB or 80% of the original size.
Number of requests can be reduced by 101 (75%)
134
33
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.haze.fm
1218 ms
wp-emoji-release.min.js
86 ms
styles.css
84 ms
template-dark.css
124 ms
icons.css
89 ms
fontello.css
88 ms
window.css
127 ms
lightbox.css
128 ms
swipebox.min.css
128 ms
style.css
129 ms
main-style.css
207 ms
style.css
167 ms
select2.css
171 ms
style.css
173 ms
qantumthemes-soundmanager2-styles.css
173 ms
jetpack.css
258 ms
default.css
221 ms
jquery.js
293 ms
jquery-migrate.min.js
222 ms
qantum-soundmanager2-library.js
263 ms
css
25 ms
css
38 ms
BidVertiser.dbm
163 ms
jquery.fileupload.css
45 ms
genericons.css
125 ms
core.min.js
46 ms
photon.js
48 ms
jquery.form.min.js
127 ms
scripts.js
143 ms
peepso.min.js
143 ms
underscore.min.js
140 ms
npm-expanded.min.js
142 ms
jquery.mousewheel.min.js
155 ms
widget.min.js
155 ms
jquery.iframe-transport.min.js
157 ms
jquery.fileupload.min.js
157 ms
chat-input.min.js
157 ms
observer.min.js
155 ms
chat-window.min.js
179 ms
chat-sidebar.min.js
180 ms
chat.min.js
193 ms
bootstrap.min.js
192 ms
time.min.js
193 ms
member.min.js
194 ms
autosize.min.js
244 ms
position.min.js
244 ms
notifications.min.js
245 ms
pswindow.min.js
245 ms
member-search.min.js
245 ms
activitystream.min.js
246 ms
image-scale.min.js
293 ms
lightbox.min.js
292 ms
modal-comments.min.js
291 ms
jquery.quicksand.js
291 ms
jquery.easing.1.3.js
290 ms
devicepx-jetpack.js
10 ms
gprofiles.js
112 ms
e-201611.js
8 ms
jquery-css-transform.js
283 ms
jquery-animate-css-rotate-scale.js
312 ms
jquery.swipebox.js
318 ms
vdl-main.js
288 ms
wpgroho.js
315 ms
ajax-loader.gif
42 ms
facebook.png
42 ms
delicious.png
41 ms
digg.png
43 ms
blinklist.png
45 ms
lifestream.png
41 ms
linkedin.png
42 ms
google.png
41 ms
1454302366370.jpeg
44 ms
wp-1450049078334.png
43 ms
wp-1450049091896.jpg
49 ms
Jam-feat.-Trey-Songz-Ty-Dolla-ign-and-Jamie-Foxx-Sing-956x956.jpg
48 ms
rihanna-anti-reveal-2015-billboard-650.jpg
48 ms
stumbleupon.png
48 ms
google_plus.png
45 ms
myspace.png
44 ms
twitter.png
44 ms
wp-1450049990488.gif
44 ms
wp-1450049086282.jpg
47 ms
1035x1035-image003.jpg
52 ms
say-it-600x600.jpg
53 ms
image.jpeg
53 ms
jquerycookie.js
244 ms
diigo.png
43 ms
blogmarks.png
50 ms
newsvine.png
46 ms
wp-1450049067390.png
50 ms
wp-1450055803679.png
47 ms
rihanna-work.jpg
49 ms
f80e7592-640x640.jpg
50 ms
WNBSGjK.jpg
51 ms
hazefmtravelcom.jpg
53 ms
theme-libraries.js
298 ms
qt-main.js
253 ms
peepsofriends.min.js
250 ms
dropdown.min.js
235 ms
peepsofriendsshortcode.min.js
235 ms
select2.min.js
347 ms
8XtYtNKEyyZh481XVWfVOqCWcynf_cDxXwCLxiixG1c.ttf
18 ms
h0STFiiHJJuefGZJAxrSiA.ttf
38 ms
peepsomessages.min.js
343 ms
sdk.js
69 ms
postbox.min.js
339 ms
peepsovideos.min.js
330 ms
jquery.autosize.min.js
338 ms
share.min.js
342 ms
posttabs.min.js
342 ms
script.js
342 ms
bdvinj.js
80 ms
wp-embed.min.js
319 ms
load-image.all.min.js
309 ms
peepsophotos.min.js
307 ms
mouse.min.js
321 ms
sortable.min.js
322 ms
360player-custom.js
347 ms
Material-Design-Icons.woff
477 ms
PeepSo.ttf
273 ms
image-1.jpeg
470 ms
volume.svg
469 ms
register-bg.jpg
615 ms
75 ms
app_android.png
462 ms
bidvertiser.dbm
235 ms
BidVertiser.dbm
234 ms
xd_arbiter.php
84 ms
xd_arbiter.php
203 ms
app_iphone.png
423 ms
app_winphone.png
423 ms
app_winamp.png
423 ms
app_mediaplayer.png
423 ms
Genericons.svg
435 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
28 ms
qticons.woff
424 ms
BidVertiser.dbm
239 ms
g.gif
9 ms
hovercard.css
45 ms
services.css
56 ms
BidVertiser.dbm
151 ms
haze.fm accessibility score
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
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
haze.fm 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
Page has valid source maps
haze.fm 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haze.fm 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 Haze.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.
haze.fm
Open Graph data is detected on the main page of Haze. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: