6 sec in total
167 ms
5.3 sec
482 ms
Visit b101.com now to see the best up-to-date B101 content for United States and also check out these interesting facts you probably never knew about b101.com
Don't miss out on the latest from B101, The 80's and More - Providence
Visit b101.comWe analyzed B101.com page load time and found that the first response time was 167 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
b101.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.3 s
68/100
25%
Value6.9 s
33/100
10%
Value4,340 ms
1/100
30%
Value0.094
91/100
15%
Value21.2 s
1/100
10%
167 ms
4030 ms
34 ms
42 ms
30 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original B101.com, 20% (33 requests) were made to Content.clearchannel.com and 18% (30 requests) were made to Flint-img.ccrd.clearchannel.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source B101.iheart.com.
Page size can be reduced by 1.5 MB (48%)
3.1 MB
1.6 MB
In fact, the total size of B101.com main page is 3.1 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.4 MB which makes up the majority of the site volume.
Potential reduce by 103.1 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.4 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.1 kB or 80% of the original size.
Potential reduce by 110.0 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. B101 images are well optimized though.
Potential reduce by 1.0 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.0 MB or 71% 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. B101.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 95 (59%)
162
67
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of B101. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 69 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
b101.com
167 ms
b101.iheart.com
4030 ms
core.css
34 ms
app.css
42 ms
ihearticons.css
30 ms
station_styles.css
126 ms
custom.modernizr.js
43 ms
jquery.js
53 ms
jquery.cookie.js
26 ms
sdk.min.js
45 ms
ads.min.js
40 ms
plusone.js
73 ms
slider.min.js
39 ms
timeline.min.js
39 ms
LAB.min.js
38 ms
main.min.js
38 ms
foundation.js
40 ms
foundation.orbit.js
40 ms
foundation.forms.js
39 ms
foundation.section.js
38 ms
foundation.reveal.js
37 ms
init.js
37 ms
challenge
43 ms
gpt.js
21 ms
analytics.js
22 ms
cb=gapi.loaded_0
18 ms
blogo_drop_0_1404388071.png
108 ms
default
50 ms
boston40.200.jpg
339 ms
wicked_deals_0_1453997220.jpg
16 ms
journeydoob.200.jpg
236 ms
duranduran200.jpg
350 ms
thumbCrop.php
105 ms
thumbCrop.php
108 ms
thumbCrop.php
45 ms
thumbCrop.php
106 ms
thumbCrop.php
47 ms
thumbCrop.php
109 ms
thumbNew.php
48 ms
thumbCrop.php
108 ms
thumbCrop.php
149 ms
thumbCrop.php
150 ms
thumbCrop.php
105 ms
thumbCrop.php
107 ms
thumbCrop.php
105 ms
thumbCrop.php
172 ms
thumbCrop.php
108 ms
thumbCrop.php
129 ms
thumbCrop.php
144 ms
thumbCrop.php
109 ms
thumbCrop.php
129 ms
thumbCrop.php
129 ms
thumbCrop.php
139 ms
thumbCrop.php
139 ms
thumbNew.php
143 ms
thumbCrop.php
141 ms
thumbCrop.php
144 ms
thumbCrop.php
142 ms
thumbCrop.php
143 ms
thumbNew.php
144 ms
2016_1370877199.jpg
203 ms
sdk.js
36 ms
thumbNew.php
198 ms
p2
32 ms
widgets.js
26 ms
pubads_impl_82.js
27 ms
collect
19 ms
collect
61 ms
fastbutton
88 ms
search_btn_icon_black.png
48 ms
container.html
43 ms
spark-mobile-play-button-sprite-v2.png
38 ms
spark-mobile-iheartradio-logo.png
45 ms
ads
120 ms
264 ms
cb=gapi.loaded_0
72 ms
cb=gapi.loaded_1
95 ms
localinfo_weather_icons.png
57 ms
xd_arbiter.php
71 ms
xd_arbiter.php
83 ms
localinfo_traffic_icon.png
43 ms
module-title-corner.png
43 ms
ti.js
31 ms
e2eDetect.js
16 ms
HTMLPoll.js
120 ms
118 ms
siteconfig.js
151 ms
recaptcha.js
21 ms
s_code.js
111 ms
ads
85 ms
E_AyvNF_72kF0OHIQSu2zz--uMLR4xMnEqQo4xsSgbQ.js
90 ms
timeline_more.html
280 ms
module-title-corner.png
64 ms
cc.js
126 ms
widget.now-playing.min.js
106 ms
widget.shoutout.min.js
106 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
66 ms
dynamic-lead-nav-sprite-black.png
39 ms
p
75 ms
bOa0NM1Her35hWadbi-bnq.js
52 ms
ads
71 ms
bridge.min.js
25 ms
embed.html
50 ms
PollsController.js
33 ms
refresh.png
15 ms
audio.png
17 ms
text.png
16 ms
help.png
22 ms
logo.png
21 ms
quickio.js
78 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
23 ms
DARTfooterNewSplit.js
52 ms
DFPheader.js
61 ms
json2.js
82 ms
jquery.min.js
186 ms
jquery.cookie.js
80 ms
HTMLPlayer.js
95 ms
FlashPlayer.js
116 ms
EmbedPlayer.js
93 ms
SharePanelManager.js
115 ms
LayoutManager.js
130 ms
MediaManager.js
131 ms
PreRollManager.js
149 ms
GlobalDataObj.js
149 ms
TrackingObject.js
162 ms
WidgetModeView.js
161 ms
ima3.js
229 ms
widget.shoutout.css
61 ms
like.php
185 ms
8911980606537238226
247 ms
moatad.js
176 ms
ads
82 ms
v2
108 ms
osd.js
96 ms
reload
90 ms
1010986
48 ms
ads
106 ms
14234098788155650513
81 ms
image
53 ms
jot
170 ms
dpx
66 ms
102 ms
s33720908879768
33 ms
s_code-secure.js
85 ms
qeKvIRsJabD.js
121 ms
LVx-xkvaJ0b.png
109 ms
pixel.gif
101 ms
beacon.js
92 ms
swfobject.js
56 ms
1020880
35 ms
1023310
46 ms
1034045
46 ms
ca.png
180 ms
pixel.gif
7 ms
xrefid.xgi
5 ms
nr-885.min.js
16 ms
25b61230c4
73 ms
rt=ifr
13 ms
pixel
20 ms
tpc=na_id
17 ms
5907
29 ms
g.json
48 ms
7 ms
4 ms
362738.gif
8 ms
b101.com accessibility score
b101.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
b101.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 B101.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 B101.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.
b101.com
Open Graph data is detected on the main page of B101. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: