8.1 sec in total
670 ms
6.8 sec
581 ms
Visit block.fm now to see the best up-to-date Block content for Japan and also check out these interesting facts you probably never knew about block.fm
ダンスミュージック、ヒップホップ、R&B、ポップミュージックなど国内外の音楽情報を中心に、最新のユースカルチャーをラジオと記事で毎日配信。
Visit block.fmWe analyzed Block.fm page load time and found that the first response time was 670 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
block.fm performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value18.0 s
0/100
25%
Value10.1 s
9/100
10%
Value3,080 ms
2/100
30%
Value0.707
7/100
15%
Value17.6 s
4/100
10%
670 ms
519 ms
371 ms
366 ms
588 ms
Our browser made a total of 181 requests to load all elements on the main page. We found that 55% of them (100 requests) were addressed to the original Block.fm, 15% (27 requests) were made to Resource.blockfm.com and 6% (11 requests) were made to Api.block.fm. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Block.fm.
Page size can be reduced by 1.1 MB (25%)
4.3 MB
3.2 MB
In fact, the total size of Block.fm main page is 4.3 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. 85% 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. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 40.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. 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 40.1 kB or 78% of the original size.
Potential reduce by 148.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. Block images are well optimized though.
Potential reduce by 704.8 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 704.8 kB or 76% of the original size.
Potential reduce by 182.4 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. Block.fm needs all CSS files to be minified and compressed as it can save up to 182.4 kB or 85% of the original size.
Number of requests can be reduced by 103 (60%)
171
68
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Block. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
block.fm
670 ms
common.css
519 ms
module.css
371 ms
header_app.css
366 ms
style.css
588 ms
reset.css
397 ms
footer.css
399 ms
css
28 ms
sp_common.css
548 ms
sp_module.css
555 ms
sp_style.css
591 ms
sp_footer.css
598 ms
sp_form.css
687 ms
jquery.min.js
70 ms
environ.js
728 ms
first_action.js
739 ms
plusone.js
78 ms
sdk.js
58 ms
iframe_api
77 ms
modernizr.custom.js
599 ms
jquery.nicescroll.custom.js
996 ms
jquery.easing.1.3.js
603 ms
jquery.mousewheel.js
679 ms
kk.1.min.js
728 ms
renew_experimental.js
745 ms
jwplayer.js
1185 ms
md5.js
800 ms
pageinfoloader.js
868 ms
header_app.js
1094 ms
timetable.js
930 ms
backnumber_playlist.js
993 ms
sbm.js
1038 ms
common.js
1303 ms
feed_html.js
1189 ms
common.css
1006 ms
image.css
1030 ms
link.css
1094 ms
list.css
1194 ms
mltext.css
1199 ms
sltext.css
1202 ms
table.css
1199 ms
subcategory.css
1275 ms
sp_common.css
1124 ms
sp_image.css
1202 ms
sp_link.css
1205 ms
sp_list.css
1184 ms
sp_mltext.css
1209 ms
sp_sltext.css
1270 ms
sp_table.css
1308 ms
sp_subcategory.css
1323 ms
dc.js
879 ms
sp_logo.png
1635 ms
icon_menu_off.png
1634 ms
icon_menu_on.png
1636 ms
icon_start_playing.png
1633 ms
f5550711cd4b4c.jpg
1702 ms
sp_genre_menu_off.png
1634 ms
sp_genre_menu_on.png
1700 ms
logo_f.png
1702 ms
icon_burn.png
1700 ms
icon_pioneer_dj.png
1702 ms
icon_wasabeat.png
1700 ms
icon_mixlr.png
1966 ms
icon_iflyer.png
1986 ms
icon_mtv81.png
1965 ms
icon_moneytree.png
2197 ms
icon_acoustic-revive.jpg
1984 ms
logo_xbs.png
1985 ms
sp_footer_logo.png
2003 ms
all.js
1630 ms
all.js
1806 ms
search_area.png
2020 ms
icon_start_playing_disabled.png
2155 ms
icon_volume.png
2153 ms
icon_menu.png
2154 ms
play_item_type.png
2162 ms
icon_arrow_l_off.png
2195 ms
icon_arrow_r_off.png
2347 ms
player_bg_cover.png
2350 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
862 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
1608 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
1617 ms
4cKlrioa77J2iqTqBgkRWg.ttf
1617 ms
cb=gapi.loaded_0
851 ms
www-widgetapi.js
1783 ms
widgets.js
949 ms
plusone.js
841 ms
cb=gapi.loaded_1
945 ms
fastbutton
980 ms
icon_start_playing_disabled.svgz
1493 ms
icon_volume.svgz
1473 ms
icon_menu.svgz
1506 ms
play_item_type.svgz
1523 ms
icon_arrow_l_off.svgz
1645 ms
icon_arrow_r_off.svgz
1687 ms
logo.svgz
1683 ms
cat_on.png
1682 ms
blockfm_banner_side.png
1868 ms
popup_player.svgz
1720 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
816 ms
2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf
816 ms
HkF_qI1x_noxlxhrhMQYEKCWcynf_cDxXwCLxiixG1c.ttf
815 ms
VNUH7ZAcagYBWsAiBBCEY6CWcynf_cDxXwCLxiixG1c.ttf
925 ms
f569346a66f7da.jpg
255 ms
f56d4318b77a19.jpg
196 ms
f56d425ebae30a.jpg
202 ms
f56d41205f008d.jpg
200 ms
f56d405c5327a5.jpg
197 ms
f56d3fd836ae54.jpg
198 ms
f56d3f4cfd7bb8.jpg
205 ms
f56d02959895b4.jpg
206 ms
f56d266e9c2058.jpg
208 ms
f56cfe3a470490.jpg
210 ms
f567900cb26320.jpg
205 ms
f56cee56af04ce.jpg
204 ms
f56c17636b49df.jpg
211 ms
f566ac0fba28f7.jpg
208 ms
f566ac0c3da750.jpg
211 ms
f56d13c9c9efb7.jpg
210 ms
f569f16da42c52.jpg
227 ms
f56d05b60bd59c.jpg
228 ms
f566ac0d970e35.jpg
229 ms
f567900cbc2f4c.jpg
230 ms
source_bfm.png
1058 ms
source_iflyer.png
1117 ms
source_iloud.png
1120 ms
f56c6ee5975baf.jpg
1503 ms
twitter_v2.html
516 ms
timetableapi.php
1152 ms
nowonair_json.js
489 ms
blockfm
335 ms
blockfmapp_feedbanner.jpg
1541 ms
f5654341946134.gif
1626 ms
blockfmapp_feedbanner2.jpg
1824 ms
icon_start_playing_rev.png
1247 ms
__utm.gif
68 ms
__utm.gif
156 ms
like.php
219 ms
cb=gapi.loaded_0
156 ms
cb=gapi.loaded_1
154 ms
postmessageRelay
108 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
143 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
94 ms
55 ms
xd_arbiter.php
81 ms
xd_arbiter.php
160 ms
vpc6VNjRPXV.js
156 ms
LVx-xkvaJ0b.png
168 ms
api.js
43 ms
core:rpc:shindig.random:shindig.sha1.js
77 ms
2536007149-postmessagerelay.js
63 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
42 ms
timelineapi.php
860 ms
twitter_timeline.css
982 ms
jquery-ui-1.8.16.custom.css
1031 ms
jquery-ui-1.8.16.custom.min.js
1420 ms
modernizr.custom.js
1176 ms
twitter-entities.js
178 ms
twitter_v2.js
517 ms
twitter_burn.js
349 ms
special_event.js
353 ms
rollover.js
1216 ms
hooplayer.js
354 ms
jot
103 ms
0229djchart360.jpg
519 ms
211_Global-Ibiza-2013_360.jpg
440 ms
231_HeldeepRadio_360.jpg
491 ms
241_VINYL_HOUSE_360.jpg
440 ms
241_Deep_and_Tech_2015_360.jpg
488 ms
261_radioreboot_360.jpg
502 ms
blockchart1200.jpg
908 ms
0229djchart360.jpg
248 ms
sign-in-with-twitter-gray.png
177 ms
icon_twitter.png
191 ms
icon_tweet_btn.svgz
199 ms
icon_hoo_btn.svgz
189 ms
style.css
178 ms
jquery.browser.js
175 ms
jwplayer.js
709 ms
hooplayer_main.js
172 ms
logo.png
57 ms
block.fm accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 valid value for its [lang] attribute.
[lang] attributes do not have a valid value
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.
block.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
Missing source maps for large first-party JavaScript
block.fm SEO score
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
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Block.fm can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Block.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.
block.fm
Open Graph data is detected on the main page of Block. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: