11.4 sec in total
2.6 sec
8.4 sec
358 ms
Click here to check amazing Rkk content for Japan. Otherwise, check out these important facts you probably never knew about rkk.jp
九州熊本のラジオ&テレビ放送局!(TBSテレビ系列) Ustream/Twitter/Facebook/foursquare にアクセス!
Visit rkk.jpWe analyzed Rkk.jp page load time and found that the first response time was 2.6 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rkk.jp performance score
name
value
score
weighting
Value7.9 s
1/100
10%
Value22.0 s
0/100
25%
Value17.6 s
0/100
10%
Value5,880 ms
0/100
30%
Value0.341
33/100
15%
Value33.3 s
0/100
10%
2606 ms
329 ms
331 ms
334 ms
34 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 69% of them (68 requests) were addressed to the original Rkk.jp, 7% (7 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Rkk.jp.
Page size can be reduced by 211.0 kB (16%)
1.3 MB
1.1 MB
In fact, the total size of Rkk.jp main page is 1.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. 50% of websites need less resources to load. Images take 983.6 kB which makes up the majority of the site volume.
Potential reduce by 42.0 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 42.0 kB or 77% of the original size.
Potential reduce by 21.7 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. Rkk images are well optimized though.
Potential reduce by 135.6 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 135.6 kB or 57% of the original size.
Potential reduce by 11.7 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. Rkk.jp needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 79% of the original size.
Number of requests can be reduced by 20 (21%)
97
77
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rkk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
rkk.jp
2606 ms
base.css
329 ms
top.css
331 ms
nivo-slider.css
334 ms
jsapi
34 ms
jquery.nivo.slider.pack.js
537 ms
pagescroll.js
363 ms
plusone.js
100 ms
news10-2011.php
628 ms
rkk-news2014.cgi
2702 ms
w-toptenkijava.js
498 ms
jquery.detapon.js
358 ms
widgets.js
4 ms
share.js
298 ms
noteit.js
19 ms
jquery.min.js
33 ms
cb=gapi.loaded_0
21 ms
article-clipper.png
28 ms
ybm16.gif
820 ms
0530.jpg
1488 ms
logo2014.png
204 ms
img_arpo1.png
209 ms
btn_ttmenu1.png
202 ms
btn_menu-l.png
208 ms
btn_ttmenu2.png
201 ms
bn_d12.png
451 ms
btn_menu-r.png
453 ms
btn_search.gif
450 ms
tit_blog.gif
464 ms
blogimg_33.jpg
462 ms
blogimg_msr.jpg
717 ms
blogimg_sorairo.jpg
715 ms
blogimg_tamago.jpg
714 ms
blogimg_kanpai.jpg
729 ms
blogimg_sore.jpg
730 ms
blogimg_tonderuwide.jpg
999 ms
blogimg_ds.jpg
1002 ms
blogimg_kc.jpg
1000 ms
blogimg_love.jpg
1015 ms
loading.gif
1015 ms
img20160103204935.jpg
1986 ms
img20160229232352.jpg
2070 ms
img20160229232439.jpg
2084 ms
bg_news2.gif
1278 ms
checkit-ico-os.gif
1279 ms
checkit-ico-bo.gif
1548 ms
checkit-ico-mi.gif
1546 ms
checkit-ico-ha.gif
1662 ms
title_detapon.gif
1815 ms
btn_weather1.gif
1812 ms
bannerb.cgi
2061 ms
bannerp.cgi
2037 ms
bannerp.cgi
2217 ms
bannerp.cgi
2187 ms
bannerp.cgi
2414 ms
share_button.html
306 ms
share
356 ms
ga.js
30 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
30 ms
cb=gapi.loaded_1
23 ms
fastbutton
95 ms
__utm.gif
30 ms
like.php
219 ms
bannerp.cgi
2146 ms
bannerp.cgi
2128 ms
btn_retop.gif
2053 ms
banner.cgi
2209 ms
banner.cgi
2243 ms
postmessageRelay
74 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
29 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
20 ms
api.js
47 ms
core:rpc:shindig.random:shindig.sha1.js
80 ms
2536007149-postmessagerelay.js
67 ms
jot
112 ms
bt_check_1.png
14 ms
vpc6VNjRPXV.js
132 ms
LVx-xkvaJ0b.png
163 ms
jquery-1.7.2.min.js
135 ms
banner.cgi
2006 ms
banner.cgi
2087 ms
banner.cgi
2111 ms
banner.cgi
2303 ms
banner.cgi
2318 ms
btn_iine_20.png
364 ms
banner.cgi
2080 ms
rkk_logo.gif
2015 ms
bg_newsber.gif
2034 ms
NS003201602291910580111.jpg
2040 ms
icn_arrow01.gif
2167 ms
bg_weather.gif
1915 ms
i_100.gif
1975 ms
wtime1.gif
1990 ms
wtime2.gif
1977 ms
wtime3.gif
1977 ms
wtime4.gif
1867 ms
bullets2.jpg
253 ms
rkk.jp 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 [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.
rkk.jp 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
rkk.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rkk.jp 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 Rkk.jp 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.
rkk.jp
Open Graph data is detected on the main page of Rkk. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: