4.4 sec in total
1.2 sec
2.9 sec
288 ms
Visit rokinawa.co.jp now to see the best up-to-date ROK Inawa content for Japan and also check out these interesting facts you probably never knew about rokinawa.co.jp
地域に根ざした楽しい番組をお届けします!
Visit rokinawa.co.jpWe analyzed Rokinawa.co.jp page load time and found that the first response time was 1.2 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rokinawa.co.jp performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value10.4 s
0/100
25%
Value18.7 s
0/100
10%
Value3,450 ms
2/100
30%
Value0.09
92/100
15%
Value45.8 s
0/100
10%
1227 ms
511 ms
355 ms
588 ms
734 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 97% of them (67 requests) were addressed to the original Rokinawa.co.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Rokinawa.co.jp.
Page size can be reduced by 47.0 kB (15%)
306.1 kB
259.0 kB
In fact, the total size of Rokinawa.co.jp main page is 306.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 235.3 kB which makes up the majority of the site volume.
Potential reduce by 41.4 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 41.4 kB or 85% of the original size.
Potential reduce by 1.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. ROK Inawa images are well optimized though.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 3.9 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. Rokinawa.co.jp needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 83% of the original size.
Number of requests can be reduced by 6 (9%)
66
60
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ROK Inawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
rokinawa.co.jp
1227 ms
style.css
511 ms
headbanner.html
355 ms
top_rok.jpg
588 ms
top_blue_bar_2.jpg
734 ms
speser.gif
388 ms
top_bangumi.jpg
554 ms
top_person.jpg
628 ms
top_news.jpg
694 ms
top_event.jpg
583 ms
top_shop.jpg
688 ms
top_pod.jpg
904 ms
top_mobile.jpg
768 ms
top_topics_000.jpg
705 ms
top_blog.jpg
783 ms
ten_ten.jpg
827 ms
news_n.jpg
852 ms
request-no_3_001.gif
711 ms
fb-f-logo__blue_29.png
377 ms
twitter_logo_2_000.jpg
378 ms
account_003.gif
481 ms
top_pod_big.jpg
864 ms
top_netradio_big.jpg
787 ms
spacer.gif
794 ms
splash_anime_201510.gif
1856 ms
icon_mail_000.gif
552 ms
colorful_anime_201510.gif
1098 ms
teasajiparadise_anime_201510_000.gif
857 ms
dj_pod.jpg
850 ms
dj_hp.jpg
848 ms
link_bannar_000.jpg
712 ms
rok_banner.jpg
1079 ms
mson_blog_bannar.gif
868 ms
tea-cha_appli_bannar2.jpg
878 ms
osb2015_bannar.jpg
1040 ms
sun_logo_bannar_000.jpg
1036 ms
nrn_120_40.jpg
1047 ms
18-rok.gif
1203 ms
rok_banner_okinawanouta_001.jpg
1420 ms
rokrecord_bannar2.jpg
1214 ms
rok_blog_banar_001.jpg
1253 ms
btn_60.gif
1274 ms
130913web.jpg
1410 ms
banner_120_90_000.gif
1217 ms
hougen_news_5_000.gif
1228 ms
hougen_news_5.gif
801 ms
speser.gif
805 ms
chatstation_anime_001.gif
1278 ms
dj_movie.jpg
852 ms
kinjonanae_60-60-2.gif
1297 ms
dj_blog.jpg
879 ms
motomurahiromi_60-60.gif
1375 ms
oyakoradio_60-60.gif
1385 ms
top_thum_aimoko.jpg
849 ms
do-yo_anime.gif
1443 ms
dj_head.jpg
954 ms
bar_back_mini.gif
956 ms
top_thum_akagawara.jpg
925 ms
sugiharaai_60-60_000.jpg
1476 ms
servicesunday_60-60.gif
1301 ms
tomitamegumi_60-60.jpg
1372 ms
fujikihayato_60-60.jpg
1380 ms
rokinawa02_000.jpg
1655 ms
podcast_2013befor_bana2.jpg
1480 ms
ichikiro_130-50_2.jpg
1536 ms
okinawa_chura_sounds_000.jpg
1550 ms
okinawabbtv.gif
842 ms
ga.js
26 ms
__utm.gif
26 ms
rokinawa.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
rokinawa.co.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
rokinawa.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Rokinawa.co.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 Rokinawa.co.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.
rokinawa.co.jp
Open Graph description is not detected on the main page of ROK Inawa. 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: