8.9 sec in total
599 ms
7.2 sec
1 sec
Welcome to radiocrazy.fm homepage info - get ready to check RADIO CRAZY best content for Japan right away, or after learning these important things about radiocrazy.fm
FM802が毎年年末にお送りする「FM802 ROCK FESTIVAL RADIO CRAZY」。
Visit radiocrazy.fmWe analyzed Radiocrazy.fm page load time and found that the first response time was 599 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
radiocrazy.fm performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.1 s
2/100
25%
Value10.5 s
7/100
10%
Value770 ms
38/100
30%
Value0.178
68/100
15%
Value23.6 s
1/100
10%
599 ms
189 ms
882 ms
734 ms
372 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Radiocrazy.fm, 60% (80 requests) were made to Funky802.com and 18% (24 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Funky802.com.
Page size can be reduced by 320.8 kB (16%)
2.0 MB
1.7 MB
In fact, the total size of Radiocrazy.fm main page is 2.0 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 200 B
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 200 B or 30% of the original size.
Potential reduce by 185.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. RADIO CRAZY images are well optimized though.
Potential reduce by 68.5 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 68.5 kB or 59% of the original size.
Potential reduce by 67.1 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. Radiocrazy.fm needs all CSS files to be minified and compressed as it can save up to 67.1 kB or 83% of the original size.
Number of requests can be reduced by 50 (38%)
130
80
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RADIO CRAZY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
radiocrazy.fm
599 ms
foot.html
189 ms
882 ms
normalize.css
734 ms
reset.css
372 ms
font-awesome.css
944 ms
common2.css
960 ms
index4.css
578 ms
event.css
554 ms
news.css
729 ms
artistinfo.css
920 ms
jquery.min.js
47 ms
common.js
773 ms
jquery.backstretch.min.js
913 ms
snowfall.jquery.js
1096 ms
snowfall.js
970 ms
jquery.bxslider.js
1645 ms
jquery.bxslider.css
927 ms
gn_top3.png
233 ms
gn_news3.png
235 ms
gn_artist3.png
234 ms
gn_artistinfo3.png
232 ms
gn_event3.png
230 ms
gn_timetable3.png
371 ms
gn_goods3.png
369 ms
gn_access3.png
371 ms
gn_reminder3.png
386 ms
ttl_main2_sp.png
1156 ms
ttl_ticket2_sp.png
1159 ms
img_snowman1.png
1098 ms
sp_prg_ttl.png
1098 ms
corner_ttl2_sp.png
557 ms
dry_img_75835.jpg
1136 ms
dry_img_75827.jpg
1833 ms
f37e.gif
1282 ms
f669.gif
1282 ms
f7ee.gif
1327 ms
f7c1.gif
1342 ms
f697.gif
1351 ms
f651.gif
1467 ms
f6a8.gif
1467 ms
f47c.gif
1521 ms
f65a.gif
1536 ms
dry_img_75821.jpg
2695 ms
f7f4.gif
1648 ms
f6d2.gif
1648 ms
f3ee.gif
1708 ms
dry_img_75750.jpg
2107 ms
f674.gif
1831 ms
txt_lead2_sp.png
1832 ms
btn_radiko_sp.png
1890 ms
btn_tw_sp.png
2012 ms
bn_fusen.png
2012 ms
sdk.js
169 ms
bn_docomo.gif
2007 ms
widgets.js
146 ms
plusone.js
93 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
85 ms
fastbutton
110 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
191 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
224 ms
fontawesome-webfont.woff
2249 ms
bn_bodywild.gif
1986 ms
bn_horiba.png
1975 ms
bn_jr.png
1985 ms
bn_kiyobank.png
2078 ms
142 ms
postmessageRelay
45 ms
cb=gapi.loaded_0
34 ms
cb=gapi.loaded_1
33 ms
xd_arbiter.php
174 ms
xd_arbiter.php
301 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
149 ms
api.js
61 ms
core:rpc:shindig.random:shindig.sha1.js
127 ms
2536007149-postmessagerelay.js
94 ms
bn_raizin.png
2024 ms
bn_jt.jpg
2025 ms
logo_rc2015_m.png
2386 ms
txt_inquire.png
2120 ms
syndication
115 ms
383476510264279041
246 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
48 ms
icn_tw.png
2016 ms
1f4fb.png
242 ms
1f338.png
269 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
46 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
206 ms
1x9tk2FN_normal.jpg
152 ms
wKaSWuV5_normal.jpeg
153 ms
4inZ0CmB_normal.jpg
153 ms
______1_normal.gif
155 ms
maPwhGPR_normal.jpg
154 ms
ofoMsAjK_normal.png
157 ms
5rhekzTf_normal.jpg
155 ms
iPmcVCSE_normal.jpg
156 ms
GfLL2ElK_normal.jpg
154 ms
241c848e39b35a8b476ffcbbc6917f1a_normal.jpeg
158 ms
______normal.png
156 ms
CcbC2XpUAAAN8kf.jpg:small
201 ms
CcbEXWmUYAEdszb.jpg:small
160 ms
CcbCxfUUcAE6Vvx.jpg:small
158 ms
CcYwo4_UkAAzCPm.jpg:small
157 ms
CcI7XbhUcAE3tSX.jpg:small
168 ms
CcYfj9yUMAEJUCt.jpg:small
165 ms
CcYyYs_UcAA7JUM.jpg:small
167 ms
CcYy1s2UcAAEKB7.jpg:small
165 ms
CcYzLv-UcAAIo2G.jpg:small
166 ms
CcYwLDDUsAAxV3I.jpg:small
169 ms
CcYxzC4UYAAkpNO.jpg:small
168 ms
CcYui4hUUAAthj6.jpg:small
169 ms
CcYuEViUYAAYVp6.jpg:small
170 ms
icn_fb.png
1480 ms
icn_yt.png
1572 ms
bg_main_light_1280.png
2705 ms
02.png
1605 ms
corner_parts_1.png
1601 ms
jot.html
27 ms
corner_parts_2.png
1587 ms
corner_parts_bg.png
1608 ms
ttl_main2_pc.png
1971 ms
ttl_ticket2_pc.png
1779 ms
corner_ttl2_pc.png
1593 ms
txt_lead2_pc.png
1595 ms
btn_radiko_pc.png
1612 ms
img_snowman2.png
1606 ms
rcbg_2.jpg
2490 ms
[object%20Object]
1633 ms
snow_flake1.png
1655 ms
snow_flake2.png
1597 ms
snow_flake3.png
1643 ms
snow_flake4.png
1650 ms
radiocrazy.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
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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 [lang] attribute
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.
radiocrazy.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
Missing source maps for large first-party JavaScript
radiocrazy.fm 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
Tap targets are not sized appropriately
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Radiocrazy.fm can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Radiocrazy.fm main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
radiocrazy.fm
Open Graph description is not detected on the main page of RADIO CRAZY. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: